SI26

(testing iframe compatibility with the wiki below)

<iframe src="https://practices.tools" frameborder="0" width="320" height="320" ></iframe>

Declarations

Declarations is an ongoing trans-disciplinary artistic research project into the poetic materiality of the CSS web-standard and its echoes on design and artistic practices.

A presentation of the declarations research project, with quotes and some illustrations of how the research is looking at declarative web-languages. It is important to read the first and second part (what is CSS, and the research questions).

We will watch the video essay by Miriam Suzanne [Why is CSS so weird https://www.youtube.com/watch?v=aHUtMbJw8iA&abchannel=MozillaDeveloper] as an important starting point to untangle some questions of the research together.

An evolving selection of declarations experiment, Doriane will present some of those progressively through the sessions.

Special issue: display and position

In the context this XPUB special issue, Declarations will focus on something quite specific. The idea is to take a specific angle on the learning of CSS: to be linguists at the same time than learning the language. The special issue is structured in 3 chapters:

1. exploring the linguistic aspect of web-languages 2. investigating & documenting cultural uses of specific CSS properties 3. speculation as a tool to think about it differently

Two CSS property have been choosing in that regard: display and position. They are interesting because they show how CSS is a language, notably by the use of non-numeric value and keyword with meaning. They also both have been subject to many change in the standard: unfolding a whole cultural history of the web that lies in the words it uses.

By reading the standard it appears that this is a rather complex propeties, what does it mean for certain things to be block and other the be inline? what does it mean to be inline-block? What does the words **block and inline** means? how where they chosen? by who? How are they implemented, what complexities or differences are often unseen in those processes?

Standard means blurry and frictions

CSS is a standard, meaning its edges are blurry. CSS is a standard maintained by the W3C (the World Wide Web Consortium). At its core, CSS is a set of recommendations, suggesting how things should be interpreted. Coming from dreams of accessibility and openness, it leaves the freedom to each software to follow or deviate from the standard. History -- notably the "the browser wars" - showed that there are divergences about which logic should dictate its evolution. Preferences of default styling, properties considered superfluous and thus removed (haikon lee CSS region), or unofficial ones forced in the standard. Knowing whether it makes sense to use a properties has became its own science, culminating in the well-named website Can I use. Technical decisions lead to cultural impact. We can only imagine how the choices of what makes it to the CSS standard could have redefined our attention to various visual elements, its impacts on our lives expanding far outside of the screens space. Therefore it seems fundamental for Declarations to ask what are the power dynamics, as well cultural positioning, at play in the CSS standard? Who are the actors of this political ecosystem and what are their motivations?

One the desire of Declarations is to create a corpus and network of meaningfull CSS artistic practices as a tool to enter in conversation with the standard itself. Through transdisciplinarity, it tries to not only speak from a designer or publisher POV, but look at the work of artists, amateur, people with literary background, cultural studies, poets and hackers. The research wishes to enter in conversation with W3C people, and maybe have **a seat at their table**, but from a different perspective: one that is not only motivated by the technics of certain properties but also by **the meaning of the words**.

Prescriptive and descriptive

During the special issue, we will not only learn to make webpage with CSS, but also look at both:

• prescriptive side of CSS: the standard by the W3C, and its evolution
• descriptive side of CSS: the cultural use of CSS by amateur & designer over the evolution of the web

Inline-block fable

A little fable that show the linguistic nature of the CSS web-language in a curious way is the one of inline-block.

It can be easy for an educated web-developer to describe what is display: block;: well, they are big block that take all width, they stack vertically and take only the necessary height they need. Same apply for display: inline;: well, they are lines of text, going from left to right or right to left, and whenever there is no space left to write the next character, it flows to the next line. But let's try to explain with the same simple language what is display: inline-block;? Much harder.

However, that doesn't prevent us to use it. In fact, the same educated web-developer might know exactly when and where to use it in order to produce a desired result in terms of design, because they saw it in use by other and learn with instinct and try and error how and when to use it. It is very similar to how we learn to use natural language: we hear people say some words, and at some point we can use them in sentences, but that doesn't mean we can define them as one would do in a dictionnary, or as an ethymologist, or as a linguist. Our instinctive but limited understanding of inline-block highlight to me how CSS is really a language that we "speak" and "learned" by using-making the web.

In the special issue we will try to deconstruct this instinct and take the role of linguist. We will ask ourselves: "Wait, what does inline-block actually mean?".

Reader

A selection of references to go further.

Caption text

Header text	Header text	Header text
Example	Example	Example
Example	Example	Example
Example	Example	Example

• Nolwenn Maudet, Tactical Design (link to come, the english translation will be published through the research website https://declarations.style)
• J. R. CARPENTER, A Handmade Web http://luckysoap.com/statements/handmadeweb.html
• Zach Mandeville, Basic HTML Competency ... https://coolguy.website/basic-html-competency-is-the-new-punk-folk-explosion/
• Laurel Schwultz, My website ... https://thecreativeindependent.com/essays/laurel-schwulst-my-website-is-a-shifting-house-next-to-a-river-of-knowledge-what-could-yours-be/
• Femke Snelting, Dividing & Sharing https://constantvzw.org/verlag/spip.php?page=article&id_article=101&mot_filtre=5&id_lang=0#
• Frank CHimero, The web's grain https://frankchimero.com/blog/2015/the-webs-grain/
• Olia Lialina, A Vernacular Web 1,2,3 http://art.teleportacia.org/observation/vernacular/
• John Allsopp, A Dao of Web Design https://alistapart.com/article/dao/

Chapt.1 Words are events, they do things, change things (Entering CSS linguistics)

Monday 6 January

morning: presentation of declarations and of the special issue.

afternoon: a first exerice [Declarative companion](https://declarations.style/declarative-companion-le75-graphic-design.html) but in group to share knwoledge, on a pad, using octomode.

Monday 13 January

todo:

• small page that present display, and position, i will need iframes to start them!
• space to drop lot of images?

morning

• sharing moment about the **Declarative companions** made last time.
• css story of the day (Doriane pick one thing from the observatory and tell a story about it)
• meeting: `display` and `position`, the two properties we are going to look at.

   * outside of CSS what does those words means to you in graphic design?
   * outside of graphic design what does those words means to you?

• starting a media collection (nextcloud or wiki ?), to drop images of thing that echoes with the words: display, block, inline, flow, root, outer-inner, position, static, sticky, fixed, absolute, relative, inherit, initial.
• browsing exercice: go through website we know and try to pick up interesting example of all those uses, through the inspector and screenshoting
• starting reading the standard page

looking at the practice of arpentage (land surveying in EN)

Put forward from lower class worker desiring knowledge, but without academic background, splitting complex text between participants to only read 1 para then explain in simplest possible language to others. Creating diagonal reading / sensible (collective) understanding. Use for reading!

Monday 20 January

todo:

• to read for that day: Nolwenn maudet - tactical design translation

• css story of the day (Doriane pick one thing from the observatory and tell a story about it)
• introduction to browser extension, the tactical interest of browser extension, how do they work concretly
• **using CSS to reveal CSS, by styling element differently according to which property they are using**. making of the "lens" extension: when extension is activated it reveal in a graphical way the `display` and `position` properties on every website (ex: all element using `display: flex;` have a cyan outline, and we get information when hovering them)

Chapt.2 Every language has a grain (CSS Deep dive in ethymology & cultural usages)

from now on, we'll be dividing in two groups: one group focusing on `display` and `position`. groups will have moment to share back to the rest of the students their research progress.

Monday 27 January

No Class Meeting

Doriane in Berlin for a Declarations workshop

Monday 3 February

morning

• css story of the day (Doriane pick one thing from the observatory and tell a story about it)
• starting the arpentage (collective reading) of the W3C standard draft for `display` and `position`

afternoon

• using the [Scratch extension](https://declarations.style/scratch.html), to restyle collectively the standard pages
• slowly going forward a web2print zine of restyled standard pages

Monday 10 February

morning

• css story of the day (Doriane pick one thing from the observatory and tell a story about it)
• continuing the arpentage (collective reading) of the W3C standard draft for `display` and `position`

afternoon

• using the [Scratch extension](https://declarations.style/scratch.html), to restyle collectively the standard pages
• do we have a zine?

Monday 17 February

• what is a block in language/graphic design? what is a line in language/graphic design?
• can we trace the history of certain of those words? how does `sticky` came to be? how does `flex` or `grid` came to be? (there are interesting stories there)

Chapt.2 Parallel sessions

Tuesday 11 February, with Manetta

nb: ONLINE OPEN DAY 10-11 (Joseph?), 17-18 (Manetta?)