---

breaks: false
---

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] - todo 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
* [reflect on report structure]
* [advisor meeting agenda]
    * [time]
    * [surprise]
* [write an UML diagram of quarto]

## From 02-22

* [write Lua parser]
* [write Lua validator]
* [write Lua serializer]
* Document the development process

## From 03-01

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

Month 2: Full Development & Testing

## From 03-14

* [midterm report]

* Week 5: Improve prototype as required
    * Test basic functionalities
* Week 6: Optimize performance, improve error handling, and add customization options
    * Create test cases for different scenarios
    * Validate error handling and robustness
* 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