TheAssignment

The assignment is also intimately tied to TheStructureOfTheClassHasBeenAbsolved.

In our pre-assignment meeting on 10.04.2020 we analyzed our current situations and brainstormed possible approaches to the curriculum that could resolve them. Among the things we were afraid were:

• a "business as usual" approach to classes and assignments
• difficulty with creating routines
• difficulty with adapting the physical school routine to your current setup
• lack of motivation
• expectations of quality and productivity you feel you can't achieve in the current cirumstances
• confrontation with the relevance of your work
• the question if learning can happen in design without a specific end goal (a final, designed "object")
• and crucially, the lack of community you all currently experience.

At the school, most learning happens communally, the classes and space are merely scaffolding that make it possible. Right now, you might be communicating, but you're not in a community.

In this assignment you are relieved of individual responsibility. Instead, that responsibility becomes shared. There is no specific result or many requirements to attain yet, this will be defined organically together. But there is a backbone: we will explore what it means to build a community. What concepts, guidelines, agreements will be formed? What images and visual information can mark it? As it is a community, it will be defined by the personal relationships that form it. You also should also consider how to expand wiki logic through design.

Directions in general:

1. Start, on the wiki itself. Place a half-formed ideas online in the hopes that someone else may complete it. This is a benefit of wiki, the ability for collaborative thinking! Be careful though; cryptic information, difficult language and lack of intent can make it hard for someone to join in.
2. To achieve the above, listen! Respect what is made. Intently read and look at the content and find ways to expand or branch away from it. Strengthen existing centers, don't create new ones. Please, avoid being destructive for the sake of it.
3. Help one another, if someone is struggling: a) ask for help and b) create articles to help them.
4. Focus on spotting patterns and concepts! It's crucial to make agreements, that's what culture is. Do certain type of articles look a certain way? Should the language be different depending on the information being discussed? Is there a strategy in images? How can you establish wiki infrastructure? It's crucial to organize a wiki, otherwise you risk making a chat room. There are many ways to organize it.
5. Keep the wiki clean and nice, like the studio. We all use Wiki, so we all try to maintain it in a usable state. This means revisions should be made to old articles, to adapt them to new guidelines/agreements, for example.
6. Either sign off with your real name (like so -- MislavZugaj), or post anonymously. Your account can be set in Preferences. Do NOT use a pseudonym. If you want to consider usage of pseudonyms, the consensus rule applies. Until then, the preceding agreement stands.
7. Work in projects. A project can be one extensive article, a vast catalogue of articles, or anything else that uses wiki. Because of wiki, every project should be collaborative, but it would be good practice to join a project and stick with it. Everyone should be involved in at least two projects.

Aims until the 8th of May (2 weeks):

1. The current "design" is rudimentary (literally, there is no styling), but can be modified. For now you should focus on content, or design through content, and organization. After the 8th of May the code will become more accessible; before that you can discuss changes and additions. See OurWikiDevelopment.
2. In two weeks the wiki should reach some mass, to get the ball rolling. What mass exactly means is up to you, i.e. you need to come to an agreement what mass is. The definition should be high on the priority agenda.

Aims until the critiques

• to be seen