Back

TYPO3

From “everyone, everywhere” to clear boundaries.

Schedule a consultation Schedule a consultation

Three situations we encounter every day.

Why choose a TYPO3 partner?

  • Too many people have access to too many pages

    With dozens of editors across multiple departments, you don’t want everyone to have access to everything. Permissions set by department, per page, and per action prevent someone from accidentally publishing something that isn’t finished yet.

  • You manage multiple sites side by side

    You manage multiple sites, languages, or locations that share the same foundation but differ by location. Managing everything from a single installation saves work and ensures that changes are applied everywhere.

  • You need to be able to demonstrate how things are organized

    In government, education, and healthcare, you must be able to demonstrate who published what and whether your site is accessible. This requires a system where that information is formally recorded rather than just noted.

TYPO3 as the backbone of your organization

For a small editorial team, any CMS will do. The challenges begin when there are dozens of editors, multiple sites, and departments, each managing their own section without getting in each other’s way.

TYPO3 is the engine for that scale. Permissions down to the page level, multiple sites from a single installation, and a workflow where publishing can require approval. It’s more complex to manage than a lightweight CMS, and that’s exactly why it’s the right choice.

You maintain full oversight. It’s clear who published what and when—and that’s no minor detail in a bid or an audit.

What We Do with TYPO3

We start with your organization, not the system: who writes, who approves, and who is authorized to publish. That structure determines the structure of your permissions and workflows, and the success of the system hinges on it.

Next, we build the content model and the sites, with a shared foundation and variations by market or department. We incorporate accessibility into this, because for public organizations, it’s a requirement, not just a preference.

If you’re migrating from another CMS, we’ll transfer your content and your SEO value. The real work lies in rethinking your structure, not in the migration itself.

Three things you’ll notice during our collaboration.

Why choose Redkiwi as your TYPO3 partner?

  • Your team publishes within clear boundaries

    Your editors publish within their own sections, and you can see who did what and when. Every month, we go over what’s needed, and you decide what gets built. You stay in control.

  • Independent advice

    If you have a single site and a small editorial team, Craft CMS is lighter and cheaper to manage. TYPO3 pays off when you scale up or have strict permissions requirements. That’s exactly what we’ll tell you.

  • Since 2004, with a familiar face

    Since 2004, Redkiwi has been building websites for organizations with multiple departments and accessibility requirements. You’ll work with a dedicated specialist who understands your editorial process.

Frequently Asked Questions About TYPO3

01/ When should you choose TYPO3?
If you have dozens of editors, multiple sites, or strict requirements regarding who can publish what. If you have a single site and a small editorial team, a lighter CMS is easier and cheaper to manage.
02/ How granular can I set permissions?
Down to the page level. A department manages its own section and cannot access anything else, and publishing a post may require approval from someone else. This prevents anything from going live that isn’t finished yet.
03/ Can I manage multiple sites from a single environment?
Yes, from a single installation. They share a common foundation and differ where necessary, so you don’t have to make the same adjustment five times. That’s usually why organizations choose this system.
04/ What about accessibility?
For government and education, accessibility is a legal requirement, not just a preference. We incorporate these requirements into the content model and templates so that an editor doesn’t accidentally publish something that doesn’t comply.