--- title: TYPO3 Neos Technical Discussion August 20th url: "https://news.typo3.com/article/typo3-neos-technical-discussion-august-20th" description: "Today we had another technical discussion meeting for TYPO3 Flow and Neos. Two topics were discussed: the TypoScript folder as well as the usage of event sourcing in workspaces." image: "https://news.typo3.com/_assets/d1e01514e4c4a5b3147940fa2ec50682/Images/og-image-news.jpg" date: 2026-06-11 modified: 2026-06-11 categories: - "Developer & Technology" - "Showcase & Success" --- # TYPO3 Neos Technical Discussion August 20th - [Showcase & Success](https://news.typo3.com/article/category/showcase-success) - [Developer & Technology](https://news.typo3.com/article/category/developer-technology) TYPO3 Neos Technical Discussion August 20th =========================================== 20 August 2013 Today we had another technical discussion meeting for TYPO3 Flow and Neos. Two topics were discussed: the TypoScript folder as well as the usage of event sourcing in workspaces. - ![](https://news.typo3.com/typo3temp/assets/t3g/blog/gravatar/bbf959d8e683550c90ae922aff9145d8.jpeg)[Berit Hlubek](https://news.typo3.com/article/author/berit-hlubek) TypoScript folder ----------------- Neos stores TypoScript in *Resources/Private*, TYPO3 CMS with Extbase has the convention to store it in *Configuration/TypoScript*. In case of Neos somehow it makes sense to have it in *Configuration*. We wanted to discuss that topic as it would be a breaking change to move the TypoScript. **Conclusion:** In contrary to TYPO3 CMS in Neos we don’t use TypoScript (exclusively) for configuration. Thus we keep the current folder structure (for now) being: - Resources \-- Private \--- TypoScript \---- Libraries (optional) Usage of event sourcing in workspaces / history ----------------------------------------------- *CQRS / ES* has been discussed for a few times now (also with Thomas, Sebastian and Robert) so we tried to put some thoughts on paper. It seems now that it might be an interesting approach for making a publish less error prone, it could be used for shine through nodes and could be the basis for a full history of content changes. It would be good to discuss if it makes sense to actually do a prototype based on those ideas. **Conclusion:** Sounds like a great idea that enables neat features like Undo/Redo and it reduces the chance for merge conflicts. This won't make it into 1.0 most probably, but Rens keeps investigating and tries implementing a first prototype as soon as possible. ***The next technical discussion meeting is scheduled for September 3rd, 3pm CEST at *** ![](https://news.typo3.com/typo3temp/assets/t3g/blog/gravatar/b5c88386e5b1d8fca79d0652427922d2.jpeg) About the Author [Berit Hlubek](https://news.typo3.com/article/author/berit-hlubek) [More posts by this author](https://news.typo3.com/article/author/berit-hlubek)