Blog

Write essays, project deep-dives, and announcements that live alongside your portfolio at folii.ai/your-username/blog.

Why blog on folii?

Your portfolio shows what you've built. The blog shows how you think. A short post about a tricky bug, a system you designed, or a library you wrote tells a hiring manager more in two minutes than a bulleted resume can in twenty.

And folii makes it cheap. No separate Substack to manage, no markdown repo to deploy, no CSS to fight. Open the editor, switch to the Blog tab, write or chat your way through a draft, hit Publish.

Writing a post

  1. 01Open the Blog tab in the editor and click New post. You get an empty draft with a title field, a markdown body, an excerpt, and a tags input.
  2. 02Type the post yourself or use the chat panel on the right. The chat understands prompts like "draft a 400-word post about my Stripe integration project" or "rewrite the intro to sound more conversational." Edits autosave as you go.
  3. 03Publish. Toggle status from Draft to Published. The post appears at folii.ai/your-username/blog/the-post-slug and on the listing page at folii.ai/your-username/blog.

Markdown that just works

The body field is GitHub-flavored markdown. Headings, lists, links, images, tables, blockquotes, and fenced code blocks all render the way you'd expect.

Code blocks

Triple-backtick code blocks get full syntax highlighting via Shiki. Specify the language right after the opening fence:

  • ```ts for TypeScript, ```py for Python, ```sql for SQL, and so on.
  • Themes auto-switch with your reader's dark/light preference.

Tags and excerpts

  • Tags show up as pills on the listing card and on the post page. Use them as topic markers (e.g. postgres, career).
  • Excerpt is the two-liner under the title on the listing. Skip it and folii will use the first ~200 chars of the body.

Drafts vs published

Every post starts as a draft. Drafts are visible only to you in the editor. Switch the status to Published and the post appears on your public blog. You can flip a published post back to draft at any time to take it offline without deleting it.

Tip
Slugs are derived from the title, but you can edit the slug before you publish. After publishing, changing the slug breaks any links you've already shared, so lock it in early.

Writing with chat

The blog chat sits next to the editor and is scoped to the post you're editing. Some prompts that work well:

  • "Draft a 500-word post about why I picked Postgres over DynamoDB for my last project."
  • "Rewrite the second section to be less academic and more conversational."
  • "Add a code example showing how I set up the rate limiter."
  • "Suggest five tags for this post."

The chat reads your portfolio for context, so "write a post about the project I shipped at Stripe" will pull from your actual project list, not invent details.

What's next

  • Publishing — how publish works for the portfolio and how it interacts with blog posts.
  • Editing with AI — the same chat principles that work for the portfolio also work for the blog.