We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FileTree
Currently the easiest way (excluding custom components) to visualize a directory structure is to use an ascii-based tree as follows:
your_app/ ├── pubsepc.yaml ├── lib/ ├── ... └── widgetbook/ ├── pubsepc.yaml ├── lib/ └── ...
Providing first-class support for this might be a good idea, to make docs more visually appealing. Here are some examples:
Nextra's FileTree - Simple and interactive file tree.
From Next.js docs - They have a more visually appealing style, they use images instead of components to be able to annotate their images.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently the easiest way (excluding custom components) to visualize a directory structure is to use an ascii-based tree as follows:
Providing first-class support for this might be a good idea, to make docs more visually appealing.
Here are some examples:
Nextra's
FileTree
- Simple and interactive file tree.From Next.js docs - They have a more visually appealing style, they use images instead of components to be able to annotate their images.
The text was updated successfully, but these errors were encountered: