If adding an article requires understanding fifteen technical fields, the problem may not be inadequate training. The model may have been organised around its builder’s vocabulary. I prefer to start with the work the editor actually needs to perform.

Follow an article’s lifecycle

Title and body are obvious fields. Draft status, source review, an English counterpart and future updates also matter. Important states can be lost when they exist only as informal notes inside the text.

I map the decisions one example article passes through from inception to publication. Not every decision needs a separate field, but the system should distinguish the states that affect publishing behaviour.

Make frequent decisions easy to reach

Title, summary, topic, language and body should be readily visible. Less frequently used technical settings can sit in a separate area. Simplifying an interface means ordering decisions sensibly, not removing every advanced capability.

Defaults matter too. A new article should not accidentally begin as published. An automatically generated address should be readable, and changing a title after publication should not silently change that address.

Record relationships explicitly

The Turkish and English versions should be connected through a stable relationship, not guessed from similar titles. Topics and related projects can likewise use verifiable content references rather than loosely typed names.

A bilingual publishing structure then becomes more than two folders. Language switching, search and links can draw on the same underlying relationship.

Design the update process

Which fields survive an edit? Are publication and revision dates separate? Should a small correction move an old article to the top of the homepage? These are editorial decisions with technical consequences.

The final test is a real workflow: create an article, save a draft, add an image, connect its translation, preview and revise. When the editor understands what happens at each stage, the data structure has begun to serve the publication.