Seekra/frontend
3
2
Fork 0
generated from Seekra/repository-template
Code Issues 4 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

Add base settings page #74

Merged
jakob.scheid merged 43 commits from feature/base-settings-page into main 2026-05-23 13:16:37 +02:00
Conversation 1 Commits 43 Files Changed 17
+193 -29
jakob.scheid commented 2026-05-23 12:58:03 +02:00
Owner
Copy Link
Copy Source

Description

This PR includes the base settings page which will be expanded to include logic at a later date.

Why?

There are (UI) decisions that the user should make, such as showing flags in the language selection dropdown menu or not.

Summary

  • New route (/settings) for the settings page
  • Layout for a sidebar on the left
  • Restructuring of some components and CSS classes
  • Second footer segment containing a router link to the settings page
  • Lower footer (due to the second footer segment)

Implementation

Create a layout component for views with a sidebar on the left side + main content on the right side that is used in the settings page. To ensure a consistent layout (without any breaks in the boundary lines), the main content padding must now be set in the views, so that the padding can be set separately for each view. As a result, it is possible to omit the padding. There is a new class for setting this padding (main-content-padding) that can be simply added to the class list of a view container to set the padding.

Furthermore, the main content container in src/App.vue was removed, so that every view needs a container.

Related Issues

Closes: #72

# Description This PR includes the base settings page which will be expanded to include logic at a later date. ## Why? There are (UI) decisions that the user should make, such as showing flags in the language selection dropdown menu or not. ## Summary - New route (`/settings`) for the settings page - Layout for a sidebar on the left - Restructuring of some components and CSS classes - Second footer segment containing a router link to the settings page - Lower footer (due to the second footer segment) ## Implementation Create a layout component for views with a sidebar on the left side + main content on the right side that is used in the settings page. To ensure a consistent layout (without any breaks in the boundary lines), the main content padding must now be set in the views, so that the padding can be set separately for each view. As a result, it is possible to omit the padding. There is a new class for setting this padding (`main-content-padding`) that can be simply added to the class list of a view container to set the padding. Furthermore, the main content container in `src/App.vue` was removed, so that every view needs a container. ## Related Issues Closes: #72
jakob.scheid added this to the mvp-frontend milestone 2026-05-23 12:58:03 +02:00
jakob.scheid added the
type
feature
prio
medium
area/global labels 2026-05-23 12:58:03 +02:00
jakob.scheid added this to the MVP Frontend project 2026-05-23 12:58:03 +02:00
jakob.scheid added 42 commits 2026-05-23 12:58:04 +02:00
Add settings view boilerplate 8901967ab0
Add translations for 'settings' 6d5c7e4270
Add settings route 027ee2d191
Add settings view heading 6726600c8e
Add link to settings page in the footer 7bcdf77ca8
Reduce footer height b324b93141
Update footer flexbox ad8bbfa666
Replace hard-coded settings link text in the footer with a translation be96541b3e
Add sidebar boilerplate d5601b8fdb
Add left sidebar layout boilerplate 0a65bcdae1
Use sidebar component in left sidebar layout 2989817278
Add sidebar section boilerplate 16ee164d76
Bugfix: Fix spelling mistake in the sidebar section component 6cc94b651f
Remove sidebar section component ed2b3224b4
Rename file d1c428eccd
Add left sidebar layout content 5104c4e8e7
Add sidebar component slot b00aaabbb1
Add CSS grid container in the left sidebar layout 2ad95385d2
Add sidebar container 989664422c
Add sidebar right border aa47015d3a
Add sidebar to the settings view 76815c6a93
Rename left sidebar layout to base layout b48a487d2f
Use base layout in the app root component def3a84e59
Add check whether there is a sidebar component in the base layout 33e9ca7cf1
Add containers to components without a content container f65c3d58aa
Remove main content wrapper b0d3258369
Rename base layout to left sidebar layout fbefb2e7fd
Remove main content bottom padding 3623265ae0
Remove top margin from footer 7013c60a20
Include sidebar in the left sidebar layout 4df51a970d
Add padding to the main content in the left sidebar layout 2a5e79b55d
Add settings view page wrapper 0583de0dfa
Add left sidebar layout top border f354c1867c
Move main content padding frm the app root component to the views 1ebf5780d2
Use semantic HTML elements in the settings view 34b7cfbf5a
Use semantic HTML elements in the sidebar d3e8a0125d
Use semantic HTML elements in the left sidebar layout ead8821b0a
Add padding to the sidebar d3e4d54c57
Add padding to the settings view header 287d7ad713
Add license header to settings view 17b49cdb6e
Add license header to sidebar fe20a618fe
Add license header to left sidebar layout bd25409d9f
jakob.scheid moved this to Review in MVP Frontend on 2026-05-23 13:00:12 +02:00
jakob.scheid added
area
settings
 and removed area/global labels 2026-05-23 13:01:09 +02:00
jakob.gregory approved these changes 2026-05-23 13:10:15 +02:00
jakob.gregory left a comment
Member
Copy Link
Copy Source

Very nice!

Very nice!
jakob.scheid added 1 commit 2026-05-23 13:16:28 +02:00
Merge branch 'main' into feature/base-settings-page 4d62ca2b75
jakob.scheid merged commit 69d752f79b into main 2026-05-23 13:16:37 +02:00
jakob.scheid deleted branch feature/base-settings-page 2026-05-23 13:16:37 +02:00
jakob.scheid moved this to Done in MVP Frontend on 2026-05-23 13:17:33 +02:00
jakob.scheid modified the milestone from mvp-frontend to settings-ready 2026-06-05 11:15:10 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
jakob.gregory
Labels
Clear labels
area/global
area
search-results
area
settings
area
startpage
prio
critical
prio
high
prio
low
prio
medium
type
bug
type
chore
type
docs
type
feature
type
refactor
type
testing
type/urgent
No Label
area
settings
prio
medium
type
feature
Milestone
No items
No Milestone settings-ready
Projects
Clear projects
No project MVP Frontend
Assignees
Clear assignees
jakob.gregory (Jakob Gregory) jakob.scheid (Jakob Scheid) johannes.vos (Johannes D. Vos)
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Seekra/frontend#74
Delete Branch "feature/base-settings-page"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?