MANAGE IT

Service · Portals & advanced CMS systems

A portal for the audience. A CMS for the people who run it every day.

A fast public portal is only worth it if the newsroom can manage content safely and efficiently. We build both sides of the product: the reader's experience and the working tool of authors, editors, marketing and administrators.

The problem we solve

When everyone has too many permissions, publishing becomes risky. When they have too few, content gets stuck with a single person.

A good CMS clearly defines who writes, who edits, who approves, who publishes and who manages ads. It also has to keep versions and allow rolling back to an earlier state.

Who it's for

  • Media houses and specialised portals
  • Institutions and organisations with an editorial workflow
  • Companies with large volumes of content

Key capabilities

  • Editorial workflow: draft → proofreading → approval → publishing
  • Authors, editors and an editor-in-chief with distinct permissions
  • Categories, media library, comments and subscribers
  • Ad positions and campaign management
  • SEO fields, slug, social media and structured data
  • Readership statistics

A real project

Poljoprivrednik — portal, CMS & classifieds

Modernising a media institution: a public portal, an editorial CMS and classifieds with commercial modules.

View case study
CMS — NewsroomPending: 1

New regulation on production subsidies

Author: M. J.Approved

Report: agriculture fair

Author: A. K.Proofreading

Grain market analysis

Author: S. P.Draft

Posts today

0

Ad positions

P1–P7

Our process

01

Analysis of the editorial flow and roles

02

Information architecture and portal design

03

Development of the CMS and the public side

04

Content migration and newsroom training

Integrations

  • Newsletter and email campaign services
  • Social media and automated posting (per APIs)
  • Ad systems, positions and campaigns
  • Weather, exchange rates and external data

How onboarding looks

Redesigning a large portal must not erase years of organic traffic. Before migration we map existing URLs, categories, media and metadata. The new system keeps valuable addresses where possible, and changes are covered by 301 redirects. After launch we monitor indexing errors, canonical tags and key pages.

Technologies

Next.jsHeadless CMSPostgreSQLElasticsearch / searchCDN

Frequently asked questions

Can we migrate our existing article archive?+

Yes — migrating the archive while preserving URL structures and SEO value is a standard part of the project.

How are ad positions managed?+

Through the admin: positions, campaigns, schedules and impression statistics — without touching code.

Let's talk about your project.

Request a quote