A content platform editors cannot break.

Portal CMS in numbers

• An agency built our site. We call them for every change.

  Building a page, defining a collection and changing a menu need no deployment; the editor does it from the panel and publishes.

• WordPress became plugin on top of plugin; the design broke within three months.

  The block catalogue is code. The editor places designed sections; no HTML or CSS, no arbitrary colours. The site still looks as designed three months later.

• We hand out member documents as Drive links and have no idea who sees what.

  Audience is inherited from the folder, every download is logged, and files open through 5-minute signed URLs.

• A member company left. Its staff can still sign in.

  Closing access is enforced in three places at once, and the confirmation box names everyone whose access is ending.

• The SEO agency pasted JSON-LD. A year later nobody knows what it does.

  Structured data, sitemap, hreflang and canonical are generated from code. The only thing the editor can touch is a six-field card.

• We write the weekly bulletin in Word. Moving it to the site takes half a day.

  Paste from Word and the images upload on their own; heading and list structure is kept.

Two languages: Turkish at the root, English under /en. A record without a translation is not hidden; it shows with a "not translated" label, and a new translation is copied from the structure.

• Invite-only, closed area

  Accounts open only by invitation from the panel: a single-use link valid for 72 hours. Sign-in by password or email code. You know who is inside at all times.

• Closing access is one button

  Mark an organisation as "left" and the confirmation box lists by name everyone who will lose access. Once confirmed, it is enforced in three places at once; open sessions close too.

• Who sees what: one answer

  Six audience types (everyone, role, category, organisation, team, person) are inherited from the folder tree. A document without an audience cannot be published; if a folder has no open document in its subtree, not even its name is returned.

• Signed downloads, logged trail

  Files sit in private object storage and open through a 5-minute signed URL. The download record is written before the URL is generated; an external short share link carries an open counter and an expiry date.

• Announcements, events, surveys, teams

  Announcements use the site's block editor; events are online, in person or hybrid with a reminder 24 hours before; surveys link to an external form; deleting a team never widens access.

• Notifications and unified search

  Push and an in-app inbox, triggered by announcements, documents, events and reminders. One search box scans six buckets and returns only what you can see.

Scale: thousands of documents, hundreds of users; in the reference install the audience filter over 1,300 documents takes 15 ms.

• Text generation

  Summaries, meta descriptions and the sibling text in the other language are written in the brand voice; the voice changes from the knowledge base, no deployment needed.

• Image generation

  A preset per image slot: target size and crop live in the preset, the agent changes the brief and cannot change the geometry.

• SEO research

  Keyword, intent, SERP and difficulty; the per-call cost is written in the tool description.

• Semantic search

  Content and records are indexed with meaning vectors (embeddings); the agent searches for "something like this" instead of having to hit the keyword.

The agent produces, a human decides: every write a draft, every publish a human approval, every step logged.

• Associations, chambers, unions, federations

  Member-only documents, announcements and events; general assembly documents, bylaws and regulations in one place.

• Franchise and dealer networks

  Dealer-only documents and campaigns; when a dealer leaves, its staff's access closes with one button.

• Educational institutions

  Parent and student portal, course documents, announcements; audiences by class or programme.

• Consulting and law firms

  A client-specific file area, signed downloads and a download log; access closes when the client leaves.

• Manufacturers and distributors

  Dealer and service portal, technical document library, product announcements and a training calendar.

• Industrial zones and business parks

  Announcements, documents and events for participant companies only; audiences by organisation, every download logged.

• Holdings and group companies

  Corporate site and subsidiary portal from the same panel, with brand and terminology adapted.

• Foundations and public-adjacent institutions

  Institutions required to keep data on their own server; external services for delivery only.

1. 01

   Discovery

   Needs, collections and the member model are mapped together.

2. 02

   Adaptation

   Brand, terminology, collections, blocks and the member area take shape around your organisation.

3. 03

   Installation

   A single-script install on your server; external service accounts are opened in your name.

4. 04

   Data migration

   The old site, documents and redirects are moved; old URLs are kept with 301s.

5. 05

   Training

   Editor and admin training; the built-in help stays in the panel.

6. 06

   Operations support

   Deployment, backups and updates are operated by Internative.

Price and timeline by proposal per project; the discovery call is free.