-
Notifications
You must be signed in to change notification settings - Fork 6
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.
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
Create a demo site #3
Comments
On the homepage, have two buttons for a "choose your path" where the first option is marked as recommended for people who want to write classes like The second path is for people who want to use the |
Features (goal: 6) to brag about: |
Wow, definitely using this one. One quick note: Sidebar is way bigger (it's like 500px or more) & the main content is smaller. I was looking at the table comparison with other libraries & had to scroll way too much to find this library in the table. I'd appreciate to see more main content than sidebar or make the sidebar toggleable :) Gitbook is a good example on sidebar & content → https://docs.gitbook.com/ or just see Tailwind → https://tailwindcss.com/docs See for yourself: |
Hi, thank you for your interest in the project! The main "article" content is locked to a readable width because of tailwindlabs/tailwindcss#2574. What are your thoughts on that? |
Hey @JakeNavith I think it's absolutely correct for articles to be But I think as this isn't a blog post rather a docs, I'd generally copy popular sites docs like Gitbook & Tailwind mentioned above. The sidebar should be a certain width & even 300px looks like a lot & the demo site currently is 500px on my Mac. In any case, I'd prefer Gitbook or Tailwind-style as it's more readable & looks clean. Yours is readable as well. Just the sidebar looks weird & the comparison table contains too many things. And please put your library in the 1st column in the table as I had trouble finding it :) |
Since this plugin is all about visuals, it'd help a lot to have a site showing off just what this plugin can do 😎
The text was updated successfully, but these errors were encountered: