Added Example Exam

* Installed quizdown and created page

* First working version of the quiz

* The questions can now be defined inside the Quiz-tag

* Updated yarn lockfile

* Made syntaxhighlighting working (not for robotframework)

* Added syntaxhighlighting for robotframework (requires a modified version of quizdown)

* Using own version of quizdown with support for own hljs parsers

* Change darkmode colors (#6)

* Changed quizdown lib

* Added darkmode to quiz

* Added darkmode for code inside the quiz

* Fixed that wrong theme is shown on initial pageload

* Global import and quiz on all pages (#7)

* Added global import for the quiz-component

* Added quiz to normal docs page (2.3 executing)

* Result storage (#10)

* Added zustand as a central store and storing all quizzes in it. Now the property name is required that needs to be unique on each page.

* Updated quizdown-extended to 0.6.5

* Added storage for quiz results

* Saving quizresults in localstorage

* Added quizResultpage-sidebar

* Made first version of the quiz result page

* Fixed quiz prebuild script

* Next version of the resultsPage

* Added link to view the results to the quiz component

* Fixed build error

* Fixed resultpage

* Delete node_modules directory

* Update to quizdown extended 1.0.0 (#11)

* Started adding quizdown-extended v1

* massive refactoring regarding quizdown-extended

---------

Co-authored-by: cz-lucas <46531925+cz-lucas@users.noreply.github.com>

* test page build

* Add GitHub Actions workflow for Docusaurus deployment

* test page build

* example from pieter

* example from pieter

* bumpt to quizdown-extended 1.1.1

* bumpt to quizdown-extended 1.2.1

* slight changes

* just another trigger

* just another trigger

* just another trigger

* worked in feedback from PR in Chapters 0-3, 4 and 5 missing

* updated dependencies

* fixed #54, User Keywords now can also define argument types.

* releasable example exam

* added pdf to home page

---------

Co-authored-by: cz-lucas <46531925+cz-lucas@users.noreply.github.com>

Author: Snooz82

.github/.workflows/pages.yml

@@ -0,0 +1,59 @@
+name: Build & Deploy Docusaurus (GitHub Pages)
+
+on:
+  push:
+    branches: [ main ]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write         # required for actions/deploy-pages
+  id-token: write      # required for OIDC auth to Pages
+
+concurrency:
+  group: "pages"
+  cancel-in-progress: true
+
+jobs:
+  build:
+    name: Build site
+    runs-on: ubuntu-latest
+    defaults:
+      run:
+        working-directory: ./website
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Use Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 22
+          cache: yarn
+          cache-dependency-path: website/yarn.lock
+
+      - name: Install deps
+        run: yarn install --frozen-lockfile
+
+      - name: Build
+        run: yarn build
+
+      # Package the static output for Pages
+      - name: Upload Pages artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: ./website/build
+
+  deploy:
+    name: Deploy to GitHub Pages
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - name: Deploy
+        id: deployment
+        uses: actions/deploy-pages@v4

.github/.workflows/test-deploy.yml

@@ -1,4 +1,7 @@
 .idea
 folder
 __pycache__
-results
+results
+
+.vscode
+.devcontainer

.gitignore

@@ -1,4 +1,3 @@
-
 # 2.3 Executing Robot
 
 ::::lo[Learning Objectives]
@@ -200,7 +199,3 @@ There are basically two kinds of logging information in Robot Framework.
 
 Log messages can be written with different levels of severity (i.e. `INFO`, `DEBUG`, `TRACE`, `WARN` or `ERROR`).
 Which levels are written to the log can be controlled by the log level of an execution. Further information in later chapters.
-
-
-
-

website/docs/chapter-02/03_executing.md

@@ -362,7 +362,7 @@ Understand the concept of argument types and automatic type conversion.
 
 ::::
 
-Library Keywords may define the expected types of their argument values.
+Keywords may define the expected types of their argument values.
 The Robot Framework specification is predominantly a string-based language, therefore most statically defined argument values are strings.
 However, the actual implementation of the keyword may expect a different type of argument, like an integer.
 

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

@@ -161,7 +161,7 @@ See also Chapter 2 [2.5.2 Keyword Arguments](chapter-02/05_keyword_interface.md#
 
 Arguments are defined by `[Arguments]` followed by the argument names separated by multiple spaces in the syntax of scalar variables.
 
-Unlike Library Keywords, User Keywords cannot define argument types like `string`, `number`, etc., as described in the [2.5.2.8 Argument Types](chapter-02/05_keyword_interface.md#2528-argument-types) section.
+Since Robot Framework 7.3 User Keywords can define argument types like `string`, `number`, etc., as described in the [2.5.2.8 Argument Types](chapter-02/05_keyword_interface.md#2528-argument-types) section.
 
 
 ### 3.3.5.1 Defining Mandatory Arguments

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

@@ -0,0 +1,7 @@
+import Quiz from '@site/src/components/Quiz/Quiz';
+
+# Example Questions
+
+This example exam should give you the oportunity to check you knowledge and to get an impression what kind of questions may be asked in the real examination for RFCP®.
+
+<Quiz name="Example" src="Example.md"/>

website/docs/example-exam/Example-exam.mdx

@@ -0,0 +1,3 @@
+{
+  "label": "Example Exam"
+}

website/docs/example-exam/_category_.json

@@ -13,7 +13,11 @@ const config = {
   url: 'https://robotframework.org',
   baseUrl: '/robotframework-RFCP-syllabus/',
   onBrokenLinks: 'throw',
-  onBrokenMarkdownLinks: 'warn',
+  markdown: {
+    hooks: {
+      onBrokenMarkdownLinks: 'throw',
+    },
+  },
   favicon: 'img/rf_favicon.png',
   organizationName: 'robotframework', // Usually your GitHub org/user name.
   projectName: 'robotframework-RFCP-syllabus', // Usually your repo name.
@@ -31,7 +35,7 @@ const config = {
           routeBasePath: '/docs',
           sidebarPath: require.resolve('./sidebars.js'),
           // Please change this to your repo.
-          editUrl: 'https://github.com/robotframework/robotframework-RFCP-syllabus/edit/docusaurus/website',
+          // editUrl: 'https://github.com/robotframework/robotframework-RFCP-syllabus/edit/docusaurus/website',
           remarkPlugins: [remarkDirective, remarkTermDirective],
         },
         blog: false,
@@ -87,6 +91,11 @@ const config = {
             to: '/docs/chapter-05/overview',
             position: 'left',
           },
+          {
+            label: 'Example Exam',
+            to: '/docs/example-exam',
+            position: 'left',
+          },
           {
             label: 'LOs',
             to: '/docs/learning_objectives',
@@ -162,7 +171,9 @@ const config = {
         additionalLanguages: ['robotframework', 'python'],
       },
     }),
-  plugins: [require.resolve('docusaurus-lunr-search')],
+  plugins: [
+    require.resolve('docusaurus-lunr-search')
+  ],
 };
 
 module.exports = config;