ON standby due to lack of crew - The idea is to keep it simple to push the control balance from the geek to the users. To use existing tools to build a open network then let the users decide how to use it. Simple. And if you look at the fedivers all this already exists. https://unite.openworlds.info/indymedia/indymedia-reboot/wiki
Go to file
Admin ed9701c2b4 Update 'design-overview/README.md' 2023-03-31 19:10:04 +00:00
design-overview Update 'design-overview/README.md' 2023-03-31 19:10:04 +00:00
README.md Update 'README.md' 2023-03-31 19:04:46 +00:00
mockup.html Add viewport meta tag 2023-03-20 14:30:40 +04:00
styles.css First pass mockup 2023-03-19 22:37:27 +04:00


Indymedia Reboot

Gotta start somewhere and where better than usage code first.


To get a better feel for the content and how it will be interacted with, we start with the front end, trusting it will better inform us on how to shape the back.

While the desktop format reflects the original Indymedia layout, we must design a responsive layout, annoyingly mobile-first for obvious reasons.

We also must preserve accessibility and retain a readable page regardless of whether a user is accessing without JS, or with a command line browser, or a text reader, etc.

Any JS that is used must only provide enhanced function and can never be the only way to get something done.


  • Get public-facing mockup clean enough and behaving acceptably for most screen sizes
  • Article editor
    • Markdown- and WSWG choice
      • This allows for writing articles even without JS yes
    • Do we need any functionality that markdown doesn't provide? dont think so.
  • Database
    • Built around #KISS semantic web, hashtags, flow, ...
    • Fast to search by tag(s)
  • Newswire and Publishing (I/O)
    • RSS
    • ActivityPub
    • Other?