[epic] Move to markdown wiki model for profile database and content (from spreadsheet)

[rufuspollock]

Context: we want to make it easier to contribute to the ecosystem project both in terms of profiles as well as general content e.g. notes on thinkers and movements.

To achieve this we want to make the site into more of a markdown (obsidian) wiki - a bit like we have done in web3 project.

The plan is to try using Flowershow so that we get all the functionality that is there e.g. wiki links etc (and start centralizing that!)

This brings us to the question: How do we integrate flowershow? Ecosystem is a ood example of a more complex app. Maybe does not integrate nicely 😄

Acceptance

• Ecosystem site content comes from markdown wiki pages
  • profiles https://ecosystem.lifeitself.us/profiles/life-itself
  • topics https://ecosystem.lifeitself.us/topics/development
  • activitys https://ecosystem.lifeitself.us/activitys/advocacy
• Ecosystem site using flowershow and only has ecosystem specific components (so less to maintain)

Features

• Obsidian links supported ✅2022-09-01 now that we are using flowershow v0.2
• FIX: topic: 0 and similar for activity in data conversion and fix

BONUS - may move to future!

• Edit this page on relevant pages (?)
• Landing page: Typing text for name of ecosystem so it can change to different things (so not tied to metamodern)
  • Revert to "emerging" ecosystem as general reference
• FUTURE referential integrity for topic and activity references etc

Tasks

• Design the upgrade @rufuspollock 🚧2022-06-28 in progress. See notes below and tasks
• Convert data over to markdown (in old ecosystem repo) Convert json databases to markdown files with frontmatter #79
• Flowershow conversion #81
  • Refactor lib/db.js to use contentlayer so that search etc keeps working (nothing is using old data/organization.db directly, yay!)
• Other fixes
  • Remove pages/search.js
  • Move pages/vis2.js (if wanted) to a markdown page (?)
  • find.js ?? ❌2022-09-01 will leave out of this repo for now
• Releasing the repository: force push over old repo content (assuming we don't just clean) ✅2022-07-05 did this and all working

graph TD

convert[Convert data over into content folder]
flowershow[Flowershow conversion]
integrate[Integrate content folder - copy it!]

convert --> integrate
flowershow --> integrate
integrate --> push[force push over old repo]

Releasing the repository

Removing sensitive data

• Analyse what sensitive data is there ✅2022-06-27 only thing we can see is some stuff in organization.db e.g. emails
• organization.db clean up ✅2022-07-08 we decided to just force push a new repo with orgs cleaned up
  • What are options?
    • filter the organization.db from history - see e.g. https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository
    • reset repo and start clean. Given that we may need this for flowershow upgrade may want to go this root ...
  • live with what's there

[rufuspollock]

@khalilcodes what remains here (separate from need to upgrade to latest flowershow soon!)? Are obsidian links supported? What about topic: 0 item?

[rufuspollock]

FIXED. this got done (ages ago e.g. last autumn 2022). May want a quick look at any things to carry over