As a maintainer, I want the links for navigation to be in a json/yaml, so that I can easily reuse them in different components without having to hardcode the data

[simon-wg]

📝 Description

I want to have a file containing all links and texts so that it can be reused in multiple components.
One example would be something like:

Navigation:
  Sektionen:
    Link:
      URL: "/groups"
      Text: "Kommittéer, föreningar och andra instanser"
    Link:
      URL: "https://dokument.chalmers.it"
      Text: "Dokument"
  Link:
    URL: "/contact"
    Text: "Kontakt"

✅ Acceptance Criteria

-[] All navmenus use data from a file instead of hardcoded values.
-[] We have a file containing mappings of links, and dropdowns containing links.

💡 Additional context

No response

[simon-wg]

@GAsplund opinions on this? I came up with the idea after discussing how to manage the mobilenav I'm currently designing with some people. If we implement this we could also allow for editing links and texts directly on the website and keep the file in a volume for persistence between redeploys.

[GAsplund]

I like the idea, as it would greatly decrease the need for pushing new commits if the header needs to change. However, I think using the database for storing these would be a better way to do it. I could see there being links stored in a key-value fashion (like they are on nollk.it) in order to store arbitrary links, but for this site I don't see other cases than the header for having editable links.

My pseudocode for this looks like:

categories:
id: number
nameEn: string
nameSv: string
url: string (nullable)

categoryLinks:
id: number [id]
nameEn: string
nameSv: string
category: number (FK -> categories.id)
url: string

[simon-wg]

That's a fair argument, I agree that the links are unlikely to be updated often.
I will take a look at implementing something similar to your code, as well as the mobile nav-drawer during the next workshop.