Contribution documentation improvements

[nirname]

📑 Summary

Brief description about the content of your PR.

Related #2910

📏 Design Decisions

• Tutorials moved to ecosystem because they are seemed not to be not officially supported
• All the pages development.md, docker-development.md, code.md and documentation.md are combined together and refined, and named contributing.md.
• CONTRIBUTING.md is now a symlink to our documentation
• Added introduction page for contributing based on Collaborators wanted! #866 so as to purify contributing guide and describe other ways of participating in project
• Link to contributing removed from versions sub-menu, because it is already there at the top bar
• I noticed that in many cases we used right sidebar with all the heading included. Now displaying all the levels of heading at the right sidebar is the default behaviour. This will make access to the sections easier and enforce better planning while writing documentation so as to avoid extra headings.
• I am not sure how many people are using GitHub directly to contribute to documentation, but I think that keeping section on "how to use Github features" is an extra for our contributing to documentation guidelines. Anyway, the overall contributing process is the same regardless of what a developer prefer - GitHub UI vs his favorite editor
• Removed recommendation to contribute directly to development branch for docs and opening PR-s targeting master branch. My thoughts that these exceptions only make process more complicated. Better keep it uniform
• Documentation section is partially intersects with Tidy up contribute to docs page #4899 and that is why it was taken as a reference in some sense
• Advanced section of configuration was removed because it was empty. Some TODO's are removed as well, because they looked messy

📋 Tasks

Make sure you

• 📖 have read the contribution guidelines
• 💻 have added necessary unit/e2e tests.
• 📓 have added documentation. Make sure MERMAID_RELEASE_VERSION is used for all new features.
• 🔖 targeted develop branch

[netlify]

✅ Deploy Preview for mermaid-js ready!

Name	Link
🔨 Latest commit	36fdff8
🔍 Latest deploy log	https://app.netlify.com/sites/mermaid-js/deploys/65a5065fdc521b0008425907
😎 Deploy Preview	https://deploy-preview-5132--mermaid-js.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (dc857f8) 43.04% compared to head (bafb991) 80.17%.

❗ Current head bafb991 differs from pull request most recent head 36fdff8. Consider uploading reports for the commit 36fdff8 to get more accurate results

Additional details and impacted files

@@             Coverage Diff              @@
##           develop    #5132       +/-   ##
============================================
+ Coverage    43.04%   80.17%   +37.12%     
============================================
  Files           23      167      +144     
  Lines         5018    13873     +8855     
  Branches        21      707      +686     
============================================
+ Hits          2160    11122     +8962     
+ Misses        2857     2598      -259     
- Partials         1      153      +152     

Flag	Coverage Δ
e2e	86.18% <ø> (?)
unit	43.04% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 163 files with indirect coverage changes

[nirname]

@sidharthv96 fixed everything, unless I had missed smth. I have a question. Some of our docs do not need mermaid code to be compiled and embedded on the page along with diagram, because diagram is only for description of the document not for description of the syntax. Thus I used mermaid-nocode keyword. But GitHub does not support that, so when using diagram solely for illustrative purposes I face a dilemma:

• avoid diagram code embedded in the doc but sacrifice GitHub contributing guidelines appearance
• put up with the extra code on the documentation website but support those who are using GitHub UI
  

Ideally I would support both, but then we have to change MERMAID_EXAMPLE_KEYWORDS to something else. And that will influence other parts of documentation as well. So I decided to tackle this problem separately and after a discussion. Right now I can get rid of mermaid-nocode in my examples if needed.

[sidharthv96]

In this specific case, I'd prioritize the website user over the GitHub one. Although, the website user seeing the code might not be a major issue.

Wonder if this could help. If the markdown parser gives us the full text, that would fix our problem.

```mermaid nocode
flowchart
a --> b
```

[nirname]

I think we will leave mermaid-nocode for now, not a big deal if someone won't see very simple and not really important diagram on GitHub directly. Lets address those keywords separately

[sidharthv96]

I have fixed the build.

[nirname]

@sidharthv96 updated branch so build works now

[nirname]

@aloisklink I remember you were asking to make CONTRIBUTING.md to be exactly the same as our website contributing documentation and combine everything in one page. This PR does exactly what you were looking for

[huynhicode]

@nirname Great job

Perhaps we can remove the "Contributing" link from the dropdown since there is a link in the Navbar.

[nirname]

@huynhicode Yep, already removed