Plan for systematic review (current master)
Closed this issue · 1 comments
sypets commented
Once a chapter has been reviewed and corrected, it can be checked off.
Here, we focus on following goals:
- is text correct and up to date
- shorten text, remove historical references to Fluid, Neos, Pibase etc, if they are not relevant and helpful for learning extension development and only result in bloating up the text. The text is currently quite long and partly not well readable.
- correct language (grammar, spelling, style), correct some phrases (that probably suffered during translation) and are really difficult to understand (e.g. Programming Secure extensions)
check off relevant section once ok
correct, up to date
for master (10-dev) - July 21, 2019
- about
- introduction
- basic design principles - not TYPO3 version specific, should be basically ok
- journey blog example
- installation
- creating a first extension (see #231)
- modeling the domain
- persistence layer
- controlling the flow with controllers
- styling the output with fluid
- configuration (was just added)
- internationalization
- localization
- validating domain objects
- Programming secure extensions
- Conclusion
- backend modules
- command controllers
- property mapper
- error action (was just added)
- coding guidelines
- extbase reference
shorten text (remove redundancies)
for master (10-dev) - July 21, 2019
- about
- introduction
- basic design principles
- journey blog example
- installation
- creating a first extension
- modeling the domain
- persistence layer
- controlling the flow with controllers
- styling the output with fluid
- configuration (was just added)
- internationalization
- localization
- validating domain objects
- Programming secure extensions (in progress ... #296)
- Conclusion
- backend modules
- command controllers
- property mapper
- error action (was just added)
- coding guidelines
- extbase reference
fix language (spelling, grammar, style), make more readable
for master (10-dev) - July 21, 2019
- about
- introduction
- basic design principles
- journey blog example
- installation
- creating a first extension
- modeling the domain
- persistence layer
- controlling the flow with controllers
- styling the output with fluid
- configuration (was just added)
- internationalization
- localization
- validating domain objects
- Programming secure extensions (#296)
- Conclusion
- backend modules
- command controllers
- property mapper
- error action (was just added)
- coding guidelines
- extbase reference
sypets commented
I am closing this now because:
- there are issues adressing the structure and further work reviewing does not make sense before that is handled IMHO.