You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am excited to announce the next major evolution of this project. What started as a minimalist tool under @mgks/docmd has grown into a robust static site generator. To support the next phase of growth, stability, and enterprise-grade features, we are making significant structural changes.
We are officially kicking off the development of docmd v0.4.x.
1. New Home, New Identity
We are moving from a personal project structure to a dedicated organization.
Version 0.3.x is stable, but it is monolithic. To achieve features like Browser-based Live Editing and Plugin Ecosystems, we need to decouple the core logic from the file system.
The v0.4.0 Monorepo Structure:
packages/cli: The command-line interface you know and love (init, dev, build). This handles the file watching and local server logic.
packages/core: The isomorphic brain of docmd. It takes Markdown and Config in, and spits HTML out. No file system dependencies. Runs in Node.js, Browsers, and Edge workers.
packages/theme-default: Our built-in themes (Sky, Ruby, Retro) extracted into a standalone package.
packages/live: The engine powering the new Live Editor.
3. Why are we doing this?
Stability: Separating concerns allows us to write better tests for the core logic without worrying about the CLI environment.
Portability: You will be able to embed the docmd compiler directly into your own React/Vue/Svelte apps.
Extensibility: This architecture paves the way for a proper Plugin API in v0.5.x.
4. We want your feedback!
This is an open source project, and we want to build what you need.
What features are missing from v0.3.x?
What pain points do you have with the current configuration?
Are there specific integrations you need?
Please drop your thoughts, feature requests, or questions below. ⬇️
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
docmd
Uh oh!
There was an error while loading. Please reload this page.
-
Hello community! 👋
I am excited to announce the next major evolution of this project. What started as a minimalist tool under
@mgks/docmdhas grown into a robust static site generator. To support the next phase of growth, stability, and enterprise-grade features, we are making significant structural changes.We are officially kicking off the development of docmd v0.4.x.
1. New Home, New Identity
We are moving from a personal project structure to a dedicated organization.
@mgks/docmdto@docmd/core(and related packages).2. The Shift to Modular Architecture
Version 0.3.x is stable, but it is monolithic. To achieve features like Browser-based Live Editing and Plugin Ecosystems, we need to decouple the core logic from the file system.
The v0.4.0 Monorepo Structure:
packages/cli: The command-line interface you know and love (init,dev,build). This handles the file watching and local server logic.packages/core: The isomorphic brain of docmd. It takes Markdown and Config in, and spits HTML out. No file system dependencies. Runs in Node.js, Browsers, and Edge workers.packages/theme-default: Our built-in themes (Sky, Ruby, Retro) extracted into a standalone package.packages/live: The engine powering the new Live Editor.3. Why are we doing this?
docmdcompiler directly into your own React/Vue/Svelte apps.4. We want your feedback!
This is an open source project, and we want to build what you need.
Please drop your thoughts, feature requests, or questions below. ⬇️
Beta Was this translation helpful? Give feedback.
All reactions