Todos
< DRAFT++ >
Things you can do to help. Most even if you don't make it to the base!
Contact → info@totalism.org
Revisions:
2016-06-07 stub
2020-09-05 moveover + quick overview
Ties to:
🔗projects — CHT proposed projects
🔗works — Semaphore: responsibilities & status of longer/recurring works
Table of Contents
¶Visit the base !
→ next.totalism.org for current/upcoming subseason.
For some things you can do here:
→ 🔗projects
→ next.totalism.org for current/upcoming subseason.
For some things you can do here:
→ 🔗projects
¶ * Contribute website content !
All pages are editable.
Just do it - there is admin oversight, so don't worry about writing something in the wrong place, or messing something up.
A good place to start is to make additions to the systematics:
* 🔗calendar: Check if your favorite events are already listed. Also historic ones, so future editions can be found.
* 🔗alike: Do you know of any other spaces like this?
* 🔗maps: Anything missing from a city you know well?
* more → 🔗systematics
All pages are editable.
Just do it - there is admin oversight, so don't worry about writing something in the wrong place, or messing something up.
A good place to start is to make additions to the systematics:
* 🔗calendar: Check if your favorite events are already listed. Also historic ones, so future editions can be found.
* 🔗alike: Do you know of any other spaces like this?
* 🔗maps: Anything missing from a city you know well?
* more → 🔗systematics
¶ * Ordering gear: Research choices & help buy
Help find the right products for gear we are currently 🔗ordering !!!
(Or even better - find them, and somehow help get it to the base).
Help find the right products for gear we are currently 🔗ordering !!!
(Or even better - find them, and somehow help get it to the base).
¶ * Promote!
Share the link, tell people, connect with another project, print some material and post it around.
Post on mastodon, diaspora, twitter, whatever.
Find profiles on 🔗contact. Also see 🔗pr.
Share the link, tell people, connect with another project, print some material and post it around.
Post on mastodon, diaspora, twitter, whatever.
Find profiles on 🔗contact. Also see 🔗pr.
¶Website Development & Server administration
This ties to 🔗E2H, the plaform running the site.
Also see 🔗dev-index.
### !!! #tomerge, actually ... also with 🔗projects
This ties to 🔗E2H, the plaform running the site.
Also see 🔗dev-index.
¶ * Help with server admin & dev-ops
Containerisation, Data, Deploying new software ...
It's running Debian.
Containerisation, Data, Deploying new software ...
It's running Debian.
¶ * Text-to-Chart graphics
See 🔗dev-charts.
Main checks: 🔗metrics/🔗poster and as a part of that 🔗subfinance (databox).
Something in D3 maybe?
See 🔗dev-charts.
Main checks: 🔗metrics/🔗poster and as a part of that 🔗subfinance (databox).
Something in D3 maybe?
¶ * Fix site CSS (especially for mobile)
All the CSS on the website is easily editable in pads.
Unsure about mobile device look (font-size and line-spacing).
* max-width & margin ???
* increase font-size ?
* line-spacing ?
* [...]
First simple step would already be:
* walk around the site
* find worst themes
* write them here!
All the CSS on the website is easily editable in pads.
Unsure about mobile device look (font-size and line-spacing).
* max-width & margin ???
* increase font-size ?
* line-spacing ?
* [...]
First simple step would already be:
* walk around the site
* find worst themes
* write them here!
¶ * Migrate maps to Open Street Maps (OSM.org)
🔗maps is running on Google Maps and that's not okay, even though they are public (so it's not a matter of "privacy", but rather extending the feature set).
See → 🔗dev-maps.
🔗maps is running on Google Maps and that's not okay, even though they are public (so it's not a matter of "privacy", but rather extending the feature set).
See → 🔗dev-maps.
¶ * Website RSS feed
... At least for some pages?
More: 🔗dev-rss.
Situation:
* Since the site is structured and not a "blog"-type sequential content, a "UPDATES DIFF" solution is needed.
Options:
A) Probably best to have curated diffs:
🔗whats-new is kind of a manual version of this
B) put the site on github:
* push E2H -> text there
http://stackoverflow.com/questions/7353538/setting-up-an-github-commit-rss-feed
C) concept of "editions":
tie to starred revisions (max 1 / 3 days)
to be released, has to be RFC !
... At least for some pages?
More: 🔗dev-rss.
Situation:
* Since the site is structured and not a "blog"-type sequential content, a "UPDATES DIFF" solution is needed.
Options:
A) Probably best to have curated diffs:
🔗whats-new is kind of a manual version of this
B) put the site on github:
* push E2H -> text there
http://stackoverflow.com/questions/7353538/setting-up-an-github-commit-rss-feed
C) concept of "editions":
tie to starred revisions (max 1 / 3 days)
to be released, has to be RFC !
¶ * Transclude + filter pages (as lines, as fragments)
Status:
* Transclude already works
* filter not
* it would also have to be "piped" somehow
Usecase example:
everything tagged with "#todo" should appear here!
Syntax:
<<<- #todo
Status:
* Transclude already works
* filter not
* it would also have to be "piped" somehow
Usecase example:
everything tagged with "#todo" should appear here!
Syntax:
<<<- #todo