-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Documentation improvement #1038
Comments
Thanks for the feedback. The individual module CDN links are located on the Customize page (https://purecss.io/customize/#individual-modules). When you refer to "releases", are you talking about the npm package or something different? |
Thanks, I didn't noticed it there! well, releases as they are right now it's only the npm packages, but I myself am not using node. I was looking for the build files themselves, and I had to individually copy/paste/save the links from the CDN snippets. It would be useful (for me, at least) if I could download the min files in a zip and host on my server. |
Good feedback, so GitHub has the releases zip file that they provide when a release is published. I can look at adding the built files into that too. |
For reference, I just found this action that might be a good fit: https://github.com/marketplace/actions/upload-files-to-a-github-release |
Is your feature request related to a problem? Please describe.
No problem here, just missing info from documentation.
The docs give CDN links to the base and grid css, but I can't find the forms one, and the releases also don't include the built files, so if I want to download the minified files I have to find the CDN link and download from there.
Describe the solution you'd like
I suggest putting all available CDN links in one place, so it's easier for people that just want to include and start using them. Also include the minified files in the releases in case someone wants to download and serve the files them selves.
Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: