-
Notifications
You must be signed in to change notification settings - Fork 246
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
Improve README #196
Improve README #196
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
4 top-level sections:
- Features
- Using Shortest in your project
- Web app development
- Shortest CLI development
The content is still quite dense, and this is an attempt to improve readability a bit.
I think the audience can be split in 2:
- people looking to use Shortest within their project
- poeple that would like to contribute
With that in mind, I'm thinking of having 3 top-level sections:
- Features
- Using Shortest in your project
- Contributing
- Web app development
- Shortest CLI development
As current focus is on the CLI development, I think the order can be swapped.
```bash | ||
npx shortest # for npm | ||
pnpm shortest # for pnpm | ||
yarn shortest # for yarn | ||
``` | ||
|
||
## Quick Start | ||
### Quick start |
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.
Changed to sentence case for headings for consistency with our other projects.
@@ -194,20 +204,21 @@ vercel link | |||
vercel env pull | |||
``` | |||
|
|||
#### For Other Contributors: |
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.
Removed punctuation from headings.
README preview
pnpm shortest:dev
to test the CLI without build