Service 03
Development
Web applications and TYPO3 extensions that are well-structured, well-documented and ready for handover.
How we develop
Quality you don't have to see — but can still feel.
Technical concept
Architecture decisions (monolithic vs. headless TYPO3, extension vs. third-party), database model, interface spec.
Iterative development
Two-week sprints with a demo session. Feedback goes straight into the next sprint — no big bang at the end.
Code review & testing
Automated tests (unit, integration, E2E), manual QA run, accessibility check. No feature goes live without review.
Staging & acceptance
Staging system identical to the production environment. Formal acceptance with a checklist — a clear definition of what “done” means.
Go-live & handover
Deployment with a rollback plan, monitoring setup, developer documentation and a handover meeting with your IT.
Technology stack
We're open to technologies — not fanatical about them.
TYPO3 (LTS)
Extensions, Fluid templates, site packages, scheduler tasks — built to TYPO3 core standards, TER-ready.
Headless / Next.js
Payload CMS + Next.js App Router as a headless alternative — for universities with modern requirements.
Campus interfaces
HISinOne (REST), SAP, Shibboleth (SAML2), LDAP/AD, Alma — experience from dozens of integrations.
BITV 2.0 / WCAG 2.1
Semantic HTML, ARIA, keyboard navigation, focus management — built in from the start, not bolted on.
CI/CD & DevOps
GitHub Actions / GitLab CI, Docker, automated testing — so that deployments are routine, not an event.
Documentation
Technical documentation, editorial manual, architecture ADRs — so your IT doesn't stay dependent on us.
0+
TYPO3 extensions developed
0
projects handed over without documentation
We develop exclusively on current LTS versions (currently TYPO3 12 LTS and 13 LTS). New projects start on the latest stable LTS. We develop extensions so that they remain compatible with the next LTS jump.
Yes — always. All source code is managed in your Git repository, and you have full access from day 1. No lock-in, no black boxes.
That's our goal. We write extensions to TYPO3 core standards, with complete developer documentation, and hand them over in a handover meeting. After the handover meeting, university IT teams can typically make smaller adjustments on their own.