Show HN: MkSlides – Markdown to slides with a similar workflow to MkDocs
Hacker News (score: 15)Description
Install: `pip install mkslides`
Building slides: `mkslides build`
Live preview during editing: `mkslides serve`
Comparison with other tools like marp, slidev, ...:
- This tool is a single command and easy to integrate in CI/CD pipelines.
- It only needs Python.
- The workflow is also very similar to MkDocs, which makes it easy to combine the two in a single GitHub/GitLab repo.
- Generates an index landing page for multiple slideshows in a folder which is really convenient if you have e.g. a slideshow per chapter.
- It is lightweight.
- Everything is IaC.
More from Hacker
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 / the browser for rather simple commands. It comes with two binaries: qq and qa.<p>qq means "quick question" - it is read-only, perfect for the commands I always forget.<p>qa means "quick agent" - it is qq'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've had the best experience using Groq + gpt-oss-20b, as it feels almost instant (up to 1k tokens/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: Sparktype – a CMS and SSG that runs entirely in the browser
Show HN: Sparktype – a CMS and SSG that runs entirely in the browser Hi HN,<p>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.<p>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.<p>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.<p>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.<p>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.<p>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 <a href="https://github.com/sparktype-project/sparktype/tree/main/st-cli" rel="nofollow">https://github.com/sparktype-project/sparktype/tree/main/st-...</a><p>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!
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're vibe-coding, shipping features, and suddenly your AWS keys are sitting in a <script> tag visible to anyone who opens DevTools. I'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/Google keys, Stripe tokens, database connection strings, LLM API keys (OpenAI, Claude, etc.), JWT tokens, and more.<p>It's not perfect, there are false positives but it'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://github.com/Amal-David/keyleak-detector" rel="nofollow">https://github.com/Amal-David/keyleak-detector</a>
No other tools from this source yet.