Restructure of docs, ordered stages

[reespozzi]

This change (hackathon away day):

• Restructures docs into stages that follow logical order for devs

Does this PR introduce a breaking change? (check one with "x")

[ ] Yes
[ ] No

[timja]

I think troubleshooting seems better, although there is some benefit to being able to search on a single page

see my feedback below

---

This loses the nesting for the different platforms at the top level.

I'm not sure if we want to do that given we just implemented that very recently, cc @linusnorton

The concepts and standards seems a bit random with angular at the top but the content doesn't fit in there and very few need to read it.

Before it was at the bottom and more out of the way:

Database schema changes seems out of place in it's current section

Troubleshooting and guides seems duplicated with guides in new component as well?

[adusumillipraveen]

Links in here are broken, may be in other sections too

[adusumillipraveen]

will be good to have this left hand navigation for onboarding include sub sections

[adusumillipraveen]

Does environments belong in new components? can we move them to Path to live may be ?

[linusnorton]

The intention was to promote the HMCTS Way as a set of standards and documentation that apply across all of HMCTS with things like Standards that apply everywhere at the top level and the specifics of each platform in their own section. That said, it's a fairly recent change and not too late to back out of if you don't like it.

If we do stick with the current top level structure I think are things that could be moved out from Cloud Native Platform and applied across all of HMCTS. Onboarding is a good example. Going forward the expectation is that everyone using the HMCTS GitHub org. Crime are migrating across at the moment.