Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plan for systematic review (current master) #296

Open
sypets opened this issue Jul 21, 2019 · 0 comments

Comments

@sypets
Copy link
Contributor

commented Jul 21, 2019

Once a chapter has been reviewed and corrected, it can be checked off.

Here, we focus on following goals:

  1. is text correct and up to date
  2. 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.
  3. 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
  • 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
    • Conclusion
  • backend modules
  • command controllers
  • property mapper
  • error action (was just added)
  • coding guidelines
  • extbase reference

shorten

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 (in progress ... #296)
    • Conclusion
  • backend modules
  • command controllers
  • property mapper
  • error action (was just added)
  • coding guidelines
  • extbase reference

sypets added a commit to sypets/TYPO3CMS-Book-ExtbaseFluid that referenced this issue Jul 22, 2019

sypets added a commit to sypets/TYPO3CMS-Book-ExtbaseFluid that referenced this issue Jul 22, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.