Every TYPO3 editor training starts from the page tree again?
Your client's editors look it up instead of asking you.
You do a task once in the TYPO3 backend – say, creating a page or adding a content element. A browser extension takes a screenshot of every step, and the AI turns them into an illustrated guide. Together, the guides become your client's editor handbook: with their logo and colours, reachable by link for their whole editorial team.
The training that starts over with every editor
The same editor training, every time
Create a page, add a content element, pick an image from the file list, hide a page: on a call or on site, you explain the same basics in every project - and again as soon as someone new joins your client's editorial team.
The handbook that goes stale with the next update
The editor handbook gets written once, as a PDF with screenshots. After the next TYPO3 update or a switched extension the backend looks different - and nobody touches the document again.
The general docs show a different backend
Which modules, fields and content elements an editor sees depends on their backend group. Tutorials and the general TYPO3 docs show a backend with every permission, one nobody at your client ever gets to see.
How it works
Three steps to the editor handbook
-
1
Record in the TYPO3 backend
Ideally, log in with an editor account: then every screenshot shows exactly the modules and fields your client's editors see. Start recording in the Aveela extension for Chrome and click through the workflow as usual, including the page module, the list module and the file list. The extension never sends what you type into fields as text, and it skips password fields.
-
2
The AI writes the draft
The screens become a page with headings, numbered steps and every screenshot in the right place. You add what is different in this project - a custom content element, an approval it needs first - and publish the page.
-
3
The guides become their handbook
Every guide lands in your client's space. Together they become the editor handbook for their website - with their logo and colours, organised in chapters, with search. In the example: the website of a made-up municipal utility, built by an equally made-up agency.
What your client gets
Their own editor handbook
Every client gets their own, cleanly separated handbook as a portal, for their website and their permissions. You manage them all from one account - up to 5 clients on the Freelance plan, up to 25 on the Agency plan.
Read without an account
The editors open a share link and read - no sign-up, no TYPO3 login. To keep it private, invite them by email instead. Readers never take up a paid seat.
In their brand
Your client's logo and colours are included in every plan. The handbook feels like part of their website, not like a stranger's tool.
Under your name (Agency)
On the Agency plan, the portal runs on your own subdomain, and the footer shows your logo instead of the Aveela note.
The basics for every editorial team, the specifics for this client
The basics are the same for every TYPO3 client and take a few minutes per workflow to record - in exactly this client's backend, with their page tree and their editors' permissions instead of a generic tutorial. Add what only this project has. Both live in the same space, as separate chapters.
Basics
- Create, move and hide pages
- Add and edit content elements
- Images and files in the file list
- Preview before publishing
Specifics
- The project's own content elements
- Extensions such as news, forms or events
- Workspaces and approvals
- What each backend group may do
After a TYPO3 update or a switched extension, you re-record only the affected workflows; every other page stays as it is.
Pricing
Two plans, both with AI drafts and the browser extension. Try everything first, no credit card needed.
Freelance
19 € / month
Up to 5 client spaces with your client's logo and colours - for freelancers with a handful of TYPO3 clients.
Agency
59 € / month
Up to 25 client spaces, white label and the portal on your own subdomain - for agencies with ongoing TYPO3 projects.
All prices excl. VAT. · All prices and limits at a glance
Frequently asked questions
Do I have to install a TYPO3 extension?
No. Recording happens in the browser (Chrome), not through an interface to TYPO3. Nothing gets installed on your client's website - no extension, no backend login for us.
Don't the page module and the file list run in their own frame?
They do, and recording picks up clicks inside them like anywhere else (from version 1.3.0 of the extension): in the page tree, the page module, the list module, the file list and the backend's dialogs. To keep a state that no click leads to, use "Keep this screen" in the side panel.
Do the screenshots show what my editors see?
If you record with an editor account, yes: every screenshot then shows exactly the modules, fields and content elements of that backend group. Create an account in your client's editor group for this, ideally on the staging system.
Do the editors have to sign up?
No. With a share link they read without an account. If the guides should not be public, invite the editors by email instead; they still do not take up a paid seat.
What happens after a TYPO3 update?
You re-record only the workflows that changed and replace the affected pages with them. Everything else stays. A guide does not update itself - but it lives in one place instead of in several PDF versions sent around.
Do login details or customer data end up in the guide?
The extension never sends what you type into fields as text, and it skips password fields entirely. Only what the screenshot shows appears - and the AI is instructed not to take names of people, companies or addresses from recordings. You review the draft before publishing it.
Is there a ready-made template for the TYPO3 basics?
No. You record the basics in each client's backend - it takes a few minutes per workflow and shows their page tree, their content elements and their editors' permissions instead of a sample.
Does it work for multilingual websites?
Yes. You maintain a space's content per language, and the AI drafts the translation of a page for you to review. Aveela's interface is available in German and English.
Aveela compared
Ready to give your clients a portal of their own?
Set up your first documentation portal in minutes - 14 days free, no credit card.