generated from digitalservicebund/remix-application-template
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Update package-lock.json * Update Angie * Update heading styles * Remove sr-only already covered by tailwind * Move telephone link styling * Don't use index as key * Refactor details / summary css * Move button styling to shared CSS * Move rich text link styling to shared CSS * Restructure CSS and add headings * Remove IE11 edge case * Move paragraph-list class * Remove support for browsers without focus-visible * Remove unused class rich-text-2xl * Move styles to PreCheckNavigation * Remove unused max class * Move ParagraphList ol styling to component * Move list stylings and remove dito styles.css * Make props Readonly * Refactor focus styling * Refactor footer link styling * Change utilities syntax * Change base syntax * Drop old safari support * Change components syntax * Remove superfluous rich text styling * Give Accordion bg-color only on focus-visible * Move body styles to styles.css * Create custom twMerge with ds support and use * Use twMerge in RichText * Make eslint happy * Refactor nested string template * Refactor index principle list styling * Refactor sitemap styling * Adapt remaining lists to new styles * Refactor error page * Refactor principle section on landing * Fix line-height * Unify prop order * Update styles.css * Fix undefined class bug * Fix component names * Give all lists max-width and remove for exceptions * Remove rich-text classes and give link styling * Update RichText.tsx * Remove list-none and ds-label-01-reg from Details * Introduce list-unstyled utility * Remove unused class from links * Inline `rich-text` styles and refactor white links * Fix vitest * Refactor twMerge import * Cache playwright dependencies * Refactor conditional pipeline checks * Revert "Refactor conditional pipeline checks" This reverts commit 5410dd8. * Revert "Cache playwright dependencies" This reverts commit 60b24e5. * Update sitemap.tsx * Remove redundant styles * Move body height / flex styles to tag * Fix support page typo * Unify breadcrumbs spacing * Improve VP index styling * Make visualisation page responsive * Improve visualisation gaps * Fix technicalFeasibility content * Change method page heading styles * Remove rounded border in feedback form * Improve feedback buttons spacing * Change method subpages heading look to h3 * Change labels to subheads where applicable * Improve PrincipleExplanation styling * Change list-unstyled handling * Add spacing between list-items
- Loading branch information
1 parent
88e883e
commit bb30a7f
Showing
45 changed files
with
283 additions
and
329 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -238,15 +238,19 @@ Damit die digitale Umsetzung reibungslos klappt, muss die Regelung digitaltaugli | |
}, | ||
], | ||
}, | ||
principals: { | ||
principles: { | ||
title: "5 Prinzipien für digitaltaugliche Gesetzgebung", | ||
content: `1. Prinzip 1: Digitale Kommunikation sicherstellen | ||
2. Prinzip 2: Wiederverwendung von Daten und Standards ermöglichen | ||
3. Prinzip 3: Datenschutz und Informationssicherheit gewährleisten | ||
4. Prinzip 4: Klare Regelungen für eine digitale Ausführung finden | ||
5. Prinzip 5: Automatisierung ermöglichen | ||
[Details und Beispiele](${ROUTE_METHODS_FIVE_PRINCIPLES.url})`, | ||
content: [ | ||
"Prinzip 1: Digitale Kommunikation sicherstellen", | ||
"Prinzip 2: Wiederverwendung von Daten und Standards ermöglichen", | ||
"Prinzip 3: Datenschutz und Informationssicherheit gewährleisten", | ||
"Prinzip 4: Klare Regelungen für eine digitale Ausführung finden", | ||
"Prinzip 5: Automatisierung ermöglichen", | ||
], | ||
link: { | ||
text: "Details und Beispiele", | ||
href: ROUTE_METHODS_FIVE_PRINCIPLES.url, | ||
}, | ||
}, | ||
}; | ||
|
||
|
@@ -659,7 +663,7 @@ Mit diesen Informationen sind Sie gut vorbereitet, um | |
- in der **formellen Beteiligung** eine wirkungsvolle Umsetzung zu besprechen.`, | ||
}, | ||
{ | ||
background: "blue", | ||
isSubstep: true, | ||
headline: { text: "2.1. Zuständige Akteurinnen und Akteure auflisten" }, | ||
info: [ | ||
{ | ||
|
@@ -676,7 +680,7 @@ Mit diesen Informationen sind Sie gut vorbereitet, um | |
], | ||
}, | ||
{ | ||
background: "blue", | ||
isSubstep: true, | ||
headline: { | ||
text: "2.2. Aufgaben und Abläufe gemeinsam erfassen", | ||
}, | ||
|
@@ -703,7 +707,7 @@ Mit diesen Informationen sind Sie gut vorbereitet, um | |
], | ||
}, | ||
{ | ||
background: "blue", | ||
isSubstep: true, | ||
headline: { | ||
text: "2.3. IT-Systeme gemeinsam erfassen", | ||
}, | ||
|
@@ -735,7 +739,7 @@ Mit diesen Informationen sind Sie gut vorbereitet, um | |
text: "Mit einem guten Verständnis des Ist-Zustandes erarbeiten Sie nun Ihre Regelung. Jetzt geht es darum, Möglichkeiten zur Digitalisierung zu finden und Hindernisse aus dem Weg zu räumen — eine gute digitale Umsetzung spart langfristig Zeit und Geld und erfüllt die heutigen Erwartungen der Betroffenen an den Staat.", | ||
}, | ||
{ | ||
background: "blue", | ||
isSubstep: true, | ||
headline: { | ||
text: "2.4. Möglichkeiten und Hindernisse der digitalen Umsetzung identifizieren", | ||
}, | ||
|
@@ -754,7 +758,7 @@ Mit diesen Informationen sind Sie gut vorbereitet, um | |
], | ||
}, | ||
{ | ||
background: "blue", | ||
isSubstep: true, | ||
headline: { | ||
text: "2.5. Technische Umsetzbarkeit sicherstellen", | ||
}, | ||
|
@@ -791,7 +795,7 @@ Die Erkenntnisse und Ergebnisse aus den vorigen Schritten helfen Ihnen dabei, | |
- den **Umsetzungsprozess einfach besprechbar** zu machen in Abstimmungen anhand von Visualisierungen.`, | ||
}, | ||
{ | ||
background: "blue", | ||
isSubstep: true, | ||
headline: { text: "Schreiben Sie die Regelung" }, | ||
text: "Nutzen Sie Ihre gewohnten Programme und Arbeitshilfen, um die Regelung zu schreiben — z. B. eNorm und das Handbuch der Rechtsförmigkeit.", | ||
}, | ||
|
@@ -1276,13 +1280,13 @@ export const technicalFeasibility = { | |
icon: DrawOutlined, | ||
title: "Verstehen Sie die Auswirkungen auf IT-Systeme", | ||
text: `Vergleichen Sie gemeinsam mit den [zuständigen Akteurinnen und Akteuren](${ROUTE_METHODS_RESPONSIBLE_ACTORS.url}) das geplante Vorhaben mit den Möglichkeiten der bestehenden IT-Systeme. Überprüfen Sie die Informationen mithilfe neutraler IT-Expertinnen und -Experten. | ||
<br class="block content-[''] !mb-24" /> | ||
So erfahren Sie | ||
- welche IT-Systeme für Ihr Vorhaben verwendet werden können | ||
- und an welchen Stellen Änderungen nötig sind. | ||
<br class="block content-[''] !mb-24" /> | ||
### Sie müssen nicht alles allein bewältigen | ||
<h3 class="ds-subhead font-bold">Sie müssen nicht alles allein bewältigen</h3> | ||
Bei kleinen Fragen rufen Sie den Digitalcheck-Support an unter 0151/40 76 78 39. | ||
Für ein unterstützendes, einstündiges Videotelefonat schreiben Sie eine E-Mail an [email protected] oder buchen Sie direkt einen Termin.`, | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.