Squido Auth Method

Doing

Migrating from a device flow model as I build out the roadmap for Squido.

Thinking

Future of Squido

I’m now thinking of Squido as more than just a publishing tool. It should become a multi-destination authoring tool. It doesn’t matter whether it’s creative writing, notes, documentation, or website content, it should have different destinations saved as states with custom metadata, icons, locales, and format.

Web Dev Workflow

I’m also seeing potential as a web content dev tool, drafting changes to content and seeing live updates through a local dev server set up to hot reload. As long as content is mapped out as separate content sections (easier if done through something like Astro collections), adding a folder or web content to Obsidian presents an exciting opportunity to build and edit content directly in a writing-friendly environment, away from other html.

It’s non destructive and doesn’t require a server side site rebuild. When ready, merely publish the page via Squido and the markdown is sent to GitHub or wherever you set it up to be stored.

There is much more to this, and I aim to make it clear in documentation in the repo as it crystallizes.

Friction and User Experience

This is the big step right now. It’s crucial that setup is smooth on desktop and mobile. So before any new features are added, I’m working on a GitHub companion app to allow easy one-click connection to GitHub, multiple saved repo destinations and folders, and no unencrypted tokens stored in data.json or anywhere it can be accidentally leaked.

This should operate similar to how VS Code connects to a GitHub account. Except ideally Squido will enable multiple destinations as time goes on.