User:Francg/expub/thesis/thesis-outline: Difference between revisions

Revision as of 12:37, 1 October 2017

Thesis Outline

Draft

What you want the thesis to be about?

Ricardo Lafuente https://pzwiki.wdka.nl/mediadesign/Lettersoup (not very well documented ... oh well) I want the thesis to be a bridge between the digital and the handmade, showing a research focused on the study of techno-dependency and techno-phobia of people in society, showing discussions that can function as speculative future scenarios, e.g.: "Who would be able to design a book in a post-apocalyptic digital era where Adobe no longer exists (neither other similar software replacements)? maybe only coders." This could be an interesting argument to stretch out in order to analyze and interpret possible directions of the actual socio-technological influence.

For instance, the book "Conversations" shows how a book can be designed using markdown languages and to still keep a beautiful layout with code-based imagery. It offers a good example of a workflow (based on existing platforms + tools; namely etherpad (web based text editor), latex (specific mdown reader) or bash (shell scripting), which in this case involves "sociality" with a group of participants.

It is indeed a laborious handwork bearing in mind nowadays we have software to ease layout making, nevertheless it is a way to encourage designers to use different methodologies for design, becoming more developers in order to question not only the visual result, but our self-sufficiency in the creative process and the social significance of these tools we are using, in such speculative social situation.

What is exciting about this, is that markup text can transition and acquire the physical qualities of rough-looking printed matter and more; (e.g. "Autonomous Archive" project, html/css -> to printable PDF). What other publishing forms or collaborative spaces can this body incorporate? Would this material be aimed for designers, non-designers, youth, politicians... and to what purpose? What is the pedagogical value for morphing design, when looping it from the digital to a physical state and back again to a different form (e.g. using automated scans)? Can this type of work-flow be interesting for documenting a dialogue between man and machine and to highlight the potential of using code without loosing the quality and craft of a handmade work?

Bibliography

sarah garcin: the PJ machine (Publishing Jockey) ... https://www.youtube.com/watch?v=mvL6N168Dg4

Ricardo Lafuente https://pzwiki.wdka.nl/mediadesign/Lettersoup

https://www.forkable.eu/generators/dit/o/free/A3/dit-A3-001.pdf

http://conversations.tools

https://archive.org/details/designforbrain00ashb

https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet http://www.latex-project.org/ http://pandoc.org/ https://en.wikipedia.org/wiki/EPUB

Scribus is designed for layout, typesetting, and preparation of files for professional-quality image-setting equipment. It can also create animated and interactive PDF presentations and forms. Example uses include writing newspapers, brochures, newsletters, posters, and books.

- - -

Session 2 thesis outline + prototype

@@ Line 12: / Line 12: @@
 Ricardo Lafuente https://pzwiki.wdka.nl/mediadesign/Lettersoup (not very well documented ... oh well)
+I want the thesis to be a bridge between the digital and the handmade, showing a research focused on the study of techno-dependency and techno-phobia of people in society, showing discussions that can function as speculative future scenarios, e.g.: "Who would be able to design a book in a post-apocalyptic digital era where Adobe no longer exists (neither other similar software replacements)? maybe only coders." This could be an interesting argument to stretch out in order to analyze and interpret possible directions of the actual socio-technological influence.
-Edge between digital and the handmade / the physical
+For instance, the book "Conversations" shows how a book can be designed using markdown languages and to still keep a beautiful layout with code-based imagery. It offers a good example of a workflow (based on existing platforms + tools; namely etherpad (web based text editor), latex (specific mdown reader) or bash (shell scripting), which in this case involves "sociality" with a group of participants.
-In an post-apocalyptic digital era where Adobe no longer exists neither text processing softwares, only coders can produce books.
-The conversations project I think offers a good example of a workflow / platform (itself based on existing platforms + tools, namely etherpad + latex + bash / shell scripting) that involves sociality -- in this case a group of participants.
-GOOD to talk about the specific workflow you used in the Autonomous archive project, and ideally try to talk specificially about what that particular workflow did (what was exiciting / what worked well in the automated parts) that you would then like to extend / further develop in the context of your project. (IE this instead of just speaking abstractly about using different softwares).
-Ultimately: it's important to think about WHO is using your platform (you, others, designers / non-designers / youth / elderly / prisoners / politicians / ... ??? ).
-Looking at your portfolio site (franc-g.com) struck by the physical quality -- the feeling of hand made, presence of your own body in the work.
+It is indeed a laborious handwork bearing in mind nowadays we have software to ease layout making, nevertheless it is a way to encourage designers to use different methodologies for design, becoming more developers in order to question not only the visual result, but our self-sufficiency in the creative process and the social significance of these tools we are using, in such speculative social situation.
+What is exciting about this, is that markup text can transition and acquire the physical qualities of rough-looking printed matter and more; (e.g. "Autonomous Archive" project, html/css -> to printable PDF). What other publishing forms or collaborative spaces can this body incorporate? Would this material be aimed for designers, non-designers, youth, politicians... and to what purpose? What is the pedagogical value for morphing design, when looping it from the digital to a physical state and back again to a different form (e.g. using automated scans)? Can this type of work-flow be interesting for documenting a dialogue between man and machine and to highlight the potential of using code without loosing the quality and craft of a handmade work?
-[Steve: this could be a lot more specific. What could it be? Your "hands on practice" needs to be up front! What can you MAKE?]
-'''How it relates to your research at the Piet Zwart so far?'''
-Nowadays, the free software movement and the diversity of open source tools encourage designers, artists and developers to question the nature of the tool they are using and its place in their creative process. The tool shapes the work. Can we imagine a World without Adobe or similar software replacement, to create printed matter and more?
-The value of the "publishing machine" in this case is not so much that it's the SOLUTION to an automated publishing workflow, but rather it has a PEDAGOGICAL value for bringing design in a playful form into a collaborative space to open up design process (what IS design) to non-designers ... design as a performance.
-https://hackersanddesigners.com/s/Events/p/Publishing_Machines_Workshop
-This book documents an ongoing dialogue between developers and designers
-Interest in the potential of using code to .
-Desire to use the skills of code he's learned
-how to embrace some automation in a digital flow without losing the quality and craft of a hand made work
-( MM: Here I think of the work of Christophe Haag in his productions with latex such as Conversations  http://conversations.tools )
-Conversations documents discussions about tools and practices for typography, layout and image processing that stretch out over a period of more than eight years.
-The transcriptions are loosely organised around three themes: tools, communities and design.
-interdependencies between Free Software and design practice.