Open rexagod opened 11 months ago
I'd like to propose a standard that all documentation in the dependent repositories adhere to, in order to improve the overall readability of the website. A couple of concerns I noticed were:
title: XXXX
(foo-bar.md
becomes ---\ntitle: Foo Bar\n---\n
) to documents lacking such a header section.bar.md
is specified as foo/bar.md
, when the former would work just the same). Introducing a lint rule for this would ensure the path translation of the pages w.r.t. serving content (content/docs/foo/bar.md
is served as localhost:XXXX/docs/foo/bar/
and needs to be sed
-ed as such before serving) is consistent throughout the text.These are the ones I can think of right now from the top of my mind, but in general, it could prove beneficial to adhere to a documentation standard (such as k/enhancements does for KEPs) and even introducing a lint rule to automate validating all that.
@simonpasquier raised a concern around outdated content that we'd be better off ignoring when compiling the website. I believe this could be addressed when writing the document and including something like website-ignore: true
within the header.
Thanks for starting this! From my POV, I'd like first that we clean up the existing MarkDown files (in terms of consistency, relevance, out-dated information, ....) as well as brainstorm on how we want the content to be organized.
Sounds good, Simon. I'll get started on that front. :)
Having said that, some of the proposed changes might already be good to go (like Makefile updates).
@AshwinSriram11 since you are already working on website see if this helps
These changes mostly entail:
Fixes: https://github.com/prometheus-operator/prometheus-operator/issues/6046