<?xml version="1.0" encoding="utf-8"?>

<feed xmlns="http://www.w3.org/2005/Atom" xml:base="https://pelliott.ca/">

	<title>peter elliott</title>
	<link href="/blog/atom.xml" rel="self" />
	<link href="/blog" />
	<id>urn:uuid:a394b9a4-16dc-47bb-ad6b-81e0f8bae4fe</id>
	<updated>2026-07-15</updated>

    
	<entry>
		<title>hello</title>
		<link href="/blog/hello" />
		<id>urn:uuid:5d2c1087-978c-4f49-8fa1-881551e04859</id>
        <published>2026-07-15</published>
        
        <summary>thoughts about personal websites, and why i made this one</summary>
		<content type="html">
          <p>if you're reading this, then i've finally made a personal website. as
a programmer i've always thought that i should have a personal website,
but in what form? making a portfolio seemed like a chore, and blogging
died before i was capable of forming blog-length thoughts. but the
concept of the "personal web", where your website is reflection of your
personality, with no creative limits really appealed to me.
unfortunately all i've come up with so far is a beige
portfolio/blog.</p>
<p>growing up in a web 2.0 world, i default to thinking about websites
as multi-user applications. in doing so, i try to model a domain as
simple and generic as possible. a site is for x to do y. well, this site
is for me to do everything. there is no singular uniting idea that it's
modeled around, other, than that it's mine.</p>
<p>i hope that by freeing myself of the restriction of designing for the
general case i can come up with some real fun stuff. but for now, enjoy
my little beige blog.</p>

		</content>
		<author>
			<name>peter elliott</name>
			<uri>/</uri>
		</author>
        
        <category term="meta"/>
        
        <category term="personalweb"/>
        
	</entry>
    

</feed>
