MathSphere Nexus
This site started the way most small-company sites start: in a page-builder, pasting text into little boxes, one block at a time. It worked — and it would have stayed that slow for every page and every change, forever.
So we changed the method instead of fighting the tool. The whole site is now plain files — the home page, the About page, the Projects page, this diary — built as finished files and hosted by GitHub Pages, straight out of a repository. There is no server to run. Updating the site is just updating the files, the same way everything else here is updated: in the terminal, with a commit whose message says what changed and why, read back before it is pushed.
The morning's record, in order: the first build landed as one commit (five files, the seal, the classic white and seal-red design ruled for the site) and the site went live. A Projects page followed the same day — each project labeled honestly, available now or in development, no dates promised. Then a dedicated showcase for the first completed project, the free Wizard Central Toolkit, with its full fleet table.
Two things this buys that a page-builder never would. First, the site lives in the same house as the code: versioned, checkable, and portable — if we ever buy a domain, it points at these same files and nothing is rebuilt. Second, nobody can suspend us from our own home. The audience a project builds on rented platforms can be switched off overnight; a repository we own cannot.
What is still open, stated plainly: an email list for beta and release announcements is planned — people will join by double opt-in and leave by unsubscribe, always — and it is not live yet, so there is no signup form here today. When there is real news, this diary is where it will be written first.
A command is what you type. The name is what the project is.
— Alexander