Have you considered adopting the Standard Readme Style Spec by @RichardLitt?
Practical that would mean having the required sections in your editable template. (see minimal-readme.md) Add your example content again.
After that, explain each section like here https://github.com/RichardLitt/standard-readme/blob/master/spec.md#sections
You can mention that it follows the Spec (with link) that members of the open source community has worked out and that one can add the badge if one follows it.
Your sections and their order are already very similar to the Standard Readme Style Spec, so this might not be too complicated. You have some additional, optional sections that make sense to me, like Visuals, Support, Roadmap and Project status, so you would need to collaborate with the other project to find consent to add them or remove them.
Would you like going this way? I could propose a Pull Request.
I opened a similar issue on their repo. (RichardLitt/standard-readme#82)
Have you considered adopting the Standard Readme Style Spec by @RichardLitt?
Practical that would mean having the required sections in your editable template. (see minimal-readme.md) Add your example content again.
After that, explain each section like here https://github.com/RichardLitt/standard-readme/blob/master/spec.md#sections
You can mention that it follows the Spec (with link) that members of the open source community has worked out and that one can add the badge if one follows it.
Your sections and their order are already very similar to the Standard Readme Style Spec, so this might not be too complicated. You have some additional, optional sections that make sense to me, like Visuals, Support, Roadmap and Project status, so you would need to collaborate with the other project to find consent to add them or remove them.
Would you like going this way? I could propose a Pull Request.
I opened a similar issue on their repo. (RichardLitt/standard-readme#82)