Dead link to knowledge base

[Brilator]

The knowledge base link in the footer directs to https://nfdi4plants.org/content/docs/research-data-management.html, which does not exist any more (was changed to https://nfdi4plants.org/content/docs/ResearchDataManagement.html...).

Maybe implement a knowledge base landing page and link to that.

[Freymaurer]

Maybe implement a knowledge base landing page and link to that.

@CMR248

[Brilator]

I would suggest to create one single page where the visitor is redirected to when clicking "Knowledge Base" in the Navbar. Just with a few lines introducing what the KB is, incl. sidebar on the left.

Would it make sense to create a new layout: landing for this?

• no (i.e. ignore) date / published, author, etc.
• MAY contain TOC
• MAY contain sidebar

[Freymaurer]

Would it be possible to just imitate the design of web-component-docs? Some documentation repos just start with an Home/Index page.

• https://nfdi4plants.github.io/web-components-docs/
• https://safe-stack.github.io/docs/

[Brilator]

Yes, that's perfectly enough. It's really just to have a save and persistent link to the kb.

My suggestion for the landing page (not PR'ed to main, yet): https://github.com/Brilator/nfdi4plants.github.io/blob/main/src/content/docs/landings/landing_knowledgebase.md

[Freymaurer]

It would be awesome if those bold textparts could be actual links to the corresponding subpages!

For a consisting naming, could you change the .md file name to either index.md or home.md?

[Brilator]

It would be awesome if those bold textparts could be actual links to the corresponding subpages!

Yes, but then it gets more complicated for you -> would require additional sub-landing pages for the sections. At the moment those are just drop-down menus.

[Brilator]

For a consisting naming, could you change the .md file name to either index.md or home.md?

Sure

[Freymaurer]

Yes, but then it gets more complicated for you -> would require additional sub-landing pages for the sections. At the moment those are just drop-down menus.

Index pages for sub-categories should not be any different to all other .md files and do not require specific parsing.

See at the example of web-component-docs:

• index-url = https://nfdi4plants.github.io/web-components-docs/
  • no .html referenced
• further sub-category landing pages (if wanted), would be https://nfdi4plants.github.io/web-components-docs/ + subcategory + home.md/index.md/introduction.md. Which can be created/referenced, etc just as all other .md files.

[Brilator]

I understand, I was just trying to say that, the section "heading" itself isn't linked.

orange arrows: no link blue arrows: link

So, this comes with redundancy (2x "Web Components", 2x "Development") and another level.

[Freymaurer]

Yeah, i imagine it to look something like this for the knowledgebase:

[Brilator]

Fine for me.

[CMR248]

Looks good to me too. It would be great if the outsourced repo could be edited by @Martin-Kuhl, being the main responsible for the KB. So he should at least be listed as maintainer.

[Freymaurer]

Done! 🎉