I like to wax rheotircal; this is where I write it down.

I also like to program computers, so I'll make my own publisher here. It's a work-in-progress.

All endeavors are susceptible to distraction and delay. This readme is my scratch pad to avoid bikeshedding the core function of writing.

The other file [INSTALL.md] contains notes about how to check out the code, install dependencies, use specific markdown elements for articles (blurbs, tags, sitemap entries), and finally how to publish.

• something's wrong with nested tags, e.g. science/programming/accessibility
• the "business" category link is broken because of that -^
• rss entries don't update, e.g. when tags are added

• DNS, hosting, updating, etc.

• Produce html from markdown

• Derrive publish and update dates from version control

• Create a good global layout

• SEO, analytics, and whatnot

• inter-linking pages like a real blog CMS

• image hosting?

• cool 2nd-buffer tool for deciding when to publish a draft document

• MDX stuff for frontmatter-or-whatever-you-call-it

• nextjs because it does all of the above jobs

• private submodule for drafts

• css & layout

• use tagged releases instead of branch deploys?

• spelling, grammer, and readability checker?

• add a tagging system

• create a "showworthy" feature list

• DNS/hosting - solved circa March 2021

• nextjs/mdx - started shortly after, but abandoned. Giant pain in butt.

• markdown MVP - start late in 2021...so late it's 2022 as I type this - complete Jan 1 2022 :party:

• private drafts start ~ Jan 11th - easy but uses submodules; blog about that

• css & layout start ~ Jan 11th

• tagging - Weekend of Feb 5th 2022

• editorconfig - Sunday Mar 3rd 2022, much nicer markdown paragraph linebreaks

This is a git repository, it's used for github-io which is Github's hosting. I further pointed it at an external domain via google's DNS registration.

Anything in /docs is public on the internet at the address specified in the CNAME file.

This repository holds the raw content and the published content. I also keep some draft content in a git submodule that is not a public repo; not every- thing that i type needs to be published. I find it conducing my ability to actually do the writing to not concern myself with the consequences of publishing.

• tags produced in the wrong order (css-misadventures)
• tags get nested strangely (science/programming)

• index page
• [/] about & contact & other non-articles
• footer (disclaimer, cookies)
• date & author
• basic images (its own featureset for non-basic)
• analytics
• seo stuff (robots, sitemap)
• micro-/structured-data for embedding

• refine the illumination
• dark mode
• color scheme
• fill-width style when appropriate (just headline?)

• make the author microdata nicer, maybe a custom renderer
• rss (as a cookie alternative)
• spellcheck - use hunspell and also blog about it

• pingback on api subdomain [https://www.hixie.ch/specs/pingback/pingback]
• rel="tag" to link to glossary pages
• web app manifest ("download this ebook", maybe?)
• rel="author" instead of microdata nonsense
• font-size 36 or 24 are both not reasonable; headings should be multiples, not the basis
• sitemap style sheet a la duluth dish via wordpress plugin; use this instead of html sitemap

• add descriptions/snippets/whatever
• refine the blockquote excerpt
• add a stylesheet to it

[INSTALL.md] ./INSTALL.md