FolderPress for Developers

You could set up a static site generator. Choose a framework. Configure the build pipeline. Set up CI/CD. Pick a hosting provider. Wire up a custom domain. Debug the CSS. Update dependencies every few months.

Or you could save a markdown file to Dropbox and have a blog.

FolderPress is for developers who want to write about code without having to maintain the infrastructure for it.

#No Build Pipeline

There’s no npm run build. No git push triggering a CI pipeline. No waiting for a deploy. No build failures because a dependency changed.

Save a markdown file to Dropbox. FolderPress detects the change via webhook, parses the markdown, and publishes it. The whole cycle takes seconds.

You already know how to create a file. That’s the entire deployment workflow.

#Write in Your Editor

VS Code, Neovim, Emacs, Sublime Text, Obsidian — whatever you use for code already handles markdown. Syntax highlighting, multiple cursors, split panes, find-and-replace across files. Your editor’s full power applies to your blog posts too.

No browser tab with a CMS. No WYSIWYG editor that mangles your formatting. No “paste as plain text” ritual. Just your editor and a file.

#Code That Looks Right

FolderPress uses Shiki for syntax highlighting — the same engine that powers VS Code’s syntax highlighting. That means:

• 100+ languages with accurate tokenization
• Theme-aware highlighting that matches your site’s design
• No client-side JavaScript — code blocks render as HTML, not a runtime syntax highlighter

```typescript
async function syncDelta(accountId: string) {
  const cursor = await getCursor(accountId);
  const entries = await fetchDelta(cursor);
  return processBatch(entries);
}
```

Your code looks like code, not a colored blob. Light and dark mode switch automatically, and line highlighting works out of the box — because developers expect that from code blocks.

Why it’s fast: Shiki runs server-side at render time, not on every sync. The output is static HTML — no JavaScript bundle shipped to the reader, no runtime highlighter, no layout shift. Server by default, client only when earned. A blog is a read path; nobody needs an interactive code editor in the browser. Rendering lazily (not on every edit) amortizes Shiki’s cost, so you get VS Code-quality highlighting without the performance penalty.

FolderPress is built for sharing 20-line code examples in blog posts, not pasting 500-line files. It’s for writing about code, not writing code to blog.

Full GitHub Flavored Markdown support too — tables, task lists, strikethrough, autolinks. If you write markdown on GitHub, you already know the syntax.

#Math That Renders

Writing about algorithms, ML, or anything mathematical? FolderPress renders KaTeX inline and display math.

The loss function $L(\theta) = -\sum_{i} y_i \log(\hat{y}_i)$ converges as $n \to \infty$.

No plugins. No configuration. Write LaTeX in your markdown and it renders.

#Slide Decks From Markdown

Conference talk coming up? Drop a markdown file in your decks/ folder and use --- (three dashes on a blank line) to separate slides — the same convention used by Marp and reveal.js. FolderPress renders it as a navigable slide deck at a URL you can share.

One format for blog posts, documentation, and presentations. Less context-switching.

#File System as CMS

Your folder structure becomes your URL structure:

my-blog/
  posts/
    building-a-sync-engine.md      → /posts/building-a-sync-engine
    typescript-tips/
      discriminated-unions.md      → /posts/typescript-tips/discriminated-unions
      branded-types.md             → /posts/typescript-tips/branded-types

Rename a file and FolderPress creates a 301 redirect from the old URL to the new one. Your link equity is preserved, and nothing breaks.

#What You Don’t Have to Manage

Unlike Ghost or WordPress, there’s no admin panel to maintain. FolderPress handles what you’d otherwise spend weekends configuring:

#Frontmatter Support

Use YAML frontmatter for metadata:

---
published_at: 2026-01-15
description: "How I built a webhook-triggered sync engine on top of Dropbox's delta API."
---
 
# Building a Sync Engine
 
Your post content starts here...

Title comes from the first H1 heading, then the filename. Published date defaults to the current date when first synced. Descriptions are auto-generated from your content unless you set one in frontmatter. Sensible defaults, optional overrides.

#Who This Is For

FolderPress is for developers who:

• Want a blog but don’t want a side project maintaining it
• Write markdown daily and don’t want a different workflow for blogging
• Need proper code highlighting, not a CSS hack
• Want to own their content as files, not database rows
• Prefer convention over configuration

#What You Give Up

Being honest about trade-offs:

• No custom themes — FolderPress renders your content in a clean, consistent layout. You don’t control the CSS.
• No API — there’s no headless CMS endpoint. It’s a publishing tool, not a data source.
• No build hooks — you can’t trigger custom scripts on publish.
• Dropbox only — no Git-based sync (yet).

If you need a static site generator with full control, tools like Astro or Hugo are what you want. If you want to write and publish without any of that — FolderPress is for writing about code, not writing code to blog.

#FAQ

#Does FolderPress support GitHub Flavored Markdown?

Yes. Tables, task lists, strikethrough, autolinks, and footnotes all work. See the markdown blogging guide for the full syntax reference.

#Can I use FolderPress for documentation?

FolderPress is optimized for blogs and writing, not multi-page documentation sites. For docs, tools like MkDocs or Docusaurus are better suited.

#How does the URL routing work?

Your folder structure becomes your URL structure. A file at posts/typescript/generics.md becomes /posts/typescript/generics. Rename the file and FolderPress creates a 301 redirect automatically.

#Can I run FolderPress locally?

No. FolderPress is a managed service. Your content syncs from Dropbox and is hosted by FolderPress. There’s nothing to install or run.

#What languages does Shiki support?

Over 100, including TypeScript, Python, Rust, Go, Java, Ruby, Swift, Haskell, SQL, and many more. Any language VS Code highlights, Shiki highlights.

#How do I get started?

Connect your Dropbox, drop a markdown file in the folder, and you’re published. The whole thing takes about five minutes. Here’s a step-by-step walkthrough.