-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Local setup guide #50
Comments
@svinkle Thank you for your question! The local setup is pretty minimal at the moment, we haven't had a chance to build a local playground for testing code changes. This is definitely on our list and will be addressed! If you want to watch for code changes you can use In terms of accessibility, we are currently working on an out of the box solution that can be further enhanced by the user. We've been addressing a number of issues in the |
@tsov I see that webpack builds the For accessibility issues, I'll keep watch on #48 but may create some specific issues of my own, if I get this up and running locally. 🙂 |
@svinkle I keep all of the source files for the site in a separate, private repo. I'm hoping to throw some barebones examples together to be hosted in this repo. I think it will be a lot easier for folks to experiment with the library without all the additional code for the site (although admittedly its currently impossible when I don't provide any examples...) By the time we do a stable release, I hope to have at least of a few examples available. |
Closed by #118 |
Hi! I'm looking to send in some issues and PRs regarding accessibility, but before I do that I need to know how to set things up locally!
I have the project forked and cloned, and I'm running a local Python http server on the
gh-pages
branch, as that branch includes theindex.html
file.My question is, when I make a change do I need to run
npm run build
after each save in order to see my changes? If so, perhaps we could implement something like browsersync to automatically run the build on save?Thanks for the assist!
The text was updated successfully, but these errors were encountered: