Closed raamdev closed 9 years ago
Great idea. I believe we can generate the link which leads back to the file without needing a new YAML config. key. That would allow this to function for all existing articles, even if they do not contain the additional key; i.e., WPKBA already knows where the underlying file is located at GitHub.
Marking this as ready for work.
we can generate the link which leads back to the file without needing a new YAML config. key.
Even better! That's awesome! I totally forgot that all that information was already available.
Adding this in the article footer on the front end, when the current user can edit the article. I'll leave this open so we can add it in the back end also.
This is now shown in three places, as seen in the above screenshots.
Beauuuutiful! Thank you!
When using the GitHub Integration, KB Articles are only edited by changing the associated Markdown file. That means making edits to KB Articles requires finding the associated Markdown file on GitHub. Right now that process looks like this:
I propose that we add a new YAML Key called
markdown-file:
that can contain a link to the Markdown file itself.Then we can create convenient links to that Markdown file when the YAML Key is present: