Add pages to discuss flow dev guide #92
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In my company, my colleagues use Node-RED broadly. And we have written flow development guidelines for developers.
We think these contents are useful also for all Node-RED users. So, I think that it would be better to prepare new pages or sections on Node-RED web site for providing these practices.
I edited the flow development guideline to markdown file for discussing chapter composition.
This PR is for adding documents as official doc of Node-RED.
Ask
Please comment if you have some ideas or opinions.
Contents
These files only contain chapter composition. The descriptions of each section are written as italic font.
I have not added specific contents of this flow development guideline yet.
The contents of each section will be added after finished the discussion about chapter order at end of February.
I think that it is more efficient to edit and summarize guideline that order.
I expect other users to share their opinions about these documents.