Features
Stars and bookmarks
Stars and bookmarks help developers support projects, save useful work, and come back to interesting builds later.
On Devmaniac, stars and bookmarks are simple signals. A star shows appreciation or support for a project. A bookmark saves a project so you can find it again.
What are stars?
A star is a lightweight way to show that you like, support, or respect a project.
You can star a project when it feels useful, interesting, well-built, or worth encouraging.
Stars can help:
- Support builders
- Show appreciation for useful work
- Signal that a project is interesting
- Help project owners see that people noticed their work
- Encourage developers to keep building
A star is not a review, contract, or deep technical approval. It is a simple signal that says:
This project caught my attention.
What are bookmarks?
A bookmark saves a project for later.
You can bookmark a project when you want to revisit it, study it, follow its progress, or use it as inspiration.
Bookmarks are useful for:
- Saving projects you want to inspect later
- Tracking live projects over time
- Keeping useful examples in one place
- Collecting inspiration for your own builds
- Returning to projects after new journals are posted
If stars are public support, bookmarks are personal memory.
Stars vs bookmarks
Stars and bookmarks are related, but they are not the same thing.
| Stars | Bookmarks |
|---|---|
| Show support or appreciation | Save a project for later |
| Useful as a public signal | Useful as a personal collection |
| Helps builders feel noticed | Helps you revisit useful projects |
| Best for projects you like | Best for projects you want to follow or study |
| Answers “Is this worth supporting?” | Answers “Do I want to come back to this?” |
Why stars matter
Building projects can feel lonely, especially when the project is early, unfinished, or still changing.
A star gives builders a small sign that someone noticed their work.
That matters because early encouragement can help developers keep going. A project may still be rough, but public support can push the builder to improve it.
Stars are not the whole goal, though. Do not build only for stars. Build for progress, proof, and real learning.
Why bookmarks matter
Bookmarks help you collect projects that are worth revisiting.
This is useful because Devmaniac is built around live projects. A project that looks early today may become much stronger after several journals, bug fixes, redesigns, and deployments.
Bookmarking lets you come back later and see how the project evolved.
When should you star a project?
Star a project when you want to support it.
Good reasons to star:
- The idea is useful
- The project is well explained
- The builder is showing real progress
- The project helped you learn something
- The project has a good demo or useful code
- You want to encourage the developer
You do not need to star only perfect projects. Sometimes early projects deserve support because the builder is documenting real progress.
When should you bookmark a project?
Bookmark a project when you want to return to it.
Good reasons to bookmark:
- You want to follow the project’s progress
- You want to study the tech stack later
- You want inspiration for your own project
- You want to read future journals
- You want to compare how the project changes over time
- You want to save it before giving feedback later
Stars and bookmarks for live projects
Live projects are especially useful with stars and bookmarks.
A live project may start small, but it can improve through journals and updates. Stars can encourage the builder, while bookmarks help others follow the journey.
For live projects:
- Stars show support for the build
- Bookmarks help people return for future updates
- Both signals can help the project feel less invisible
Stars and bookmarks for finished projects
Finished projects can also receive stars and bookmarks.
For finished projects:
- Stars show appreciation for completed work
- Bookmarks help people save useful examples
- Both can help strong projects get noticed
A finished project with clear explanation, working links, and useful screenshots is more likely to be saved or supported.
Do stars prove skill?
Stars can be a useful signal, but they are not the full proof.
A project with many stars may be interesting, but the real proof still comes from the project itself: the description, code, demo, journals, decisions, and progress.
Do not treat stars like a developer rating from heaven. They are helpful, but they are not magic. 😭
Do bookmarks prove skill?
Bookmarks are mostly personal. They show that someone wanted to save the project, but they do not automatically prove technical quality.
Still, bookmarks are useful because they show that the project was worth returning to.
How to get more meaningful stars and bookmarks
The best way is not begging. The best way is making your project clear and useful.
Improve your project page by adding:
- A clear title
- A useful description
- An honest tech stack
- Working GitHub or live links
- Screenshots or images
- Progress journals
- Clear next steps
- Context about what problem the project solves
People are more likely to star or bookmark when they understand why the project matters.
Common mistakes
Avoid these mistakes:
- Begging for stars without improving the project
- Using stars as the only measure of success
- Bookmarking everything and never revisiting anything
- Ignoring project clarity
- Posting vague projects and expecting attention
- Comparing your early project to someone else’s mature project
Stars and bookmarks are useful, but the real game is still building better work.
The core idea
Stars and bookmarks should answer:
Which projects are worth supporting, saving, following, or revisiting?
They help projects feel less invisible, but they work best when the project already has clear proof of work.