Releases

Paramsat 1.0

The first numbered release. A Lab to read and search, Google sign-in for its owner, and pages edited where they stand, saved as private drafts and published as revisions.

22 Oct 2026 #paramsat

Paramsat 1.0 is the first release to carry a number. The site has been live at paramsat.com since 9 October 2026; this release gathers what has been built since, and each release after it will have notes of its own, saying what it changes.

It brings forward much of what the roadmap kept for a later phase: signing in, an editor, drafts that save themselves, revisions and publishing.

Reading

  • A Lab holds projects, and a project holds its work as pages in sections, such as Docs and Posts, each page with a sidebar, an On This Page rail and a way to the next page.
  • Every address begins with the Lab's owner: /tejas is the Lab, /tejas/paramsat one of its projects, and the project's pages follow.
  • Search looks within the project being read, with a switch to every project; on the front page it covers them all from the start.
  • Topics gather pages across projects.
  • A page can hold cards, buttons and pictures, across the column or beside the text, rows of columns, tables, code and notes, as well as its prose.
  • Nothing is counted: there are no views, likes or followers.
  • The theme follows the system's, or is set to light or dark from the account menu.

Writing

  • The Lab's owner signs in with Google. Reading never asks anyone to sign in.
  • The owner edits a page where it stands. Its prose is typed into the page itself, with a toolbar for the style of a block, bold, italic and links. Cards, buttons, pictures and the other blocks open in place, as small forms or as their Markdown, and Insert adds new ones. Edit Source shows the whole file.
  • What is typed is saved as a private draft within seconds, and the sidebar marks the pages whose drafts readers have not seen. Publish makes the draft the page's next revision, with a note of what changed. Every revision stays readable to the owner, and an older one can be published again.
  • A draft changed in two places at once is never overwritten: the later save shows the newer text above its own, to be merged.
  • When a session ends, Sign In opens in a tab of its own, and the page keeps what was typed and saves it once the owner is back. What no save has taken is also kept in the browser, and offered back the next time the page opens.
  • On a phone, the toolbar stays at the top of the screen while the keyboard is up.

Under the Hood

  • The site is one Go program. A Lab's pages live in a PostgreSQL database, every published revision kept.
  • Every change to the site is tested in Chromium and WebKit, the engines of Chrome and Safari, before it is released.

Not Yet

  • Several Labs, each with its own owner. The addresses and the database already leave room for them, but the site serves one Lab, and only its owner can sign in.
  • Uploading pictures. For now a picture is one of the site's own files, or an address.
  • The title and summary edited in place, and blocks moved by dragging.
  • Responses, typed links made in the editor, and an assistant (Phase D).