docs: add npm publication workplan and update TODO
- Created comprehensive NPM_PUBLICATION_PLAN.md with 9 phases - Covers bundling, testing, and npm publication process - Uses Rollup with marked.js as peer dependency - Targets 3-5 day implementation timeline - Updated TODO.md with current active tasks
This commit is contained in:
parent
66cbd5c3d8
commit
fd12bbd34a
2 changed files with 1587 additions and 0 deletions
1564
NPM_PUBLICATION_PLAN.md
Normal file
1564
NPM_PUBLICATION_PLAN.md
Normal file
File diff suppressed because it is too large
Load diff
23
TODO.md
Normal file
23
TODO.md
Normal file
|
|
@ -0,0 +1,23 @@
|
|||
# Todofile
|
||||
|
||||
This is a "to do next" file, particularly useful to keep the human and a coding assistant in sync.
|
||||
|
||||
The format is based on [Keep a Todofile V0.0.1](https://coulomb.social/open/KeepaTodofile).
|
||||
|
||||
The structure organizes **future tasks** by their impact, just as a changelog organizes past changes by their impact.
|
||||
|
||||
***
|
||||
|
||||
## [Unreleased] - *Active Vibe-Coding State* 💡
|
||||
|
||||
This section is for tasks currently being discussed with or worked on by the coding assistant. These are the ephemeral, flow-of-thought tasks.
|
||||
|
||||
1) Implement the NPM_PUBLICATION_PLAN.md
|
||||
2) Make sure that Markitect integration still works fine
|
||||
3) Update STANDALONE_PLAN.md and decide if it should be implemented
|
||||
|
||||
***
|
||||
|
||||
## Completed Tasks
|
||||
|
||||
*Recent completed tasks have been documented in CHANGELOG.md following Keep a Changelog format.*
|
||||
Loading…
Add table
Add a link
Reference in a new issue