Resolve "Check for correct semantic html elements" #2302
No reviewers
Labels
No labels
Security
TeX
auto-update
board
done
board
ready
board
todo
check
delete-eslint-rc-js
check
update-builddeps-package-json
check
update-eslint-rc-js
check
update-gitignore
check
update-merge-request-template
check
update-prettier-ignore
check
update-pyproject-toml
check
update-renovate-json
check
update-tox-ini
part
backend
part
ci
part
docs
part
frontend
part
i18n
part
non-technical
part
packaging
prio
1
prio
2
prio
3
release-mr-5.x
size
large
size
medium
size
small
source
customer
source
customer::fsmw
source
customer::fss
source
customer::teckids
source
downstream
type
breaking
type
bug
type
feature
type
refactoring
workflow
blocked
workflow
confirmed
workflow
current-todo
workflow
discussing
workflow
new-app
workflow
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
aleksis/AlekSIS-Core!2302
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "474-check-for-correct-semantic-html-elements"
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?
Closes #474
added 4 commits
9a668b19- Load all roboto variants in the head.49b28002- Use h1 as the main heading in the base templatea9b7b9f1- Style h1 and h2 elements to better fit aleksis820a05ef- Replace all heading tags with semantic correct alternativesCompare with previous version
Only ready in the core! Please check the design in the dev meeting:


old:
new:
marked this merge request as ready
assigned to @hansegucker and unassigned @ZugBahnHof
approved this merge request
added 1 commit
58981921- Adjust font-weightCompare with previous version
Current screenshot:

Do we really need all these different font weights? Or, can we limit them at least to some?
This is a little reminder, @ZugBahnHof: Please check the discussion item above and add the change to the changelog.
added 27 commits
master4aade7a8- Merge branch 'master' into 474-check-for-correct-semantic-html-elementse2a827cb- Update CHANGELOG.rstCompare with previous version
Not necessarily (→ currently not). But maybe in the future… Therefore, I would leave the declaration in the settings by all means, the loading in the template is maybe not that important. What do you think about this @hansegucker ?
Ok, then leave them there. Additionally, please check why the pipeline fails.
resolved all threads
added 1 commit
3bc5a44d- Use correct Roboto font variants in base_print.htmlCompare with previous version
added 5 commits
masterabb9ce12- Merge branch 'master' into 474-check-for-correct-semantic-html-elementsCompare with previous version
mentioned in commit
aa32d543f7