Code contribution guideline


(Christian Müller) #1

Make sure you have read the contribution introduction.

General development documentation

Additional development documentation

  • schema
  • package overview (Neos/Flow)
  • debugging
  • scramble translations
  • logging
  • versioning strategy (Neos/Flow)
  • releasing (Neos/Flow)
  • merged composer.json
  • tools

Neos specific development documentation

  • general introduction
  • styling
  • demo site
  • code structure
    • JS backend
      • minified (built)
      • grunt
      • structure
      • browser caching
      • external API
      • jQuery
    • backend controllers
    • services
  • EEL (parser)

Flow specific development documentation

  • code structure

Other resources

When are pull requests merged

Note that you need to fork the two development collections depending on which code you want to change. We cannot accept pull requests into the READ-ONLY repositories (like https://github.com/neos/neos), these are build with the changes.

Tips:

  • FAQ section

  • TL;DR for all sections

  • ask everyone to read through, add missing stuff and comment

  • ask everyone to always refer people to the guidelines and if something is missing, add it


Code review process for pull requests
Neos shortcut: best practice for Bigpage or Section-Page with anchor?
Activity log: General (non-team related)
(Christian Müller) #2