Your help center, blog and FAQ: same module, same workflow
Most companies end up with a help center on one platform, a blog on another, a knowledge base on a third, and a product-tours tool on a fourth. Each has its own login, editor, search index and analytics. Worknano collapses all of that into one Articles module: every piece of long-form content lives in the same place, with a 'type' field deciding whether it shows up in the help center, the blog, the FAQ accordion or as an in-app tour.
Six article types, one editor
Help: task-shaped content for users solving a specific problem. FAQ: short Q and A surfaces, embeddable anywhere. Blog: magazine-grade posts with hero images and rich layout. KB: internal knowledge base, scoped to the workspace. Policy: company policies with version history and acknowledgement tracking. Tour: Shepherd-powered in-app product tours.
Publish to the right surface, automatically
Set type and visibility; the article shows up where it belongs. A help article goes to /public/articles?type=help on your wn tenant. A blog post goes to the blog index and emits an RSS entry. A FAQ becomes available to embed via the [FAQ:slug] marker on any other page. An internal kb article is invisible to the public but searchable from the in-app help widget.
Editor that does not fight you
Rich text with code blocks, callouts, tables, embeddable forms, embeddable other articles, embedded screenshots from the screenshot library, and AI assists for tone, length and SEO. Drafts, scheduled publishing and version history are built in.
Search that works because the content is unified
Because help, blog, FAQ and kb live in the same table, search can rank across all of them. The in-app help widget surfaces the most relevant article regardless of type. Public visitors get the public surfaces; logged-in users get the broader index.
[FAQ-CATEGORY:help]