Add docs for the NuGet package
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 175k
- Forks
- 78.6k
- Avg merge
- 7h 19m
- Merged PRs (30d)
- 35
Description
For .NET developers NuGet packages are god-sent to not install npm or anything from JS ecosystem.
A simple README.md at https://www.nuget.org/packages/bootstrap.sass of how to setup for example with EmbeddedSass.Net or AspNetCore.SassCompiler would help a lot.
Alternatively simply give instructions of just how to unpack the .scss files.
Im digging on how it works, would you accept a PR with a README.md?
Also in my opnion as a .NET developer, these docs are wrong, because with the packages I mentioned, you can compile the front-end assets from back-end.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the NuGet package page and the requested README.md scope, then review the existing package documentation. Check the EmbeddedSass.Net and AspNetCore.SassCompiler references, and document either a .NET compilation setup or how to unpack the .scss files; done means the package page has usable instructions for .NET developers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sass, scss
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- Half a day
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100