update Docusaurus and fixed vulnerabilities. (#89)

Updates the Docusaurus website dependencies and configuration to target Docusaurus 3.10 while improving compatibility with upcoming v4 changes, plus cleans up generated quiz artifacts and MDX syntax in docs.

**Changes:**
- Bump Docusaurus packages to `^3.10.0`, add `@docusaurus/faster`, raise Node engine requirement to `>=20`, and add security-related `overrides`.
- Enable Docusaurus `future.v4` flag and remove large blocks of commented-out navbar/footer configuration.
- Replace HTML comments in docs with MDX-compatible `{/* ... */}` comments and remove generated timestamps from quiz-generated files.

Author: Snooz82

.github/.workflows/pages.yml

@@ -5,21 +5,27 @@ This website is built using [Docusaurus](https://docusaurus.io/), a modern stati
 ### Installation
 
 ```
-$ yarn
+$ npm install
+```
+
+For reproducible installs in CI, use:
+
+```
+$ npm ci
 ```
 
 ### Local Development
 
 ```
-$ yarn start
+$ npm run start
 ```
 
 This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
 
 ### Build
 
 ```
-$ yarn build
+$ npm run build
 ```
 
 This command generates static content into the `build` directory and can be served using any static contents hosting service.
@@ -29,13 +35,13 @@ This command generates static content into the `build` directory and can be serv
 Using SSH:
 
 ```
-$ USE_SSH=true yarn deploy
+$ USE_SSH=true npm run deploy
 ```
 
 Not using SSH:
 
 ```
-$ GIT_USER=<Your GitHub username> yarn deploy
+$ GIT_USER=<Your GitHub username> npm run deploy
 ```
 
 If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the `gh-pages` branch.

website/README.md

@@ -39,7 +39,7 @@ When executing or debugging tests|tasks, the editor supports the execution layer
 When writing keywords in e.g. Python for keyword libraries, the editor supports the adaptation layer.
 Therefore also other additional extensions of Robot Framework can be categorized into these layers.
 
-<!-- TODO: add a graphic here -->
+{/* TODO: add a graphic here */}
 
 ## 1.2.2 What is Robot Framework & What It Is Not
 

website/docs/chapter-01/02_architecture.md

@@ -194,7 +194,7 @@ A suite file must contain either a `*** Test Cases ***` or a `*** Tasks ***` sec
 
 See [2.6 Writing Test|Task and Calling Keywords](chapter-02/06_writing_test.md) for more information about the `*** Test Cases ***` or `*** Tasks ***` section.
 
-<!-- TODO maybe more references to Test Setup/Teardown or Documentation? -->
+{/* TODO maybe more references to Test Setup/Teardown or Documentation? */}
 
 ### 2.1.2.4 Introduction to `*** Keywords ***` Section
 

website/docs/chapter-02/01_suitefile.md

@@ -1,11 +1,8 @@
 
 # 2.2 Basic Suite File Syntax
 
-<!--
-TODO:
-I think this section needs a bit more structure and we should introduce the concept of "settings" like [Documentation] already here and reference to Chapter 4.
+{/* TODO: I think this section needs a bit more structure and we should introduce the concept of "settings" like [Documentation] already here and reference to Chapter 4.*/}
 
- -->
 
 ::::lo[Learning Objectives]
 

website/docs/chapter-02/02_suitefile_syntax.md

@@ -1,9 +1,10 @@
 
 # 2.4 Keyword Imports
 
-<!-- To use Keywords that are not part of BuiltIn, which is always imported invisibly, you must import keywords into the current scope. Basically Two different sources of keywords.
+{/* TODO: To use Keywords that are not part of BuiltIn, which is always imported invisibly, you must import keywords into the current scope. Basically Two different sources of keywords.
 - Libraries, which contains low-level keywords actually implementing functionality, typically in Python.
-- Resource Files, which either again import libraries or other Resource Files or they specify User Keywords.  -->
+- Resource Files, which either again import libraries or other Resource Files or they specify User Keywords.  */}
+
 Robot Framework has a modular design that allows users to import keywords from external sources.
 Without importing external keywords into a suite, only the keywords from Robot Framework's BuiltIn library are available for use, due to them being imported automatically.
 Also the Robot Framework language statements themselves are available for use without importing them.
@@ -37,7 +38,7 @@ From a user perspective there are three different kinds of libraries:
 - **Custom Libraries**: These libraries are developed by the users themselves to solve specific problems or to encapsulate more complex functionality.
 
 Further more detailed information about the different types of libraries and are described in later chapters.
-<!-- TODO: Do we fulfill this promise? -->
+{/* TODO: Do we fulfill this promise? */}
 
 To import a library into a suite or resource file the `Library` setting is used in the `*** Settings ***` section followed by the name of the library as long as they are located in the Python module search path, which automatically happens if they are installed via `pip`.
 The name of the library is case-sensitive and should be taken from the library's keyword documentation.

website/docs/chapter-02/04_keyword_imports.md

@@ -20,7 +20,7 @@ Basically all standard and external 3rd party libraries offer these Keyword Docu
 
 Robot Framework offers the Keyword Documentation of its Standard Libraries at https://robotframework.org/robotframework .
 
-<!-- Keywords from Libraries and Resources can be called and can be documented either as HTML or in IDEs with Robot Support. -->
+{/* TODO: Keywords from Libraries and Resources can be called and can be documented either as HTML or in IDEs with Robot Support. */}
 
 
 
@@ -406,7 +406,7 @@ The error message would be: `ValueError: Argument 'y' got value 'Not_A_Number' t
 
 The advantage of using type hints is that the user get more information about what kind of values are expected and the keyword implementation can be simpler, because it can rely on the arguments being of the expected type.
 
-<!-- Just to understand that they are there and that they may document how values are handled or which are allowed. -->
+{/* TODO: Just to understand that they are there and that they may document how values are handled or which are allowed. */}
 
 
 ### 2.5.2.9 Return Types
@@ -430,7 +430,7 @@ Similar to the argument types, return types are optional and a more recent featu
 It is important to know that keywords without a return type hint are often still returning values!
 This is typically documented in the *Documentation* part of the keyword documentation.
 
-<!-- Keywords may gather information and return these to the caller of that keyword. A Documented Return Value may be present but often it is just written in the docs, due to new feature -->
+{/* TODO: Keywords may gather information and return these to the caller of that keyword. A Documented Return Value may be present but often it is just written in the docs, due to new feature */}
 
 
 

website/docs/chapter-02/05_keyword_interface.md

@@ -420,13 +420,14 @@ Get ISO Time
 ## 3.3.7 Keyword Conventions
 
 
-<!--
-TODO:
+
+{/* TODO:
 
 Should we have that  chapter???
 Opinions?
 And if, is this want we want to ask the participants to know?
--->
+*/}
+
 
 ::::lo[Learning Objectives]
 

website/docs/chapter-03/03_user_keyword.md

@@ -21,6 +21,10 @@ const config = {
     },
   },
   favicon: 'img/rf_favicon.png',
+  // Future flags, see https://docusaurus.io/docs/api/docusaurus-config#future
+  future: {
+    v4: true, // Improve compatibility with the upcoming Docusaurus v4
+  },
   organizationName: 'robotframework', // Usually your GitHub org/user name.
   projectName: 'robotframework-RFCP-syllabus', // Usually your repo name.
   trailingSlash: false,
@@ -103,67 +107,11 @@ const config = {
             to: '/docs/learning_objectives',
             position: 'left',
           },
-          // {
-          //   href: 'https://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html',
-          //   label: 'User Guide',
-          //   position: 'right',
-          // },
-          // {
-          //   href: 'https://robotframework.org/robotframework/#standard-libraries',
-          //   label: 'Standard Library',
-          //   position: 'right',
-          // },
-          // {
-          //   href: 'https://robot-framework.readthedocs.io/en/stable/',
-          //   label: 'API Documentation',
-          //   position: 'right',
-          // },
-
-          // {
-          //   href: 'https://slack.robotframework.org/',
-          //   label: 'Slack',
-          //   position: 'right',
-          // },
-          // {
-          //   href: 'https://github.com/robotframework/robotframework-RFCP-syllabus',
-          //   label: 'GitHub',
-          //   position: 'right',
-          // },
         ],
       },
       footer: {
         style: 'dark',
         links: [
-          // {
-          //   title: 'Docs',
-          //   items: [
-          //     {
-          //       label: 'Syllabus',
-          //       to: '/docs/overview',
-          //     },
-          //     // {
-          //     //   href: 'https://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html',
-          //     //   label: 'User Guide',
-          //     // },
-          //     // {
-          //     //   href: 'https://robotframework.org/robotframework/#standard-libraries',
-          //     //   label: 'Standard Library',
-          //     // },
-          //     // {
-          //     //   href: 'https://robot-framework.readthedocs.io/en/stable/',
-          //     //   label: 'API Documentation',
-          //     // },
-          //   ],
-          // },
-          // {
-          //   title: 'More',
-          //   items: [
-          //     {
-          //       label: 'GitHub',
-          //       href: 'https://github.com/robotframework/robotframework-RFCP-syllabus',
-          //     },
-          //   ],
-          // },
         ],
         copyright: `Copyright © ${new Date().getFullYear()} Robot Framework® Foundation - Syllabus of Robot Framework® Certified Professional`,
       },