/ia

this page talks about how this personal website its organized, viz. its information architecture; the presentation layer is discussed in /theme; to learn more about the person behind the website, see /who.

the information (the what)

there are many types of website and ways of naming them: corporate; brand; personal; news; information; etc. sometimes it is hard to distinguish between them, for example, a personal website could equally be described as a brand if all it contains are self-centered humblebrags and “week notes” full of superlative-prefixed achievements¹.

this site falls into a few categories:

comments-off

because it eschews commenting (discus, webmentions, etc.); if you have anything to say, a rebuttal perhaps, then write something on your website and drop and email to notify me.

personal

because its centered about a person

slowweb

it takes time to write well, so a be grateful for the few posts that appear each year. nobody needs to post frequently.

indieweb-friendly

becasue it supports some IndieWebOrg building blocks, specifically some microformts data will be emitted using conneg

the message (the how)

the message is stored in whatever is the most convenient form for the author and mangled into whetever is convenient for the reader

to get technical: data is stored as text, markdown, html, etc., and varied by the web server into an appropriate format for the user agent using http’s content negotiation (conneg).

the architecture (the where)

/

the index page: gotta start somewhere, and this is it

http’s content negotiation (conneg) is used to vary the response, which opens up a lot of possibilities (not least of which is annoying tantek who is so anti-conneg its worth implementing just to make a point)

/feed.rss

the principal rss feed for the website

/assets/

contains presentation layer assets (style sheets, fonts, etc.)

/assets/theme/<name>

contains a set of assets bundled together as the theme called <name>.

/app/<codename>

for applications that I develop, this contains various landing and associated pages, sometimes hand-wrangled HTML, mostly markdown because hand-wrangling HTML is not my idea of having a good time.

/b/<yyyy>/<slugname>-<id>

blog posts — organized by year then <slugname>-<ID>

/bot/<codename>

for bot and libraries that I develop, the user-agent is set to a resource at /bot/<codename>; this is so any sysadmin who bothers to examine their logs will have someplace to go when their curiosity is peaked or something has gone terribly wrong and they’re looking who to blame

/i

object by uuid-based reference; primarily to retrieve Activity Stream objects using ActivityPub

/e

ephemeral bullshit goes here

/my/<thing>

a place to share specific personal resources in a simultaneously memorable and also secure manner. e.g. my thumbnail picture is at “/my/thumbnail”. Thanks to some back-end magic, the actual resource returned will VARY based on who is asking for it (user-agent, peer address, etc.).

/w

writing — many words of wisdom are contained herein

/u

for use with ActivityPub, anything that’s user-oriented is here, i.e. inbox, outbox, etc.

$LastModified: 2024-11-18 15:29:36Z (Mon, 18 Nov 2024) $