We’re building Ever Works in public. Some things may be incomplete, missing, or broken while we continue improving the platform.We’re building Ever Works in public — expect a few rough edges.
Use Case
A blog only works if it keeps publishing. Ever Works turns an editorial calendar into shipped posts: it researches the topic, writes the draft, and deploys — on the cadence you choose — so the blog stays active and your search footprint keeps growing, all owned in your Git. The writer behind the Posts tab today is the platform’s shared content pipeline; a dedicated blog-post generator is rolling out.
Posts grounded in a real, cited reference set rather than generic filler.
Style and tone pulled from your Knowledge Base every run.
New posts land in your Git and go live without anyone opening a CMS.
Older posts are refreshed so the archive stays useful.
Give the platform topics and a cadence.
Drafts are researched and written by the shared content pipeline.
Posts ship to your site automatically.
Blog is a first-class Work kind. The Blog chip is live on the create page, the kind is persisted on the Work, the content tab is named Posts, categories and tags are kept, the Overview tiles are posts, page views, registered users and deploy status, and the works.yml spec carries authors, taxonomies, the feed, pagination and a generation cadence. Deploys, custom domains, schedules, the Knowledge Base and the three Git repositories all work now. One part is still landing, and it is worth knowing before you plan around it: there is no dedicated blog-post generator yet, so the Posts tab is filled by the same content pipeline every Work runs — the one built for directory-shaped content first. The blog, its repositories, its schedule and its upkeep loop are yours on day one, while the editorial writer catches up.