Main into develop

CHANGELOG.md

@@ -1,5 +1,12 @@
 
 
+## [0.5.1](https://github.com/Amsterdam/ee-docs/compare/v0.5.0...v0.5.1) (2025-04-14)
+
+
+### Bug Fixes
+
+* **searchpage:** update swizzled search template to resolve build errors ([#126](https://github.com/Amsterdam/ee-docs/issues/126)) ([c504890](https://github.com/Amsterdam/ee-docs/commit/c504890f74e65cc176ccceedf449c05dba8d4d39))
+
 ## [0.5.0](https://github.com/Amsterdam/ee-docs/compare/v0.4.0...v0.5.0) (2025-02-06)
 
 

docs/frontend/accessibility.md

@@ -1,10 +1,10 @@
 # Accessibility
 
-> This page was last reviewed 6th March 2024. It needs to be reviewed again on the 6th December 2024.
+> This page was last reviewed on 6 February 2025. It needs to be reviewed again on 6 November 2025.
 
 ## What is the standard for accessibility?
 
-In accordance with the Digital Government Act, the municipality of Amsterdam is required to build all its websites and applications in compliance with the Web Content Accessibility Guidelines (WCAG) at levels A and AA.
+In accordance with the Digital Government Act, the municipality of Amsterdam is required to build all its websites and applications in compliance with the Web Content Accessibility Guidelines (WCAG) 2.1 at AA level.
 
 ## When and for whom is this standard applicable?
 
@@ -20,14 +20,15 @@ The law is applicable to all government websites and applications, including int
   - [ ] zooming in at 200%
   - [ ] verify that all links feature descriptive link text
 - [ ] Evaluate the usability of your application by
-  - [ ] testing a workflow on your application without the use of a keyboard. Employ screen readers, such as [JAWS](https://accessibility.psu.edu/screenreaders/jawscommands/) or [VoiceOver](https://support.apple.com/guide/voiceover-guide/welcome/web).
-    - [ ] confirm the page's order is logical
-    - [ ] verify all content is accessible to the screen reader
-  - [ ] testing a workflow on your application without the use of a mouse  Employ keyboard shortcuts
-    - [ ] check if the focus ring remains consistently visible
-- [ ] Ensure all videos are captioned
-- [ ] Ensure all audio is described as needed
-- [ ] Ensure all audio-only files are transcribed
+  - [ ] testing a workflow on your application without the use of a keyboard or mouse. Employ screen readers, such as [JAWS](https://accessibility.psu.edu/screenreaders/jawscommands/) or [VoiceOver](https://support.apple.com/guide/voiceover-guide/welcome/web).
+    - [ ] ensure logical page order
+    - [ ] confirm screen reader compatibility
+ Employ keyboard shortcuts
+    - [ ] check focus ring visibility when navigating
+- [ ] Ensure all multimedia has alternatives:
+  - [ ] videos must have captions
+  - [ ] audio must have descriptions
+  - [ ] audio-only content must be transcribed
 
 ### on a web application?
 
@@ -94,6 +95,7 @@ Testing accessibility thoroughly can be challenging. Consider collaborating with
 
 - [Testing for Accessibility](https://accessibility.psu.edu/testing/protocol/)
 - [Praktische toegankelijkheidstips](https://www.digitoegankelijk.nl/aan-de-slag/tips)
+- [WCAG rules and regulation](https://wcag.nl/kennis/wet-en-regelgeving/)
 
 ## Acknowledgments
 

docs/general/languages-and-frameworks.md

@@ -1,6 +1,6 @@
 # Languages & Frameworks for Software Development
 
-> This page was last reviewed October 10th 2024. It needs to be reviewed again on April the 10th 2025.
+> This page was last reviewed on 10th April. It needs to be reviewed again on 10th January 2026.
 
 ## What is the standard?
 
@@ -19,7 +19,7 @@ New frontend applications are developed using **[TypeScript](https://www.typescr
 
 - UI logic is implemented with **[React](https://react.dev/)** in combination with the **[Amsterdam Design System](https://designsystem.amsterdam/)**.
 - CSS is implemented using **[CSS modules](https://github.com/css-modules/css-modules)**.
-- Full application development is implemented with **[Next.js](https://nextjs.org/)** or **[Remix](https://remix.run/)**.
+- Full application development is implemented with **[Next.js](https://nextjs.org/)** or **[React Router (Framework)](https://reactrouter.com/)**.
 
 ### Mobile Applications
 

docs/general/project-documentation.md

@@ -1,5 +1,5 @@
 # Documentation
-> This page was last reviewed 6th March 2024. It needs to be reviewed again on the 6th December 2024.
+> This page was last reviewed 13 February 2025. It needs to be reviewed again on 13 November 2025.
 
 ## What is the standard for documentation?
 Include documentation in your project that facilitates understanding, usage, and maintenance of your code. The documentation should promote usability and longevity of your project, and effective collaboration among your stakeholders.

docs/general/readme-default.md

@@ -1,10 +1,10 @@
 # Readme files
 
-> This page was last reviewed on April 23rd, 2024. It needs to be reviewed again on January 23rd, 2025.
+> This page was last reviewed on February 3rd, 2025. It needs to be reviewed again on November 3rd, 2025.
 
 ## What is the standard for a README for the city of Amsterdam?
 
-There must be a README.md file for every Github repository of the city of Amsterdam. A README.md file should be an overview and list of instructions to help someone get started with your project.
+There must be a README.md file for every Github repository of the city of Amsterdam. A README.md should briefly describe the project, its purpose, and provide clear instructions to help developers, contributors, and stakeholders navigate and use the repository effectively.
 
 ## When and for whom is this standard?
 
@@ -15,10 +15,14 @@ This standard must be applied to all new repositories of the city of Amsterdam (
 
 A README must include the following:
 
-- [ ] Name of the project and a short introduction. Give the objectives and motivation behind the project and, if applicable, give the URL of the web application.
+- [ ] Name of the project and a short introduction. This should include:
+    - [ ] A brief overview of the project’s purpose.
+    - [ ] The main objectives and motivation behind it.
+    - [ ] (If applicable) A link to the deployed web application and relevant documentation.
 - [ ] Name of the team responsible for maintaining the project and how to contact them.
 - [ ] An installation guide which contains information about software dependencies.
-- [ ] A how-to build and test the application
+- [ ] A how-to build and test the application.
+- [ ] Guidelines on where to report bugs or request features (e.g., GitHub Issues, Jira).
 
 ## What pitfalls to avoid?
 

docs/general/using-git.md

@@ -1,5 +1,5 @@
 # Using Git
-> This page was last reviewed May 14th, 2024. It needs to be reviewed again on February 14th, 2025.
+> This page was last reviewed 13 February 2025. It needs to be reviewed again on 13 November 2025.
 
 ## What is the standard for using Git?
 The city of Amsterdam uses Git to push its code to GitHub.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "docusaurus",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "private": true,
   "scripts": {
     "docusaurus": "docusaurus",