Ethering
< DRAFT++ >
Table of Contents
¶INTRODUCTION
A highly effective ideation, organization & publication model, using Etherpad and 🔗E2H software.
This document gives a functional introduction, at all levels — basic, intermediate & advanced.
An example:
The CHT/Totalism knowledge commons.
The public website has been assembled by hundreds of participants accross 10 years, and maintained by a full-time editor. The "internals" are an extended document set (staged to release, limited access, etc), accessible only to a core-group of operators.
a view of the extent & inter-linkage of the documentation here.
A highly effective ideation, organization & publication model, using Etherpad and 🔗E2H software.
This document gives a functional introduction, at all levels — basic, intermediate & advanced.
An example:
The CHT/Totalism knowledge commons.
The public website has been assembled by hundreds of participants accross 10 years, and maintained by a full-time editor. The "internals" are an extended document set (staged to release, limited access, etc), accessible only to a core-group of operators.
¶* Documents (or "pads") are contained in a pod.
A pod can have thousands of documents, that can be edited by many people at the same time.
The name also includes the infrastructure that powers it.
A pod can have thousands of documents, that can be edited by many people at the same time.
The name also includes the infrastructure that powers it.
¶* You can open documents either in VIEW or EDIT mode.
The difference is the first part of the link, before the document name.
You can find the EDIT button on each VIEW page!
### [!] make reverse true as well ...... @@e2h-todo
### [!*] consider hiding "Edit CSS" by default (as nobody does it EVER) ........ @@e2h-todo
Tip: For reverse and practicality, we reccomend trying to set up the 🔗workflow-bookmarklets.
The difference is the first part of the link, before the document name.
You can find the EDIT button on each VIEW page!
Tip: For reverse and practicality, we reccomend trying to set up the 🔗workflow-bookmarklets.
¶* VIEW mode is ... normal websites
Rich-text ("hypermedia") documents — with structured text, images, graphs, charts, and videos; you can follow links both inside ("internal links"), and outside the pod.
Rich-text ("hypermedia") documents — with structured text, images, graphs, charts, and videos; you can follow links both inside ("internal links"), and outside the pod.
¶* EDIT mode is ... real-time collaborative writing
Any number of people can edit the document simultanously, at the same time.
Every change is automatically saved, there is no special save button.
All changes persist, and can be easily rolled back. (So, nobody can break or vandalize things).
It's reccomended that when editing, you open the documents side-by-side, and refresh the
Any number of people can edit the document simultanously, at the same time.
Every change is automatically saved, there is no special save button.
All changes persist, and can be easily rolled back. (So, nobody can break or vandalize things).
It's reccomended that when editing, you open the documents side-by-side, and refresh the
¶* Editing is trivially simple
* You open the edit link.
* You scroll up and down the document.
* You position the cursor where you want to add something.
* You start writing.
* You open the edit link.
* You scroll up and down the document.
* You position the cursor where you want to add something.
* You start writing.
¶* Learning basics of computer use will help you use the system more effectively.
You might not consider yourself a "computer person".
But this is not about computers, but about collaborating with other people.
###AWK (You don't need to be a car person, but you still need to understand the simple basics of driving to stay on the road ... Except if you have a chauffer.)
You might not consider yourself a "computer person".
But this is not about computers, but about collaborating with other people.
¶* Your contribution to the pod is essential !
When collective adopted the pod system as the way to organize together, ideas expressed in other means (in chats, emails, unwritten conversations, etc) — will not reach others in the same way.
You might currently be more used to another system of interacting, but you should soon see the clear benefits of structured collaboration.
they do if you would express them in the pad system.
... Except if the chauffeur will write them for you.
When collective adopted the pod system as the way to organize together, ideas expressed in other means (in chats, emails, unwritten conversations, etc) — will not reach others in the same way.
You might currently be more used to another system of interacting, but you should soon see the clear benefits of structured collaboration.
¶* Work with the pod keepers
Every collective appoints Mentors & Editors, which will make sure you are successful in contributing to the collective.
With their help, you will progressively master good contribution practices!
Every collective appoints Mentors & Editors, which will make sure you are successful in contributing to the collective.
With their help, you will progressively master good contribution practices!
¶* Keep improving
By learning the more advanced concepts, you can significantly increase your collective's expressive power, and also help others.
By learning the more advanced concepts, you can significantly increase your collective's expressive power, and also help others.
¶* Learn & remember basic keyboard shortcuts
Basic keyboard use is essential to good
See → 🔗workflow-basics !
Learn to work rapidly.
ctrl+pg up/down
etc
------------------------
[!] >david : make a test app ;-) ........ #dev.ideas
Basic keyboard use is essential to good
See → 🔗workflow-basics !
¶* Don't even try to work on documents on mobile
It works, but is a waste of time.
You will be much more effective & comfortable on a laptop.
It works, but is a waste of time.
You will be much more effective & comfortable on a laptop.
¶* Search for content within the document
Use Ctrl+F in your browser to find things.
This will be especially useful with the syntax tags below!
Use Ctrl+F in your browser to find things.
This will be especially useful with the syntax tags below!
¶* Learn and use other basic keyboard shortcuts
* Pg Up / Pg Down
* Ctrl+X , Ctrl+V
More → 🔗workflow-basics !
* Pg Up / Pg Down
* Ctrl+X , Ctrl+V
More → 🔗workflow-basics !
¶* Don't delete content on your own
Only strike it out!
Wait for co-editors to acknowledge, and (re)move the content.
Only strike it out!
Wait for co-editors to acknowledge, and (re)move the content.
¶* Following positions & moving within pads
(You don't need to say if it's in document/pad, as it's apparant.)
¶ → "Line 64"
You'll be asked to navigate to the edit mode of the pad,
or you will want to bring a position to the attention of other people.
There's lines on the left of the editor.
* "let's go to one forty four":
line 144 in pad:
and, INDICATE YOU ARE THERE ("use checks" - make an x)
__________________________
* "2.1 in TOC!":
go to the "2.1" in Table of Contents
You'll be asked to navigate to the edit mode of the pad,
or you will want to bring a position to the attention of other people.
There's lines on the left of the editor.
¶ → "Check!"
("Acknowledge!")
== "[xxxx]"
A space for participants to they "acknowledged!" or "checked!" a point.
The initiator opens it at some spot like this:
"[x]"
Other participants find it & and add their mark:
"[xxxx]"
The spot has been provably "acknowledged" or "signed" !
(in the pad, you will see different colored 'x' due to authorship colors)
== "[xxxx]"
A space for participants to they "acknowledged!" or "checked!" a point.
The initiator opens it at some spot like this:
"[x]"
Other participants find it & and add their mark:
"[xxxx]"
The spot has been provably "acknowledged" or "signed" !
(in the pad, you will see different colored 'x' due to authorship colors)
¶* Styling & headering 101
Unlike Mediawiki, Markdown and other similar systems, Etherpad does this without syntax!
¶ * Auto-generated Table of Contents
like "[TOC]"
bold+underline text to create a heading
drop increments of 4 spaces for subheadings
helps a lot with content organisation!
like "[TOC]"
bold+underline text to create a heading
drop increments of 4 spaces for subheadings
helps a lot with content organisation!
¶ * Images by URL, via upload, or from other Pods
like "[img:https://example.com/test.png|width]"
width: "50%" or "300px".
like "[img:https://example.com/test.png|width]"
width: "50%" or "300px".
¶ * Adopt Styles from other pads ("-css")
a) "[style]" declaration:
[style:padname].
(includes "padname-css" pad as a stylesheet)
b) with url parameter "CSSPAD":
Example: http://localhost/CHT/E2H/e2h.php?_=cht5-frags&CSSPAD=hyperphoto
a) "[style]" declaration:
[style:padname].
(includes "padname-css" pad as a stylesheet)
b) with url parameter "CSSPAD":
Example: http://localhost/CHT/E2H/e2h.php?_=cht5-frags&CSSPAD=hyperphoto
¶ * Image galleries (from Pods, or local storage)
like "[###:part_of_filename]"
(Example on ### page.)
¶ * Text-to-Graph (flowcharts, diagrams, networks, etc)
using the "[graph]" directive & an own intermediate language
details → 🔗glia-graph
example → 🔗graph-index
using the "[graph]" directive & an own intermediate language
details → 🔗glia-graph
example → 🔗graph-index
¶ * Include maps
Allows referring to Google MyMaps, a collaborative editor for public maps.
* use as: "[gmap:google_mid|label]"
* gives rendered link with .kmz and .gpx exports
* (with Mirrorable) makes automatic offline backups
* see on 🔗maps (the top list)!
Allows referring to Google MyMaps, a collaborative editor for public maps.
* use as: "[gmap:google_mid|label]"
* gives rendered link with .kmz and .gpx exports
* (with Mirrorable) makes automatic offline backups
* see on 🔗maps (the top list)!
¶ * Include content via Date
as "[date:YYYY-MM-DD]" and then "[date++]"
This auto-includes related content (images, ...) from the archives, as subheadings.
Also useful as activity logs.
as "[date:YYYY-MM-DD]" and then "[date++]"
This auto-includes related content (images, ...) from the archives, as subheadings.
Also useful as activity logs.
¶ * Transclusion
###[!!**] lol move this out/document/something
1960's style !
a) [TRANSCLUDE:url]
* transclude any foreign page, via url
b) [TRANSCLUDEX::padname:query_part]:
* partial transclusion (by section, via "query_part")
* TODO: full inner page <???>
* TODO: page on any pod
a) [TRANSCLUDE:url]
* transclude any foreign page, via url
b) [TRANSCLUDEX::padname:query_part]:
* partial transclusion (by section, via "query_part")
¶Access Levels
###"lupine"
* Within a single pod, you will usually operate with documents
3 = public
2 = internal / members
1 = leadership
* Often, a document will have a main level (for example 3), with an aux document at another level (for example, 2):
Two second will point to the first.
### [!!] E2H— solve this programmatically
* Within a single pod, you will usually operate with documents
3 = public
2 = internal / members
1 = leadership
* Often, a document will have a main level (for example 3), with an aux document at another level (for example, 2):
Two second will point to the first.
¶ "BANGS", "HASHES": Marking tasks & improvement parts
[!!!] document the new, header-level syntax
"!!!" == "bangs": fix this (content), or, do this (task)
→ prioritized tasks to work on
"$$$" == "currently working on this"
→ one or few
"###" == return to this
→ many, not top priority
"!!!" == "bangs": fix this (content), or, do this (task)
→ prioritized tasks to work on
"$$$" == "currently working on this"
→ one or few
"###" == return to this
→ many, not top priority
¶ NAME TAGGING: Involving others
tag people, for example on todos, with
(you can then find and cycle theirs/yours via Ctrl+F search)
--------------- FOR
">leo" == "for leo":
todo for leo!
">all !!!!!!" == "for all":
something very important for all to look at.
--------------- FROM/BY/VIA
"<john" == "john>" == "from john":
john wrote this part
--------------- WITH
"+jessica" == "with jessica"
another person is involved / mentioned in what is written
--------------- (DEACTIVATED REFERENCE)
"_jessica"
... the mention was deactivated for some reason (for example: task deferred, etc)
tag people, for example on todos, with
(you can then find and cycle theirs/yours via Ctrl+F search)
--------------- FOR
">leo" == "for leo":
todo for leo!
">all !!!!!!" == "for all":
something very important for all to look at.
--------------- FROM/BY/VIA
"<john" == "john>" == "from john":
john wrote this part
--------------- WITH
"+jessica" == "with jessica"
another person is involved / mentioned in what is written
--------------- (DEACTIVATED REFERENCE)
"_jessica"
... the mention was deactivated for some reason (for example: task deferred, etc)
¶ SIGNED COMMENTS & INLINE CONVERSATIONS
(possibly, in early stage collaboration)
"<john>", or a shortened version, "<j>"
when replying, you should use:
<<<jane
you can also add a date, like
<<<junior , 2022-02-12
(possibly, in early stage collaboration)
"<john>", or a shortened version, "<j>"
when replying, you should use:
<<<jane
you can also add a date, like
<<<junior , 2022-02-12
¶ "GENERAL NOW-POINT" (for new, unsorted content)
== "((NOW))"
(with double brackets)
Usually at the end of the document.
== "((NOW))"
(with double brackets)
Usually at the end of the document.
¶ "NOW-POINTS" (current working location)
== "(NOW)"
== "$$$$"
CURRENT DOCUMENT WORKING LOCATIONS
Find them (Ctrl+F)
== "(NOW)"
== "$$$$"
CURRENT DOCUMENT WORKING LOCATIONS
Find them (Ctrl+F)
¶ "NEW-POINTS" or "FORKS" (space for new unsorted content)
== "<------------ (new)"
Every living document should have at least one.
A drop-off point for new fragments, usually written above.
Sometimes as "NAMED FORKS" (for specific types of new entries)
== "<------------ (new) More forks examples ↑"
Cycle them with Ctrl+F.
== "<------------ (new)"
Every living document should have at least one.
A drop-off point for new fragments, usually written above.
Sometimes as "NAMED FORKS" (for specific types of new entries)
== "<------------ (new) More forks examples ↑"
Cycle them with Ctrl+F.