Road to Product-First Docs

[mason-at-pieces]

We are changing the structure of our docs to be Product-First rather than Feature-First, which it currently is.

We will be following the Diataxis framework for the new structure and content

TODO:

• [x] Raycast
• [x] Pieces CLI
• [ ] Neovim
• [ ] Sublime
• [ ] VS Code
• [ ] Visual Studio
• [ ] JetBrains
• [ ] Web Extension
• [ ] Obsidian
• [ ] Azure Data Studio
• [ ] JupyterLab
• [ ] Teams

Here is the proposed structure for each product:

• Product (vs code, jetbrains, etc.)
  • Overview (landing page that shoots out to the below resources)
  • Quickstart (tutorial)
  • [ ] Install & Save Snippet during Quickstart
  • Features (reference, can have subpages)
  • Guides (how-to)
  • Explanations (explanations)
  • *If any features are more complex or something we want to explain the process of how we do it, then we can have that here