feat: implement basic design for empty content library

[standeren]

Description

Implements the content-library, with a landingpage and empty pages for codeLists and images, to be used in the app-development service. It can be accessed by adding /content-library to the url for an app in designer.

Related Issue(s)

• #{issue number}

Verification

• Your code builds clean without any errors or warnings
• Manual testing done (required)
• Relevant automated test added (if you find this hard, leave it and we'll help out)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.62%. Comparing base (1b47df6) to head (aba1f76).
Report is 37 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #13805      +/-   ##
==========================================
+ Coverage   94.59%   94.62%   +0.02%     
==========================================
  Files        1630     1647      +17     
  Lines       21894    21992      +98     
  Branches     2573     2582       +9     
==========================================
+ Hits        20711    20809      +98     
  Misses        940      940              
  Partials      243      243              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Annikenkbrathen]

I see that things are progressing quickly, and the same goes for the sketching. This front page of the library appears when the user opens the library, but once you click to a new page, you don’t have the option to go back to the front page. This is poor UX design on my part, and something I missed. The settings modal doesn’t have a front page but takes you to the first item in the "About the App" column when you open the modal.

Possible solutions:

1. Make the "Library" title clickable so the user can click it to view the front page.
2. Add a page called "About the Library" in the left-hand column.
3. Remove the front page entirely.

Personally, I’m leaning towards option 2 to follow the same pattern as the settings modal.

[Konrad-Simso]

Nice work! 😄 I saw some possible changes and made suggestions.

As for the comment by Anniken about the UX design.
The current solution fulfills option 1. I think it's good as a first iteration, and if there is going to be a redesign of the library, then changes can be implemented in a second iteration.

[Konrad-Simso]

Nice work! 💯