gauthiier/wwwriting
gauthiier/wwwriting
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

... (bis)

Browse Source
This commit is contained in:
gauthiier 2023-09-02 11:39:17 +02:00
parent 6486f3ed58
commit b61f385ff6
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
README.md
View File

@ -3,7 +3,7 @@ title: WWWRITING WITH WIT
bibliography: wwwrite.bib bibliography: wwwrite.bib
--- ---
<img src="https://le-club-des-sans-sujets.org/w/wwwriting/img/rkwk101.gif" width="450"/> <img src="https://le-club-des-sans-sujets.org/w/wwwriting/img/rkwk101.gif" width="80%"/>
*Course prepared for the UvA in 2015* *Course prepared for the UvA in 2015*
@ -21,16 +21,17 @@ The idea in compiling this site-lesson is two fold:
(1) Present an alternative to the use of proprietary software for writing academic texts: (1) Present an alternative to the use of proprietary software for writing academic texts:
Considering the hegemonic use of proprietary software to write academic and non-academic texts (MS Word, Google Docs, Apple Pages, etc.) it is important to underline alternatives as these software not only “hide” their inner workings to scrutiny but most importantly may fall short in providing writers with adequate functionality required in writing academic texts [^1]. Obfuscation is impractical (and problematic) obviously so for academics in the Humanities. Considering the hegemonic use of proprietary software to write academic and non-academic texts (MS Word, Google Docs, Apple Pages, etc.) it is important to underline alternatives as these software not only “hide” their inner workings but most importantly may fall short in providing writers with adequate functionality required in writing academic texts [^1]. Obfuscation is impractical (and problematic) for academics in the Humanities.
We believe in texts that we can read, that is, we will utilise (as much as possible) software which is made “open” for us to read the source code and formats that are [human-readable](https://en.wikipedia.org/wiki/Human-readable_medium) as opposed to solely [machine-readable](https://en.wikipedia.org/wiki/Machine-readable_data). Hence, throughout the lessons, we will be inspecting files and writing ones that are augmented with special codes that machines can understand. This idea of writing "meta-data" into the text or more precisely _markup_ text in a file is very important in making sure the text is human _and_ machine readable. We believe in texts that we can read "all the way down". We will thus utilise (as much as possible) software which is “open” so that we can read the source code and formats that are [human-readable](https://en.wikipedia.org/wiki/Human-readable_medium) as opposed to solely [machine-readable](https://en.wikipedia.org/wiki/Machine-readable_data). Hence, throughout the lessons, we will be inspecting files and writing ones that are augmented with special codes that machines understand. This idea of writing "meta-data" into the text or more precisely _markup_ text in a file is very important in making sure the text is human _and_ machine readable.
(2) Offer a glimpse into methods, practices and systems of software writing: (2) Offer a glimpse into methods, practices and systems of software writing:
As you may already know, writing software is primarily a textual-based practice. Writing code is all about text, keyboards, text editors, line count, syntax and the likes. Hence an important amount of systems and technologies have been devised for the composition of software (as text). From syntax highlighting to version control, these systems have a long history and can possibly provide academic writers with powerful literary tools that can enable them to bolster their prose.[^2] In exposing (and historicising) these systems our objective is for the reader to relate to modern software writing systems not as merely a tool but as system with a culture. In no way we expect readers to become "programmers", far from this, we would rather present them the basics of writing text using (modern) computer systems while hoping that they'll develop a critical stance on these systems' genesis, conditions, limitations and capabilites.
As you may already know, writing software is primarily a text-based practice. Writing code is all about text, keyboards, text editors, line count, syntax and the likes. Hence an important amount of systems and technologies have been devised for the composition of software (as text). From syntax highlighting to version control, these systems have a long history and can possibly provide academic writers with powerful literary tools that can enable them to bolster their prose.[^2] In exposing and historicising these systems our objective is for the reader to relate to modern software writing systems not as merely a tool but as system with a culture. In no way we expect readers to become "programmers." Far from this, we would rather present them the basics of writing text using (modern) computer systems while hoping that they'll develop a critical stance on these systems' genesis, conditions, limitations, and capabilites.
## Scheme ## Scheme
The current site is segmented in six lessons covering the (very) basics of writing academic texts on a computer.[^3] The overall composition of these lessons is by no mean derived from obscure "Principles" or (even worst) "Best-practices" but rather stand as loosely coupled set of lessons that can be traversed all together (or not) in a short period of time. The site is neither a manual nor a manifesto and should be seen as a starting point into further developing (creative) technics and methods in text writing. The current site is segmented in six lessons covering the (very) basics of writing academic texts on a computer.[^3] The overall composition of these lessons is by no mean derived from obscure "Principles" or (even worst) "Best-practices" but rather stand as a loosely coupled set of lessons that can be traversed all together (or not) in a short period of time. The site is neither a manual nor a manifesto and should be seen as a starting point to further developing (creative) technics and methods in text writing.
* [Lesson 1: Text Encoding](https://le-club-des-sans-sujets.org/w/wwwriting/Lesson1.html) * [Lesson 1: Text Encoding](https://le-club-des-sans-sujets.org/w/wwwriting/Lesson1.html)