Publishing needs
Running the magazine means preparing new articles while keeping earlier stories accessible. Content needs to remain connected to its subjects and contributors, rather than becoming an archive readers can navigate only by publication date.
Jsme.cz supports several starting points: recent stories, subject categories, thematic collections and authors. These reflect different reading needs—from browsing a broad subject to following a specific theme or finding more work by a familiar contributor.
A connected reading experience
The website brings categories, collections, author profiles and search into its navigation. The homepage also separates recent articles from editorial selections and most-read stories, giving readers alternatives to a chronological feed. Article listings show publication dates, estimated reading times and author names where available.
Within the published technology article, a linked contents list and a return-to-top control provide shortcuts through a longer text. The newsletter subscription form offers another way to follow the magazine and states that subscriptions require confirmation by email.
Search that supports content discovery
Relatude.DB supplies the data and search-index storage. The magazine’s published technical description identifies full-text search—matching words in the content—as the implemented approach. Public search also checks publication status before returning content.
The database also supports semantic matching, or comparison by meaning. This can help find relevant articles even when their wording differs from a query. However, the technical description presents semantic search as a possible next step, not an implemented magazine feature.
Editorial selections come first. The homepage’s editorial picks give readers a deliberately chosen route through the archive, alongside recent stories, collections and search.
Editorial selections come first.
Connecting AI assistants to the editorial workflow
Alongside these magazine features, our TinyWeb CMS offers an MCP connector. MCP stands for Model Context Protocol: it provides a connection through which compatible AI assistants can work with CMS content. Our connector supports reading published articles, preparing and editing article drafts, and adding images.
The workflow starts with a plain-language request in a compatible assistant. The resulting draft goes into the CMS, where the editorial team can edit, fact-check and refine it. Publishing remains a human decision, rather than an automatic consequence of generating a draft.
This is a TinyWeb platform capability, distinct from the public search described above. It offers a way to bring AI-assisted preparation into the content workflow; it is not evidence of a measured time saving or a specific MCP deployment at Jsme.cz.
The publishing foundation and outcome
The documented application saves related article changes together, including paragraphs, authors, tags and links. This prevents a failed database operation from leaving only part of those changes saved. Uploaded files are handled separately, with their metadata and relationships stored in the database.
The result is an operating magazine with multiple routes through its archive, editorial selections and a public newsletter signup. These are concrete publishing and reading capabilities; no traffic growth, publishing-time reduction or engagement improvement is claimed.