Hi HN,I’m Martin, a 20-year-old developer from Hungary, and I’ve been building Scrib.ee by myself for the past 8–9 months.It started as a personal project. I wanted a blog that actually felt like my own space: my domain, my branding, my fonts, my favicon, my Open Graph metadata, my analytics, and control over how everything looked and worked.I liked the result enough that I decided to turn it into a SaaS.Scrib.ee is currently in alpha. It includes a Tiptap-based editor, custom domains and subdomains, configurable fonts and themes, tags, multiple authors, comments through Scrib.ee accounts, image uploads, YouTube embeds, editable metadata, generated sitemaps, full-text search, and analytics for geography, user agents, and popular posts.Longer posts also get a feature called Cleo. It works like a small tour guide for the article. It can target important text sections and show short popup explanations that help readers understand the structure and key points of the post.Public posts are also available as clean Markdown by adding .md to the URL:/posts/example-post /posts/example-post.mdEach blog also has a simple /llms.txt file, but this is only a small compatibility feature rather than a core part of the product.The application uses two Nuxt 3 frontends: one for the dashboard and one for the public blogs. The backend is written in Go with Echo, and the rest of the stack includes MySQL, Redis, Meilisearch, and a few smaller Go services such as sitemap generation.Everything is free during the alpha, with no credit card required. The only current limit is a maximum of two blogs per account.Around 30 people have registered so far, but it is still very early and only a few blogs are actively being tested.The MVP is mostly complete, so I’m now trying to decide what to improve next. One idea is to add multiple blog layouts instead of having one layout with configurable colors, fonts, and themes.I would really appreciate feedback on:- Which missing feature would stop you from using it? - Should I prioritize more layouts, publishing workflows, integrations, or something else? - Are there security, abuse, SEO, or scalability issues I should focus on early? - Does Cleo sound useful, or would it just get in the way while reading?I built the whole project alone, so feedback on both the product and the technical approach would be very helpful.