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
mj-saunders
6ffffccf1b
Apparently mobile devise may lie about their screen size and this is the proposed solution. Reference: https://developer.mozilla.org/en-US/docs/Learn/CSS/CSS_layout/Responsive_Design#the_viewport_meta_tag |
||
|---|---|---|
| README.md | ||
| mockup.html | ||
| styles.css | ||
README.md
Indymedia Reboot
Gotta start somewhere and where better than usage code first.
Mockup
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.
TODO
- Get public-facing mockup clean enough and behaving acceptably for most screen sizes
- Article editor
- Markdown-only ?
- This allows for writing articles even without JS
- Do we need any functionality that markdown doesn't provide?
- Markdown-only ?
- Database
- Built around semantic web, hashtags, flow, ...
- Fast to search by tag(s)
- Newswire and Publishing (I/O)
- RSS
- ActivityPub
- Other?