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 task 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] - todo by sabin
* [write minimal Lua extension] - done by leandre
* Practice semantic annotations todo by leandre
* prior work: check if similar extensions exist
* locate relevant papers todo by sabin and leandre
* [describe markup languages] starts 2025-02-08
* [describe Markdown processors]
* [describe collab-tools] todo by sabin 
* [generate PDF report from Markdown snippets] todo by jonas

## From 02-15

* Research different ways to extend Quarto
* define the project scope

## From 02-22

* [write Lua parser]
* [write Lua validator]
* [write Lua serializer]

## From 03-01

* Refine the prototype
* test edge cases
* gather community feedback

Month 2: Full Development & Testing

* Week 5: Improve prototype as required  
* Week 6: Optimize performance, improve error handling, and add customization options.  
* Week 7: Test across real-world use cases and ensure compatibility with different Quarto formats.  
* Week 8: Gather user feedback, make necessary improvements, and finalize core functionality.

Month 3: Finalize Documentation, Deployment

* Week 9: Write documentation, tutorials, and create a demo project.  
* Week 10: Conduct final testing and fix any remaining bugs.  
* Week 11: Release the extension and promote it within the Quarto community.(if possible  
* Week 12: Gather post-release feedback and plan for future improvements.