t3olayout issueshttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues2022-04-04T14:46:50Zhttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/640Refactor login to Extbase and fix the automatic reload after successful login...2022-04-04T14:46:50ZThomas LöfflerRefactor login to Extbase and fix the automatic reload after successful login and logout* [ ] Use Extbase variant of felogin
* [ ] Use Fluid templates for login form on flyout and on login page (for mobile)
* [ ] Do automatic reload when successfully logged in or logged out
* [ ] Show alert messages* [ ] Use Extbase variant of felogin
* [ ] Use Fluid templates for login form on flyout and on login page (for mobile)
* [ ] Do automatic reload when successfully logged in or logged out
* [ ] Show alert messages_Ready for sprinthttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/652Add backend layout with right side menu, based on content structure2023-06-15T19:22:14ZThomas LöfflerAdd backend layout with right side menu, based on content structureExample page: https://typo3.org/project/association/contact/fields-of-responsibility
Using scrollspy: https://getbootstrap.com/docs/4.6/components/scrollspy/Example page: https://typo3.org/project/association/contact/fields-of-responsibility
Using scrollspy: https://getbootstrap.com/docs/4.6/components/scrollspy/_Ready for sprintThomas LöfflerThomas Löfflerhttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/646Move news configuration and templates to t3org_template2021-08-19T13:24:03ZThomas LöfflerMove news configuration and templates to t3org_templateAs the news extension is only used on typo3.org website, we don't need to handle templates and configuration in t3olayout.As the news extension is only used on typo3.org website, we don't need to handle templates and configuration in t3olayout._Ready for sprinthttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/633Check for libraries to replace2022-04-04T14:23:13ZThomas LöfflerCheck for libraries to replace_Ready for sprinthttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/632Check for libraries to update2022-04-04T14:23:13ZThomas LöfflerCheck for libraries to update_Ready for sprinthttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/631Check for libraries to remove2022-04-04T14:23:13ZThomas LöfflerCheck for libraries to remove_Ready for sprinthttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/622Frontend Editing2022-04-07T06:59:57ZStefan BusemannFrontend EditingAs an editor I want to edit content in the frontend
AC
* Frontend Editing is installed
* Content Elements Supports editing
* News are editable
* events are editableAs an editor I want to edit content in the frontend
AC
* Frontend Editing is installed
* Content Elements Supports editing
* News are editable
* events are editable_Ready for sprinthttps://git.typo3.org/services/t3o-sites/common/t3olayout/-/issues/620Restructure and separate templates/partials/layouts from page and content ele...2022-06-16T10:13:59ZThomas LöfflerRestructure and separate templates/partials/layouts from page and content elements<!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "bug" label and verify the issue you're about to submit isn't a duplicate.
--->
### Summary
Look for all Fluid files wh...<!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "bug" label and verify the issue you're about to submit isn't a duplicate.
--->
### Summary
Look for all Fluid files which are used by pages and content elements.
Then put all files into the folders they belong to.
Currently the file `Layouts/Default.html` is used by content elements and pages.
### Steps to reproduce
Put HTML code to `Layouts/Default.html` (which should handle pages only).
The HTML code appears on every content element as well.
### Example URL
(Add an Url where we can see the issue)
### What is the current *bug* behavior?
One layout file used by page and content elements
### What is the expected *correct* behavior?
Separate layout files and make it more clear which file is used for what.
**Acceptence Criterias**
* [ ] Clear structure for page templates
* [ ] Clear structure for content element templates
### Possible fixes
(If you can, link to the line of code that might be responsible for the problem)_Ready for sprint