Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Combine or better reference Use Cases, Ecosystem and Documentation #32

Open
marcoroth opened this issue Oct 15, 2023 · 1 comment
Open

Combine or better reference Use Cases, Ecosystem and Documentation #32

marcoroth opened this issue Oct 15, 2023 · 1 comment
Labels
content structure

Comments

@marcoroth
Copy link
Owner

marcoroth commented Oct 15, 2023 •
edited
Loading

Right now a library like "Tom Select" appears in the Use Cases section under "Select Boxes", is in the Ecosystem page under "npm packages" and also might have an entry in the "Documentation" section.

All of these ways are good to have, so one could find the information in more than one way, but all of the entries should be linked/referenced better so they all lead to the same page/information.
@sajal-123
Copy link

I want to contribute to restructuring the documentation for "Tom Select," but I’d love to know more about what specific changes you’re looking for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
content structure
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@marcoroth @sajal-123