Conversation
|
@knolleary let me know what you think here. Inspired by the readme of https://github.com/immich-app/immich/ |
|
We can additionally consider displaying something like this graph they display on their readme: It uses https://repobeats.axiom.co/ but requires certain permissions it seems. |
Updated the Forum badge color from Node-RED red (#8f0000) to Discourse's official blue (#17B4E6) for better brand recognition.
- Removed Node-RED logo from library badges - Removed redundant suffix words (nodes/flows/collections) - Added descriptive labels (Nodes/Flows/Collections) instead - Badges now show cleaner format: "Nodes: 5656" instead of logo + "5656 nodes"
|
ready for review |
knolleary
left a comment
There was a problem hiding this comment.
Looks good. Couple comments to consider.
Co-authored-by: Nick O'Leary <nick.oleary@gmail.com>
|
@knolleary ready for review again :). Also mentioned in https://flowforgeworkspace.slack.com/archives/C021LKE5EAY/p1762253601026259 |
|
@knolleary great this got merged 💪. Do you want to highlight this on "lowest threshold" socials? Thinking slack, discord, bsky etc? Maybe mentioning it inside of the existing forum post of the Node-RED con? Thinking here is: celebrating small wins instead of only voicing big wins. This will set us up slowly for more continued engagement. Side thought: Pondering how we could visualise the latest 1-3 topics from the forum and/or latest blogpost in the readme 🤔 |
|
Also curious towards your thoughts on #5340 (comment) |
|
I don't think we need to promote the fact we've updated the readme in light of all the other things we want to share in the coming days. If every time I commit something I need to post to multiple channels about the fact, I won't get anything done. |
|
To clarify, when I post about the roadmap plans, I can certainly point back to this as an example of incremental improvement. |
|
Doh - should have said earlier - I rarely use twitter so no point linking to me there :-) |
|
Sorry for sharing my opinion without being asked for, but this PR feels really weird. The README file's extension is |
|
@Semmu I agree there was an optimisation here for the rendered markdown view on GitHub rather than when reading this readme with an IDE. As a proposal, what if we minified the html, especially at the top, to all be on one line? Let me know your thoughts |
|
Most of it looks like images and links which can be written in markdown. so why not use real markdown for most of it ? |
|
Created #5423 to resolve this problem |
Proposed changes
Update the Node-RED repository readme to be more up to date/modern and inform better about contributers and contributions ahead of Node-RED con.
See the readme rendered here: https://github.com/dimitrieh/node-red/tree/improved-readme
Checklist
npm run testto verify the unit tests pass