The v3 website will use the files in the docs folder of a track. This is similar to how the current (v2) website works. Examples of files in the docs folder are INSTALLATION.md ,ABOUT.md and SNIPPET.txt. In this PR, I've copied the latest version of the v2 docs folder to each of the v3 tracks's docs folder. This will allow us to use the information in this docs folder and show it on the v3 website.
Once we're ready to explode this repo back to the track repos, each track can indicate if they want us to copy over the docs folder from the v2 repo or to just keep the docs in the v3 repo. If you don't plan on updating the v2 docs, you could directly edit these docs in the v3 repo.
Note: I've excluded the docs folder from being linted/formatted by prettier for now. I don't know if people would want that :)
The v3 website will use the files in the
docs
folder of a track. This is similar to how the current (v2) website works. Examples of files in thedocs
folder areINSTALLATION.md
,ABOUT.md
andSNIPPET.txt
. In this PR, I've copied the latest version of the v2docs
folder to each of the v3 tracks'sdocs
folder. This will allow us to use the information in this docs folder and show it on the v3 website.Once we're ready to explode this repo back to the track repos, each track can indicate if they want us to copy over the docs folder from the v2 repo or to just keep the docs in the v3 repo. If you don't plan on updating the v2 docs, you could directly edit these docs in the v3 repo.
Note: I've excluded the docs folder from being linted/formatted by prettier for now. I don't know if people would want that :)