2026-04-17 Managing the Lifecycle of Project Assets Like Drafts, Notes, and Outputs

I've got a question about how to deal with the lifecycle of assets in project management. I think I asked this before, actually quite recently.

For example, when I'm writing the Polycrisis to Metacrisis paper, there are:

• Drafts
• Ideas
• Notes
• Research
• The final draft and assets

Do I keep all of that in one project? Is it a subfolder of a second renaissance book project, so everything lives inside there, in subfolders?

When I want to find the tidy stuff, how do I tidy that up? Do I have a common wiki across the whole project?

When I move one of them onto the second resource website, that's another place to publish it, and the assets end up somewhere else (e.g., the PDF or other materials). How do you weave those together so that, when you want to make a change, you can publish it in one place without it showing up on the second release website too? You want these changes to flow through the system so that, if you make it in some local project repo, it flows into the larger book repo and then into the website or whatever.

It's a bit like cell updating in Jupyter notebooks. There's this desire to recompute things, but also to work on things in chunks and fairly autonomously, without having to touch everything in one massive notebook (metaphorically).