Rewrote the docs structure. #509
Conversation
…helper to compose markdown in markdown.
… EduardoLopes/new-website
|
I think we'll want to remove the manual cloning/build instructions. It's confused a lot of people. We should keep some of that only in the contributing docs. We actually already have a release published to npm under |
|
(That's just a general unrelated criticism of the current docs, your changes look great!) |
|
|
||
| Rome is not available via `npm` and must be installed from GitHub. | ||
| In a folder of your choice, clone the `rome` repository: | ||
| Rome is currently not available via `npm`, and must be installed from GitHub. In a folder of your choice, clone the `rome` repository. |
There was a problem hiding this comment.
Rome technically is available through npm with yarn add rome@^0.0.25 or npm install rome@^0.0.25. Not sure if its premature to add it in the docs though. Either way, I thought I'd point that out.
|
Most of the documentation in this PR is straight out ported from the Docusaurus build, with the difference that the headings should better fit the single page structure. Due to us moving to this format, the sidebar became a whole lot more important. @sebmck I'll rewrite the The final result ends up here: #507 |
Co-authored-by: Kevin Kelbie <[email protected]>
Co-authored-by: Kevin Kelbie <[email protected]>
I've cleaned up the structure of the docs in order to better match a single page.