ePokalbis community forum

ePokalbis is a self-care product, and it needed a public place for people to start topics and talk — separate from anything private.

A self-care platform lives or dies on whether people feel safe enough to talk, so ePokalbis needed a place where visitors could read and post without the whole thing feeling like a clinical intake form. The tension was keeping the public forum genuinely live — new posts and replies appearing without reloads — while the marketing copy around it stayed easy to edit by non-engineers. Those are two very different update rhythms, and we didn't want one to hold the other hostage.

A webedge-db-backed forum — topics, threaded discussions and content pages — that anyone can read and join, sitting alongside the rest of the ePokalbis platform.

This is the public community forum for ePokalbis: topics people can browse and discussions they can join, sitting on the public side of the self-care platform. Forum state lives in our reactive backend so threads update as they change, and the surrounding public descriptions are edited through our CMS rather than hard-coded.

Built with Vue 3, webedge-db, CMS sync.

The forum data runs on our reactive backend for live thread updates, while the static public copy is authored in our CMS and pulled into the page, keeping content edits out of the deploy loop.

People find a topic, join the discussion and come back to it, in a public space that stays distinct from the app's private side.

A modest, honest piece: a working public forum where discussions stay current on their own and the surrounding copy can be reworded without a developer. There is no public repository for it.