Web MVP Initialization and Structure | Texsydo MVP (2025/08/25)
The Texsydo MVP repository requires a new structure that supports modular Kotlin and Gradle projects, as the Web MVP is transitioning from the Prototype stage. Such a structure must be scalable to be adapted by coming MVPs with a product approach.
Initialize Texsydo Web MVP project operations
Aug 10: PR #6 merged into
tsd/dev <- tsd/ops by tobiasbriones
It begins the project migration from MathSwe Prototypes by creating the project structure.
The structure consists of a Gradle, Kotlin non-modular project with default
libraries, such as ArrowKt. It includes MathSweKt with the pipe,
application, and composition operators.
The MVP migration will have a product focus, unlike the prototype, which was a development one. This initialization opened more requirements for the MVP. For example, separating the Jekyll static files to a separate repository to decouple the output (static site) from the tool (CLI app), as well as their licenses (user sites must not be affected by the AGPL license of the tool).
It still doesn’t add deploying support with jpackage, like the prototype (on
Gradle 8) did, since beryx is not compatible with Gradle 9, the version used
by the new MVP. The branch tsd/ops-_-beryx-jpackage-on-gradle-9 is pending
completion of the deployment support.
Creating the project structure initiated the migration process from Texsydo Web Prototype to MVP, while identifying important structural changes. The migration from prototype to MVP will consist of a product approach, as I’ve developed and validated most of the code concerning this migration.
Add docs for project Texsydo Web MVP
Aug 18: PR #7 merged into
tsd/dev <- tsd/docs by tobiasbriones
Texsydo Web MVP is being migrated from MathSwe Prototypes, which contains implementations dating from 2023, and this PR reflects the subproject docs in the MVPs repository.
Enable CLI and System APIs from Texsydo Web Prototype
Aug 21: PR #8 merged into by tobiasbriones
It migrates the structure of the CLI code to allow commands to be implemented, and adds the System API to run commands, such as DoRep for Jekyll. The next features to migrate will require support from both APIs.
Set up Gradle multimodule project tsd-web—mvp with Kotest
Aug 24: PR #9 merged into by tobiasbriones
Texsydo Web MVP and others, like FX (and Dev), are migrating from their Prototype form to MVP, which requires a modular monolithic structure for each major project (i.e., Web, FX, Dev).
The multimodule setup will allow TSD Web MVP to migrate its base code from the prototype and enable interfaces, such as a CLI or Web App, to reach production soon. Regarding testing, Kotest (unlike JUnit) fits FP better and is designed for Kotlin.
The multimodule structure and Kotest integration will provide the right spot for Texsydo Web MVP to reach production after finishing its migration, as well as the next MVPs coming.
The project organization keeps a Kotlin Gradle paradigm, introducing Gradle 9 and a modular monolithic structure for the MVP. That structure is meant to be utilized by the next migrating MVPs (Texsydo FX and Dev).
For testing, I settled on Kotest for its declarative and Kotlin-first design that aligns better with FP.
The modular structure will allow the migration of Texsydo Web MVP from its Prototype with scalability in mind. I devised that TSD Web must be decoupled into Web and Dev (i.e., development workflow), so the project structures are ready to allow such a design.