commit 79e1723d578ed1db77888a332cfd12c24683e3ca
parent d7106bed1c86d248db5c48fb3713c28dda381928
Author: ugrnm <ugrnm@web>
Date: Fri, 6 Nov 2026 15:58:10 +0100
Diffstat:
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/editing.mdwn b/editing.mdwn
@@ -28,7 +28,9 @@ We do not have fine grained permissions and would like to implement as little bu
* **[[Projects]]**: needs some cleanup, but workflow is stable. Basically each project should have a oneliner and an internal dedicated page. A project page needs to follow a simple template with three sections: 1. a descriptive introduction, 2. a sections explaining the relevance to permacomputing ideas and principles, 3. a section about the limits of the projects, 4. a section with relevant links. Keep it short and to the point See [[cerca]] for a good example. Only add projects that are really relevant to permacomputing, not the first thing you find that you might find remotely interesting. The project entries can be written by anyone, and it's also an option to do that with the assistance of a project's creator(s), assuming they are willing to engage with the critical part about the projects own limits and challenges
-
+* [[Assessments]]: in dire need of cleanup, rethinking, etc
+
+* [[workshop]]: this page is an index for existing and new practical technical documentation, HOWTOs, IRL workshop scripts and material, project blueprints that could be reused by other groups, etc. The workflow is simple. For new projects 1. add/create your page in the "Work in Progress" section, 2. when finalised move it to the "Released" section. For existing released projects, feel free to update/fix/correct the material, however if you want to depart from it too much, just fork it and follow the workflow of new projects and indicate/links that this is based on previously released existing entry xyz, because it's nice.
(Copy)editing style
@@ -113,10 +115,7 @@ Reference style
---------------
When referencing, please use the [Notes and Bibliography version of The Chicago
-Manual of
-Style](https://www.chicagomanualofstyle.org/tools_citationguide/citation-guide-1.html).
-However, this is not an academic paper, don't overthink it or spend ages on it,
-try to make it work as best as you can, it's just to have some overall
+Manual of Style](https://www.chicagomanualofstyle.org/tools_citationguide/citation-guide-1.html). However, this is not an academic paper, don't overthink it or spend ages on it, try to make it work as best as you can, it's just to have some overall
consistency. No sweat :)
