Repository navigation
Auto-Generate the Mindmap on .md-source changes #162
Description
#156 is great stuff, we just need to remember to add a GitHub Action to regenerate the SVG / HTML / rendered products once the .md changes and make a checklist item for PRs to update the .md once new things come in to keep everything fresh.
Originally posted by @lenucksi in #156 (comment)
Activity
spier commentedon May 10, 2020
When you say mindmap, are you referring to
IS.mdandIS.html?What I am missing from
IS.mdas well is an explanation of what it is. e.g. if any reader of the IS Patterns finds this file, how would they know what it is?lenucksi commentedon May 11, 2020
With
mindmapI'd refer to the rendered artifact(s), i.e. the SVG or the SVG embedded in a HTML file.mindmap sourceis the underlying MD file.Sorry for having an issue that is still a bit raw - it's generated from a PR comment to be dealt with later.
I would hope that we have the mindmap embedded an a larger production (e.g. the pattern catalogue or book at some point) that has additional details explaining it.
spier commentedon Dec 26, 2020
FYI documentation and files related to the mindmap are now in:
https://github.com/InnerSourceCommons/InnerSourcePatterns/tree/master/pattern-categorization
spier commentedon Aug 29, 2021
I asked a question on the markmap repo related to this.
While we could generate the input file (markdown) automatically, markmap doesn't have an option to turn that into a static file that we can embed in our book at https://patterns.innersourcecommons.org.
spier commentedon Sep 1, 2021
This particular issue has been implemented in #348