New docs

[kof]

• Move all packages docs to /docs
• Compare the changelog with the docs
• Update all docs where plugin names are mentioned, plugins order needs to get new extracted plugins into the list
• Update polyfills list here
• Create Changelog
• Default Preset should fetch all syntax files and render on one page?
• Check all links after moving files

New contents

• Write v10 migration guide
• Write Introduction, reduce the main readme.md
• Rewrite benefits.md
• CDN links
• Write tradeoffs.md
• Update pereformance.md
• Write Getting Started
• Write Hello World
• Write FAQ
• Write articles.md with a list of all known articles
• Rewrite and improve or remove links to my medium articles

Structure (inspired by react docs)

Installation

• Getting Started
• Setup
• CDN Links

Main Concepts

• Introduction
• Hello World
• Benefits
• Tradeoffs

Advanced Guides

• SSR
• CSP
• Performance
• CLI

API Reference

• Styles Syntax
  • Core
  • Default Preset
• JSS
• React-JSS
• Styled-JSS
• Plugins
  • jss-plugin-x
  • jss-plugin-y

Contributing

FAQ

Community

• Chat
• Projects
• Articles
• Courses
• Podcasts
• Examples
• Videos

[eps1lon]

Removing the readmes from the packages does have the downside that you won't have any displayed on npmjs.org: https://www.npmjs.com/package/jss-plugin-vendor-prefixer

The individual package.json also don't have a repo listed at the moment which again causes trouble with npmjs.org. Packages usually have a link to their repository on their page on npmjs.org.

Just wanted to let you know in case this was not intended.

[HenriBeck]

Good catch. I think we should just copy the docs when releasing but ignore them in git.

[HenriBeck]

Also, we should remove all of the version which are <= 9 from the dropdown on the docs page because you end up at a NotFound page

[kof]

Regarding readme.md, lets do the same thing as babel: https://www.npmjs.com/package/@babel/plugin-syntax-export-namespace-from

Regarding docs: its broken right now. My original plan was to publish the 9th version as a subdomain and when dropdown selects v9, switch to that subdomain. I am not sure though its worth the effort and maybe we should just remove v9 from the docs.

cc @oliviertassinari

[HenriBeck]

👍
I will create a script for creating the readme then

[kof]

@HenriBeck its not a full readme, its just title, link to the docs on the website and install steps. I think it is manually created for each package.

[HenriBeck]

Yeah, we can automate that 🤔

Just generate them before the release and they don't even need to be in git
I would like to do the same with the licenses inside the packages

[kof]

I think you want them to be in git even if you generate them, for the case someone lands there over github link