-
Notifications
You must be signed in to change notification settings - Fork 148
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
Docusaurus v1 site #341
Docusaurus v1 site #341
Conversation
add deps for docusaurus rendering
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
size-limit report 📦
|
this is awesomeness! always wanted this package to have a proper doc site 😸🙌❤️ |
Thanks @hartzis . I'm going to keep polishing it up a bit. Curious if you have any thoughts for improvement? I was considering updating the examples to use a different carousel potentially that we can just pull straight from npm, or even |
Lookin' good! Found a couple things, flagged 'em in vercel comments mostly. one of them might also be on Nuka and I just missed it. Good catch with the dueling versions for usage. I think that would be a great thing to work on if you find yourself blocked by needing review here tomorrow. Holler when you're ready for a second pass. Looks so great! |
@BrittanyIRL Thanks for reviewing. The only remaining issue right now is with the Copy button looking weird on Safari. I'll keep working on that tomorrow. I left the other vercel comment open for you to review and close if you think it's fixed on your iPhone 13 mini. From what I can tell, it seems fixed. The node version issue shouldn't be a blocker for releasing this. It's just kind of confusing, but shouldn't prevent the PR from being approved and merged as I was able to get CI working by putting in a couple of other fixes. However, I do think we should do a follow-up PR to get node18 working which will probably require a major or minor release depending on what we have to do. |
Here's a fix for the buttons: FormidableLabs/nuka-carousel@2275109 Thanks for clarifying, I don't mean that the node update needs to be part of this update I just mean that it's a valuable update that isn't blocked by review of this branch since it's its own thing :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🙌 woo woo!
📓 on the node upgrade: we should really try to avoid a major bump for a dev dep unless there is something fundamentally changing in the output which i don't think should be the case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the changes!
Description
New Vercel Site
Existing github pages site
Search plugin added
Adding a new Docusaurus Documentation site. The content of the new site has been extracted from the already excellently written
README.md
file and put into the /docs portion of the site.I also got the examples from the example app working within the documentation. However, I left the old examples repo in place in case users want to run locally instead.
Things left to be done (open to suggestions)
Landing Page
Documentation site
Other
react-swipeable
doesn't currently work with node 18, so you need to be on 16 when running the demo app locally. However, the docs site (using Docusaurus framework) requires at least node 18, so you have to currently switch between node versions. I can work on fixing this. 🚧 Will do this in a separate pr 🚧Type of Change
Documentation
How Has This Been Tested?
mobile:
api docs:
working demo:
Checklist: (Feel free to delete this section upon completion)