TYPO3 website development
A website your team can maintain without a manual.
A TYPO3 website your editors actually like
Most TYPO3 projects do not fail on the technology. They fail because nobody enjoys maintaining the content. So we build the editorial concept first and the design second.
The difference is concrete. Instead of a handful of universal elements into which editors can tip arbitrary HTML, every kind of content gets its own element with its own fields. A teaser has a field for the title, one for the text and one for the target — not a single rich text field that has accumulated five different formatting styles after two years.
What you get
- A sitepackage of your own. Not a bought-in theme you never quite get rid of and whose updates overwrite your changes.
- Content Blocks instead of walls of text. Every element has clearly named fields, a preview in the backend and a short description of what it is for.
- Accessibility from the start. Retrofitting costs considerably more and still tends to leave gaps.
- Core Web Vitals in the green. On a mid-range phone over mobile data too, not just on laptop Wi-Fi.
- Multiple languages where you need them. Handled properly through the TYPO3 language management with clear fallback rules — not as a second page tree.
- Deployment and documentation. A scripted path from the development to the live environment that somebody else can run too.
How we go about it
We start with a content inventory: which page types really exist, which elements are genuinely used, what has accumulated over the years and will never be used again. That list becomes the set of Content Blocks — usually a good deal smaller than everyone expected.
Then the sitepackage is built: templates, SCSS, JavaScript, backend layouts, TypoScript. In parallel the editing environment is opened up so that your team can start entering content while we are still building. That shortens the overall schedule considerably, because filling the site does not become the bottleneck at the end.
Before go-live we check against a fixed list: contrast, keyboard operation, heading structure, load times, redirects, sitemap, robots.txt, error pages, and forms with real test submissions. You get the results in writing.
Who this suits
Companies, institutions and associations that already use TYPO3 or choose it deliberately — typically from the point where several people maintain content, several languages are involved, or interfaces to other systems exist. For a five-page business-card website TYPO3 is the wrong tool, and we say so.
Questions about website development
Can we keep our existing design?
Yes. Where a corporate design exists we implement it; where an existing website serves as the model we rebuild it and tidy up what has accumulated over the years. Where a design detail collides with accessibility — insufficient contrast being the classic — we show an alternative that preserves the look.
Do we need a separate editorial manual?
Usually not. Every content element carries a short description in the backend of what it is for, and every field has help text. Anything beyond that we cover in a half-day training session on your own website — which in our experience sticks better than a PDF nobody opens.
Who hosts the website?
You decide. We work with several Swiss and European hosting providers and set the environment up, or we deliver into your existing infrastructure. All that matters to us is a current PHP version, SSH access and the ability to deploy by script.
A website project in mind?
Tell us about it. The first conversation costs nothing and takes half an hour.