The basic plan 3 month plan is this:

* Month 1: Research, Planning and Initial Prototype
* Month 2: Full Development and Testing
* Month 3: Finalizing, Documentation and Deployment

The weekly tasks could be follows:

## Month 1: Research, Planning, and Initial Prototypes

* defining the problem starts 2025-02-05 todo by sabin
* setup the project collab-tools starts 2025-02-05
  * linux
  * git
  * radicle
  * quarto
* establishing problem related terms starts 2025-02-05
  * quarto
  * Lua
  * semantic annotations

### From 02-08

* [write anything in Lua] - done by sabin
* [write minimal Lua extension] - done by leandre
* [practice semantic annotations] - done by leandre
* [check if similar extensions exist] - todo by jonas and leandre and sabin
* [locate relevant papers] - todo by sabin and leandre and jonas
* [describe markup languages] starts 2025-02-08 - todo
* [describe Markdown processors] - todo
* [describe collab-tools] - todo by sabin 
* [PDF layout visual] - done by jonas
* [PDF layout citation] - done by jonas
* [generate PDF report from Markdown snippets] - done by jonas

### From 02-15

* [research different ways to extend Quarto] - todo by sabin 
* [define the project scope] - todo
* [advisor meeting agenda]
    * [time] how should we spend our time / balance (meeting, personal work)
    * [surprise] how to handle / forsee unexpected event
* [write an UML diagram of quarto]

### From 02-22

* [write Lua parser]
* [write Lua validator]
* [write Lua serializer]
* [document the development process]
* [write report Description of the program]

### From 03-01

* [refine the prototype]
* [test edge cases]
* [gather feedback]
* [write report introduction]
* [write report abstract]

## Month 2: Full Development & Testing

### From 03-08

* [improve prototype]
* [test basic functionalities]
    * parser
    * validator
    * serializer
* [midterm report]
    * ready to be send
    * understandable by the other

### From 03-15

* [midterm report]
    * March 19th 1215-16 (ca.) in Room 44.3-40
* [optimize performance]
* [improve error handling]
* [add customization options]
* [create test cases] for different scenarios
* Validate error handling and robustness

### From 03-22

* Test across real-world use cases and 
* [ensure compatibility] with different Quarto formats

### From 03-29

* [gather user feedback]
* [make necessary improvements]
* [finalize core functionality]

## Month 3: Finalize Documentation, Deployment

### From 04-05

* [write more documentation]
* [tutorials]
* [create a demo]
* [write report User Guide]

### From 04-12

* [conduct final testing]
* [fix any remaining bugs]
* [write report testing]

### From 04-19

* [release the extension] 
* [promote it] within the Quarto community
* [write report discusion and conclusion]
* [write report appendices]
* [write report bibliography]

### From 04-26

* [gather post-release feedback] 
* [plan for future improvements]

