Experiment

Design notes for Camilo:

The Miro Board should help as a visual reference for the structure as laid out below, but for the end-user I hope to eventually create a body-on-the-ground experience - instead of this bird-eye perspective. (I am considering to create a simple aesthetic style for each narrative 'cut", and "experience" - but I will have to re-visit this later). I explain some of these ideas below under front-end wishlist/suggestions.

Structure of pages and links:

Wikimedia pages, terms and syntax:

Wikimedia Page= Cut/Track/Manuscript (generative action/physical manifestation/Academic format)

A page is a run-on, linear narrative track that cuts along the KLS, which makes it possible for the reader to trace an academic manuscript These tracks have a point of beginning, and they end at another point of beginning

Sometimes a narrative cut/track splits off in multiple different branches. In this case the page end with the heading after which narrative track branches out. Links are offered to multiple "new" points of beginning under this last heading. This for example happens in cut2; 3. Aesthetic (in)action in BearWatch, which splits of into 2 "new" places of beginning (and also has a "hidden" third "new" place of beginning).

Different linking logics, terms and syntax:

Run-of-the-page tracks

Run-of-the-page tracks that can be traced as a linear cut through the KLS, are marked in Miro by a solid arrow

When people follow one cut linearly, they are "tracing" this narrative. There is not a lot of interaction, or transformative engagement taking place. When people choose to interact with the possibilities that are offered to divert or pivot on the way, it means that they are "threading" their own narrative. Such threading is intra-active between reader, writer, designer, and all the other more-than-human manifestive agents that shape the KLS.

Front-end options?

Rather than reading the text through a scroll-down format, I would like to see if there is a possibility to move "through" it, per (sub)heading.

Detours and returns

"Detours" and "returns" allow for users to thread their own narratives between cuts. They are marked in Miro by a striped arrow in a particular direction. They exist in 2 versions:

Detour= In text link, usually a hyperlinked word within the run-on text. (Black striped arrow in Miro)

Return= In text link, at the bottom of relevant headers you offered ways to return to previous point in your journey. They are currently more visually explicit than "detours" because they consist of stand-alone texts like; "Click here if you want to return" (Purple striped arrow in Miro). I am adding them at the moment, but might want to discuss at a certain stage to take some of them out.

Invitations to trail-off

"Invitations" to trail-off allow readers to wayfare or dwell- to be curious, to divert from previous trajectories, "waste" time and be curious. It is actually the main action that I hope my readers will engage in- and is also the most effective way to encounter "hidden" vistas and landmarks along the way.

Invitations start on a new wikimedia page, which I refer to as a "trail". It may connect multiple phenomena, or just one. The trail usually picks up where you left the track, or it will include return links.

Invitations to trail-off are marked by a thin dotted black line in Miro, and lead along one or more agential phenomena marked in Miro by green post-its.

Different Pop-up phenomena in the KLS: their terms, Miro-design and syntax

Pop-up phenomena are phenomena that either; de/markate the im/possibilities of the KLS, like Pressure ridges and Great White Beasts. are not so much invitations- as they are directive elements. They create the conditions under which the user can make decisions, and therefore also other patterns in the KLS. I envision them as visual pop-up' elements, that you may click to explore and understand better (read the accompanying text). I assume this means I need to design a visual element (most obviously an ice-pressure ridge) that can serve as a click-able pop-up.

Pressure ridges

"Pressure ridges" are re-directive agential forces that mark the de/limitations of the KLS, and the im/possibilities of how we can move through it. It's a referral to the agential forces and apparatuses at play which mark the extent of possibilities within a particular generative action - in this case it marks the boundaries of what is included in the KLS, and it also marks the boundaries of the extent that users can make tracing/threading/wayfaring choices. User choices may be generative to the materiality of the KLS that emerges to them when they engage with its possibilities- but it also marks that not everything is possible within a given phenomena, like this KLS.

Pressure ridges start on a new wikimedia page, which I refer to as a "ridge". It may connect multiple phenomena, or just one. The ridge usually picks up where you left the trail or the track, or it will include return links.

In very rare cases (so far only twice), a pressure ridge does not start a new page/ridge, but is rather part of a main cut/track as one of its headers. This happens when a pressure ridge can not be avoided, by redirecting. The cases so far are "Wayfaring the BW project Point of Beginning#Covid-19", and "Wayfaring the BW project Point of Beginning#Arctic travel".

Pressure ridges are marked in Miro as purple post-its, and their pop-up nature with thick blue dotted lines.

Blue Houses

Response-ability

Miro design:

Front-end wishlist/desires

I hope to eventually create a body-on-the-ground experience - instead of this bird-eye perspective.

This interface makes use of the story frames as sketched above: https://fielddaylab.wisc.edu/play/headlines/

some ideas:

Create a backdrop for each cut, with different versions. Regular track. Track with Detour. Track with invitation(s) to trail off. Track with pressure ridge.

Process Notes for round 5:

Letting yourself be lead from the trajectory, the detours, allow for opportunities to for example engagae, inspire, create, spend time. See "Spending time vista"

Perhaps Round 5 could be a discussion of the different vista's that have emerged?

Process documentation:

05-11-2024

collage vista's and landmarks?

30-10-2024

Ask Camilo to install https://www.mediawiki.org/wiki/Extension:Cite this is for Voices of Thunder#Response-ability

Also discuss how and where to put the references (each header?) AND at the end of each thread?

28-10-2024

Start thinking of visual language. I want a partial on-the-ground perspective with a horizon that indicates landmarks and vista's that help navigating, not a god's eye perspective. Could I generate a 3D model with Echo of my miro board? and then render and sketch out the horizon? for each heading? Or will I sketch different landmarks as they emerge when following the cut. Or both?

Start adding reference pictures here.

27-10-2024

Politics of recognition is an example of unresolvable tension, without any right way of doing things. In Invivo- I have marked these as "staying with the trouble" - They should pop-up as a category, at certain points of each cut. Like the other "vista's". They are added as bold in-text page links

I have started to think of categories for these "pop-ups": External influence/agential apparatus of PB monitoring, conservation, natural science etc./pressure ridges - Emergent insights/landmarks - Imaginaries that can function as buoys/vista's.

Navigation levels are now as follows I think (see Miro graph visualization):

Run-of-the page = cut (solid line) - doesn't avoid certain agential pressure ridges see below like covid or arctic travel.

In text links = are non-linear options/ reader agency to (re)turn to other cuts (striped line)

Bold in text links bottom of heading =

Either Green and purple post-its wayfaring invitations, to respond - or to be re-directed by agential pressure ridges (marked in miro by dotted line)

Or Vista's and landmarks = suggested "pop-ups" only when reader hits certain post-its. (those are the emergent insights around the ESE).

25-10-2024

The Wayfaring thread is a linear cut, it follows the BW project process. I add headers on level 4 and 5:

level 4

is response-ability/choices/ethical considerations

level 5

is External material agencies / pressure ridges

Not sure what to do with Politics of recognition yet - how it is connected to wayfaring (see 27-10 for further thought).

24-10-2024

Maybe wayfaring thread cut is indeed not linear, but has a point of beginning and weaves throughout the 2 other cuts. -Wayfaring is the process. -The ESE are the in-between spaces that emerge while wayfaring. These spaces are their own pages? Like the vista's suggested below? -The 2 cuts are the practices

15-10-2024

What if the vista's / landmarks emerge on the "horizon", when one hits certain "sidequests?"

14-10-2024

The narrative can't be the manuscript. because it is a knowledge product. The manuscript is then the decisions I made, and the process of an emergent project. So the encounters and the choices that each connect, or lay out a certain path. For example you can go straight from the workshops page to the output if you want - skipping the problematizing of "description".

Maybe each encounter (page, or subheading) is an ethical space of engagement, were different interests come together? This means that the previous decisions made (like the workshops in 2019 in my case), lead to the current encounter.

11-10-2024:

Cut 1: The page runs as the voices of thunder narrative (written out)

Place of beginning as an introduction of this thread, explaining what the thread is about, and in what way you as a reader/ researcher are invited to respond.

The cut is threaded with other intra-acting aesthetic actions like the workshop in 2019, the conference calls, the paper, the film, the website, which are each (running) pages themselves

06-10-2024:

Practice: aesthetic action (this is what I/we did - the paths of the map).

Space: corresponding ethics of willingness and boundaries (These are the different corresponding agential forces, e.g. refusal, care, curiosity).

Process: Wayfaring in the apparatus (this is the directional force - exerted by reader).

The logic I am trying out first is adding whole Manuscripts/cuts (aesthetic action) in 1 page and then adding its corresponding forces through links.

Here my H2

My text can go here. Well or not Well-written is just part of the process.

Here. i

am. camilo

there. me

bee

create. this

type of content

Template:CURRENTPAGE 22:52 Template:CURRENTUSER 354

Path 1

This is an Audio test

Subpath

This is my youtube video experiment: