- Good use of badges (build passing, etc), emojis, short code snippets
- Improve the demo
- Add Screenshots to the readme
- If you’re using newer APIs, indicating browser support
- Solid readme, good links to docs, contributing
- Use syntax highlighting in code snippets —> ```lang
- Link to the page examples, not just images
- Embed components directly vs. using codepen (see Chakra)
- Good screenshot at the top, good Readme
- Clean up open PRs, esp from Bots —> discourages potential contributors
- Site — try to spruce up the template, or do something unique
- Make application available on a url, use fake data so people can play around
- Readme has good stuff, but I don’t know how to use it —> npm install?
- Docs site —> how can I use it right now?
- Pitsby is great for generating Vue documentation
- Looks very complete, but no CTA — include GitHub star / fork
- Good name / explanation — very straightforward
- Consider putting a live demo —> nothing more powerful
- Name is confusing, just the name of the service
- Readme is in Portuguese, suggest translating it to English
- Site is nice, demo is good —> you could profile the input w/a sample article
- Its a little vague at first, takes a bit to figure out what it does
- Readme feels empty, contributing steps are good — list all functionalities in the readme?
- Demo works and is helpful —> but whats the best way to display the information? Can do the same w/Alfred —> maybe an Electron app could be something to explore.
- Great Readme, a good logo helps —> sponsors and contributors are great social proof, lots of people behind it
- Site: would add more content to the landing page, missed opportunity to share benefits
- Showing the limitations is great, creates trust
- Documentation is nice —> giving common use-cases is really nice
- Consider a focused screenshot of the GH release on the homepage, makes it more clear
- Lots of text, try to explain the amount of text —> 1 or 2 lines to summarize
- Edit —> you don’t need to say performance wasn’t a focus
- Architecture drawings are good
- Code snippets are really big —> Readme is more to give hints, consider decreasing size of snippets if possible
- A site would be a good complement
- Love the readme, center aligned logo, techs it was built with
- Demo —> predefined templates are great
- Awesome demo, dark mode
- Ads hint that the maintainer wants to monetize —> think about your SEO strategy, use your own domain instead of Vercel
- Not clear how to contribute —> there seems to be interest from others
- Logo, badges, gif is great —> TOC, emojis, great
- Code snippets could be shorter, overall great readme
- Overall really great —> why low visibility? Distribution —> share on Twitter, Dev.to, Hackernews
- Good position / messaging / readme
- Remove extra spaces / unnecessary characters in code snippets for a better copy/paste/use experience
- Hard to navigate in the docs site —> put screenshots of the components in the readme
- Move examples to be the first tab
- Links, docs, video is great
- Why not link the site from GitHub
- Readme is good —> you’ve got the gifs on the site, consider embedding in the repo and on your Wordpress page
- It’s a very, very niche project
- ASCII art is great, readme is nice
- Deploy button is the best way to showcase your projects
- Consider creating a docker image and showcase on docker hub
- Highlights are good, very compelling to use over regular Puppeteer
- Huge features: Generate a screenshot from code hosted somewhere, choose a theme, generate screenshots w/fancy overlays —> highlight those
- Documentation —> needs syntax highlighting
- W/the minimalistic vibe, consider adding a dark mode
- Raises a flag that its JSON/XML/YAML/CSV all in one —> performance hit
- Focus on what you’re delivering, adding the inspiration links later one
- Docs are great —> examples are nice and simple, mitigates perf concerns
- Site is kind of simple and a little boring, consider a live demo