Plan for books

I've had /books parked now since two to five versions of my site ago.

But, nothing's yet written, organized, pitched, set in sand (let alone stone).

I want to be more open about it, and share with people the various works in progress.

So—

here's what's been cookin' in the background as I've been running my worrystone of a website.

The URLs

I've "parked" multiple pages with the titles of the books, each having various children depending on where the lightning struck.

These all live under /books, but none of them are live & publicly accessible.

The goals and content design of this section of the site:

• /books has an overview intro of how I'm writing in open; each book having a title/nutgraf/call-to-action.
• /books/$title is a book's homepage, with an overview, various chapter notes, /links and other content tagged as the book titles.

The Boundaries

Books are long-thought stories I want to tell. I need time to focus, but also build over time in the midst of everything else happening in life.

Call it "preparing for a time of writing, but currently in a time of necessity & doing."

That's the point of building up over time. It's collecting primary and secondary sources. It's building associative links to temporal context.

Difference with Essays

Essays are series of long-ferm personal articles, as well as essay series.

Essays are then organized as:
`/essays/$title/$part'.

For my Chrysalis essays, that would translate to:

• /essays/chrysalis/ as the first essay/article in the series
• /essays/chrysalis/2 as the second essay/article in a series and part-two.

Or, rather more specific and dependent on the essays themselves:

• /essays/chrysalis/jan-jun/
• /essays/chrysalis/jun-dec/

I don't know. But it's different in terms of intent and story over time.

Chrysalis is set and done.

I could have Tattoo Series where I gather all my personal articles of my tattoos into one space.

This would be a way of building both books (a content type inside a book collection) built from essays organically as well as essays being singular encapsulations within themselves.

I intend to write more of my tattoos.

The others haven't had their stories told; yet.

And—they're stories I wanna tell.

Similar to /tags

This layout of content-type sorted groups is similar to what currently exists at /tags.

Tags are grouped by the entries that appear in /journal, /articles, /essays, /work...and every other page of my garden.

Tags are a required field for my site. As a rule, that's one not to break. I do this for future me to use to help make sense of how my content architecture merged rather than "is defined as."

I know this likely goes against a lotta "how things are done" but it's one of the reasons I like Kirby. It adapts, as I adapt. It's also more intentional. Tending my garden doesn't just mean coming back to topics and iterating on.

For me, it means coming back and making better sense of the tags over time. Categorizing and sensemaking what it's become. Learning about the trends, seeing what I'm reading/writing/tagging.

Also, just data normalization of tags. Figuring out how to improve it more programmatically (e.g. ICE should also be I.C.E. and Immigration and Customers Enforcement...but could also be spelled ice, Ice, i.c.e....but not confused with Immigration or fascists, just because of frequent pairing).