Mis-leading "client-side" text
Nobody has claimed this yet.
- Dominant language
- Less
- Stars
- 680
- Forks
- 442
- PR merge metrics
- No merged PRs in 30d
Description
I still think this is misleading on the website:
LESS runs on both the server-side (with Node.js and Rhino) or client-side (modern browsers only).
Everyone I know in web-development would assume that saying "LESS runs client-side" means it's good to go for production, when what we (currently) mean here is that you can test it in the browser.
How about:
LESS compiles on the server-side (with Node.js, Rhino, and others), or you can easily try it client-side (on modern browsers).
"Try" implying "testing"
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
Locate the quoted “client-side” sentence in the less-docs website content. Update the wording so server-side compilation is distinguished from trying LESS in modern browsers, then verify the rendered documentation communicates that distinction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100