That is a brilliant solution actually. I've already been thinking about creating different landing pages for the 3/5 primary "roles" I can imagine would want to use this, where I explain how it covers their particular needs, with some example use cases. However, it didn't occur to me I could "lead" these roles into these sections from the primary landing page before you said it (sound of me feeling stupid ... :/). Thank you :)
Commenting on your other comment here BTW.
I think amount of github stars do not solve this task
The purpose of that thing is to communicate that the thing is open source. It's kind of a "head fake", where the secondary message (GitHub/Open Source) is more important than the number of stars. Plus of course implicitly encouraging visitors to star the project, leading to higher ranking, etc ...
I would state it directly, that the product is open source and is being widely used currently. Because Github (with all due respect) and Github stats are not self-explanatory thing for many of your web-site visitors.
If it is possible I would collect reviews and post these reviews (from developers, devops and non technical managers) on the pages, dedicated for the relevant roles to make the product more appealing for the target audience.
I would state it directly, that the product is open source and is being widely used currently
It is a part of the header in the second section, below the fold. But if you didn't see that before I told you, there is something wrong with our communication ... :/
BTW, check the screenshot. Is this a better "primary message". Another commenter here said this was the best sentence that explained things the best ...
Notice the new text saying "Wrap your database in a CRUD API in seconds" - I suspect it's a better primary message ...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
That is a brilliant solution actually. I've already been thinking about creating different landing pages for the 3/5 primary "roles" I can imagine would want to use this, where I explain how it covers their particular needs, with some example use cases. However, it didn't occur to me I could "lead" these roles into these sections from the primary landing page before you said it (sound of me feeling stupid ... :/). Thank you :)
Commenting on your other comment here BTW.
The purpose of that thing is to communicate that the thing is open source. It's kind of a "head fake", where the secondary message (GitHub/Open Source) is more important than the number of stars. Plus of course implicitly encouraging visitors to star the project, leading to higher ranking, etc ...
... but I definitely see your point :/
I would state it directly, that the product is open source and is being widely used currently. Because Github (with all due respect) and Github stats are not self-explanatory thing for many of your web-site visitors.
If it is possible I would collect reviews and post these reviews (from developers, devops and non technical managers) on the pages, dedicated for the relevant roles to make the product more appealing for the target audience.
It is a part of the header in the second section, below the fold. But if you didn't see that before I told you, there is something wrong with our communication ... :/
BTW, check the screenshot. Is this a better "primary message". Another commenter here said this was the best sentence that explained things the best ...
Notice the new text saying "Wrap your database in a CRUD API in seconds" - I suspect it's a better primary message ...