TYPO3 9.5: blog (tx_t3blog) is separate from TV, editor is horrified. Need a middleware layer Claude → review → import. Planning to migrate to TYPO3 v13 in the future
Hi r/webdev,
Setup:
- TYPO3 9.5
- Main site (header, navigation, content, footer, contact form) — built with TemplaVoila
- Blog (tx_t3blog) — lives on its own, has nothing to do with TV
- Blog content is imported into the blog via an existing importer (pulls data from a content generator)
New challenge:
I need to insert Claude into the pipeline: Content generator → Claude (enhances) → Editor (review & edits) → Existing importer → tx_t3blog
The editor must never see the TYPO3 backend (especially the TV part).
What I need:
A simple standalone web middleware for the editor where they can see:
- Original text (from generator)
- Claude's enhanced version
- Final editable text
And one button: "Approve & send to blog"
Important: We're planning to migrate to TYPO3 v13 eventually. I want this middleware to not be tied to legacy stuff and be easy to carry over.
Questions:
What's the simplest way to build this middleware so that:
- Editor never touches TYPO3
- TV remains untouched
- Existing importer doesn't break
It can be easily migrated to v13 later?
How should I pass the final text to the existing importer? It currently pulls data from the content generator. How do I feed it data from Claude + editor instead — via a method call? A temporary table? A file?
Considering the future v13 migration — should I store approved articles in some neutral format (JSON, separate table) right now, so I can just grab them during migration? Or is that overengineering for the current task?
Thanks for any advice. Not touching TV, not rewriting the blog. Just need a clean bridge between Claude, the editor, and the importer — with an eye on the future.