typo3.org issueshttps://git.typo3.org/services/t3o-sites/typo3.org/typo3.org/-/issues2023-06-15T19:22:13Zhttps://git.typo3.org/services/t3o-sites/typo3.org/typo3.org/-/issues/606Multiple URLs for same content2023-06-15T19:22:13ZOliver HaderMultiple URLs for same contentAs a visitor, I want to access articles with unique url
Examples:
* https://typo3.org/security/advisory/typo3-ext-sa-2021-012 (correct & published in advisories, advisory ID shown in title)
* https://typo3.org/article/typo3-ext-sa-2021-...As a visitor, I want to access articles with unique url
Examples:
* https://typo3.org/security/advisory/typo3-ext-sa-2021-012 (correct & published in advisories, advisory ID shown in title)
* https://typo3.org/article/typo3-ext-sa-2021-012 (duplicate, but used by some blog posts, advisory ID missing in title)
AC:
* Security Advisories are only accessible via /security/advisory
* News Articles are accessible via https://typo3.org/article
Posssible solution: https://docs.typo3.org/p/georgringer/news/9.1/en-us/AdministratorManual/BestPractice/Routing/Index.html#using-limittopages_Ready for sprintStefan BusemannStefan Busemannhttps://git.typo3.org/services/t3o-sites/typo3.org/typo3.org/-/issues/24Integrate events with frontend editing2023-07-25T19:24:35ZThomas LöfflerIntegrate events with frontend editingAs a frontend user I like to create events
**AC:**
* [ ] creation is only allowed for logged in users
* [ ] new events are hidden by default
* [ ] events are visible, if an event of this fe_user was accepted in past
Todos:
- [ ] bui...As a frontend user I like to create events
**AC:**
* [ ] creation is only allowed for logged in users
* [ ] new events are hidden by default
* [ ] events are visible, if an event of this fe_user was accepted in past
Todos:
- [ ] build a form to submit events (currently done via ext:form)
- [x] basic event data (information, category, images)
- [x] hidden if fe_user has no approved event, not hidden if fe_user has approved event
- [ ] define mandatory fields
- [ ] configure correct filemount for event records(?)
- [x] allow to configure event date and TIME
- [ ] Location. Propose: suggest with Google Maps API Search and already existing records
- [ ] Skills. Propose: Textarea - one skill per Line?
- [ ] RTE for description (others?)
- [x] generate Slug for created event record (Finisher?)
- [ ] Backend Module for easy approving?
- [x] start-/stoptime to create an event that should not be published yet
- [ ] possibility to edit?_Ready for sprintJonas GötzeJonas Götzehttps://git.typo3.org/services/t3o-sites/typo3.org/typo3.org/-/issues/418Make list of documentation and doc landing pages on typo3.org2022-04-04T15:27:54ZspetersMake list of documentation and doc landing pages on typo3.orgI think we need to develop a homogenous concept of what should be documented on docs.typo3.org and what on typo3.org and what should link where. This includes landing pages for documentation. But, first step could be to collect a list of...I think we need to develop a homogenous concept of what should be documented on docs.typo3.org and what on typo3.org and what should link where. This includes landing pages for documentation. But, first step could be to collect a list of documentation on typo3.org
If you can add something to this list, please help._Ready for sprintspetersspetershttps://git.typo3.org/services/t3o-sites/typo3.org/typo3.org/-/issues/419Update fluid landing page2022-04-04T15:21:03ZspetersUpdate fluid landing pagehttps://typo3.org/fluid
* [x] remove link to Extbase / Fluid guide
* [ ] Add link to main Fluid documentation start page (once ready ...?)
* remove history or move it down on the page?
It might also make sense, to move the fluid page a...https://typo3.org/fluid
* [x] remove link to Extbase / Fluid guide
* [ ] Add link to main Fluid documentation start page (once ready ...?)
* remove history or move it down on the page?
It might also make sense, to move the fluid page as subpage of documentation (pid=23) and redirect /fluid to https://typo3.org/help/documentation/fluid. In a next step, the documentation page on typo3.org could be used as general documenation start page and docs.typo3.org mapped to it (but that is not decided yet, I just see that as a good idea to make docs on typo3.org / docs.typo3.org work more seamlessly).
Related:
* #418_Ready for sprintspetersspetershttps://git.typo3.org/services/t3o-sites/typo3.org/typo3.org/-/issues/532Concept of a better cross linking to documentation link2023-06-15T19:22:14ZStefan BusemannConcept of a better cross linking to documentation linkWe want introduce a better way, to cross link from typo3.org to docs.typo3.org
Questions:
* Link to master or specific version?
* Link to special uri or to a "jump" linkWe want introduce a better way, to cross link from typo3.org to docs.typo3.org
Questions:
* Link to master or specific version?
* Link to special uri or to a "jump" link_Ready for sprintStefan BusemannStefan Busemannhttps://git.typo3.org/services/t3o-sites/typo3.org/typo3.org/-/issues/462node_modules of t3olayout should be deleted2022-06-16T10:18:12ZBoris Schauernode_modules of t3olayout should be deletedI suggest to add
`- exec: rm -rf private/typo3conf/ext/t3olayout/Build/node_modules`
before the npm install task in the `.ddev/config.yaml`
So we can be sure that the build scripts won't fail due wrong versions in node_modules.
If you ...I suggest to add
`- exec: rm -rf private/typo3conf/ext/t3olayout/Build/node_modules`
before the npm install task in the `.ddev/config.yaml`
So we can be sure that the build scripts won't fail due wrong versions in node_modules.
If you agree you could give me the ticket back and i will add that._Ready for sprinthttps://git.typo3.org/services/t3o-sites/typo3.org/typo3.org/-/issues/351Single login for all typo3.org subpages2022-06-16T10:18:12ZBoris SchauerSingle login for all typo3.org subpagesPerhaps that could be done with https://www.keycloak.org/Perhaps that could be done with https://www.keycloak.org/_Ready for sprinthttps://git.typo3.org/services/t3o-sites/typo3.org/typo3.org/-/issues/610Organize and simplify knowledge base (TYPO3 101, Ultimate FAQ)2023-06-15T19:22:13ZStefan BusemannOrganize and simplify knowledge base (TYPO3 101, Ultimate FAQ)_Ready for sprintStefan BusemannStefan Busemann