Note: THE TECHNICAL DOCS HAVE MOVED. For the sake of my own sanity, all technical documentation regarding Write.as/WriteFreely has been moved to a dedicated repository.
This repository encompasses the whole of both the editorial and developmental processes involved in creating bilge.world.
See my 2020 reflectory post for a few more details.
-
As part of my continued exploration of Git as an editorial tool, I have done my best to make use of as many GitHub-specific features as possible.
-
The Psalms' Project Board tracks ideas, notetaking, research, documentation, drafting, revision, and extra-site discourse (like Tweets or HackerNews comments.) Its left-most column also documents style and technical changes to its code.
-
I've been using Issues to document just about anything, including all of the above, as well as any other specific subject involved (ex: an "official" wallpaper pack.)
-
Commits function as a chronological revision-tracker which I have indeed made use of in a few, particularly dire writing situations.
-
I've been slow at integrating the Wiki, but its uses - such as documenting specific editorial definitions - will continue to be expanded.
-
Discussions are an intriguing possibility for external feedback (stop by and say something! really!,) but explaining why my general audience should have a GitHub account to participate even if they have zero interest in dev shit is going to be difficult.
-
Within the code, you'll find my voice notes, an image library, and a variety of other miscellaneous associated files (better organization is coming.)
