Show HN: Sparktype – a CMS and SSG that runs entirely in the browser

Hacker News (score: 15)
Found: November 04, 2025
ID: 2327

Description

Other
Show HN: Sparktype – a CMS and SSG that runs entirely in the browser Hi HN,

After trying to teach a non-technical friend how to manage a Jekyll site I decided there must be a way to make building a site with a SSG easier. Options like Decap, Contentful etc. do make it a bit easier but still take lots of tech knowledge to set up.

So I built Sparktype, a browser-based CMS that outputs statically-generated HTML and CSS. My goal is for it to be as easy to use as Substack or Medium, while providing all the benefits of a static site generator including openness, simplicity, speed, security and ownership.

It handles most things that you'd need from a CMS, including creating pages, image resizing, menu management, tags, collections, listings etc. I've only made two themes so far, but I'm working on a theme store and the ability to import custom themes.

Content is saved as plain Markdown + YAML frontmatter and JSON config files, so there's no lock-in and content is easily portable to other platforms. Generated sites can be exported as a zip file to upload via FTP, committed to Github or published via Netlify API.

I'm working on cross-platform client apps using Tauri which will enable more publishing options as its not limited by what can be done in a client-only environment.

The way the system works means that the Web doesn't need to be the only interface to the content - here's a simple Go-based CLI client that bypasses the HTML altogether https://github.com/sparktype-project/sparktype/tree/main/st-...

It's very early days and there are still plenty of bugs, but I'm posting now to hopefully get feedback and see what people think. Please do let me know!

More from Hacker

Show HN: MkSlides – Markdown to slides with a similar workflow to MkDocs

Show HN: MkSlides – Markdown to slides with a similar workflow to MkDocs As a teacher, we keep our slides as markdown files in git repos and want to build these automatically so they can be viewed online (or offline if needed). To achieve this, I have created MkSlides. This tool converts all markdown in a folder to slides generated with Reveal.js. The workflow is very similar to MkDocs.<p>Install: `pip install mkslides`<p>Building slides: `mkslides build`<p>Live preview during editing: `mkslides serve`<p>Comparison with other tools like marp, slidev, ...:<p>- This tool is a single command and easy to integrate in CI&#x2F;CD pipelines.<p>- It only needs Python.<p>- The workflow is also very similar to MkDocs, which makes it easy to combine the two in a single GitHub&#x2F;GitLab repo.<p>- Generates an index landing page for multiple slideshows in a folder which is really convenient if you have e.g. a slideshow per chapter.<p>- It is lightweight.<p>- Everything is IaC.

Structured Outputs on the Claude Developer Platform (API)

Structured Outputs on the Claude Developer Platform (API)

Show HN: qqqa – a fast, stateless LLM-powered assistant for your shell

Show HN: qqqa – a fast, stateless LLM-powered assistant for your shell I built qqqa as an open-source project, because I was tired of bouncing between shell, ChatGPT &#x2F; the browser for rather simple commands. It comes with two binaries: qq and qa.<p>qq means &quot;quick question&quot; - it is read-only, perfect for the commands I always forget.<p>qa means &quot;quick agent&quot; - it is qq&#x27;s sibling that can run things, but only after showing its plan and getting an approval by the user.<p>It is built entirely around the Unix philosophy of focused tools, stateless by default - pretty much the opposite of what most coding agent are focusing on.<p>Personally I&#x27;ve had the best experience using Groq + gpt-oss-20b, as it feels almost instant (up to 1k tokens&#x2F;s according to Groq) - but any OpenAI-compatible API will do.<p>Curious if the HN crowd finds it useful - and of course, AMA.

Show HN: KeyLeak Detector – Scan websites for exposed API keys and secrets

Show HN: KeyLeak Detector – Scan websites for exposed API keys and secrets I built this after seeing multiple teams accidentally ship API keys in their frontend code.<p>The problem: Modern web development moves fast. You&#x27;re vibe-coding, shipping features, and suddenly your AWS keys are sitting in a &lt;script&gt; tag visible to anyone who opens DevTools. I&#x27;ve personally witnessed this happen to at least 3-4 production apps in the past year alone.<p>KeyLeak Detector runs through your site (headless browser + network interception) and checks for 50+ types of leaked secrets: AWS&#x2F;Google keys, Stripe tokens, database connection strings, LLM API keys (OpenAI, Claude, etc.), JWT tokens, and more.<p>It&#x27;s not perfect, there are false positives but it&#x27;s caught real issues in my own projects. Think of it as a quick sanity check before you ship.<p>Use case: Run it on staging before deploying, or audit your existing sites. Takes ~30 seconds per page.<p>MIT licensed, for authorized testing only.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;Amal-David&#x2F;keyleak-detector" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Amal-David&#x2F;keyleak-detector</a>

No other tools from this source yet.