Current checkpoint (September 2026): central strategy and pipeline design now live in comms/docs/content-strategy.md. DAM supports that work. See the research checkpoint before following the historical intake-first direction below.
Aside: Issue for task tracking: https://github.com/life-itself/community/issues/1236
For SCQH and motivation see MOTIVATION.md
We have a growing need to better organize and surface our digital content—especially images and videos—for our new websites. A structured approach to managing this content will also support ongoing communications, social media, and storytelling work.
- High priority is collecting relevant raw image and video material for the new websites (e.g. the Hubs site, Orion site, Second Renaissance).
- We’re exploring two parallel approaches:
- Content Lake approach: systematically dumping all existing material into a central repository for future curation and AI-assisted processing.
- Page-led (pull) approach: identify what pages we’re building now, and pull together the best existing material to support those pages.
Right now, the pull approach is most urgent, as we need content for specific pages that are actively being built.
- Surfacing relevant content (esp. for the Hubs site first),
- And helping us organize or centralize the archive (content lake) long-term.
- Where is the content currently stored? E.g., Google Drive, YouTube, Google Photos, Canva.
- What is our main “content lake”? At present, probably Google Drive—though Google Photos may be better for some things (e.g. albums, visual browsing).
- How can we tag or flag content easily? Even informal systems like album names, shared docs, or lightweight tagging may help.
- Can AI assist in organizing over time? We expect to rely more on AI curation going forward, so dumping now and organizing later is acceptable.
- We are working on the website in the coming days, possibly live-editing with someone—you can join to help fill in media where needed.