User:Kiara/Research/WebSpell/Prototypes: Difference between revisions
| Line 148: | Line 148: | ||
== 7.1 Eleventy == | == 7.1 Eleventy == | ||
<code>05-01-2025</code><br> | |||
To learn eleventy, I used the first step described on the official website and [https://learn-eleventy.pages.dev/lesson/1/ this tutorial].<br> | To learn eleventy, I used the first step described on the official website and [https://learn-eleventy.pages.dev/lesson/1/ this tutorial].<br> | ||
The tutorial is a bit confusing after the official guide. I would recommend starting directly with one of the tutorials linked at the bottom of the official guide ([https://www.11ty.dev/docs/#tutorials-and-starter-projects here]).<br> | The tutorial is a bit confusing after the official guide. I would recommend starting directly with one of the tutorials linked at the bottom of the official guide ([https://www.11ty.dev/docs/#tutorials-and-starter-projects here]).<br> | ||
Anyways, this tutorial is helping (not explicitly, but still) to understand the structure of a project directory: [[File:Folder-tree-eleventy.png|500px|frameless|center]] | Anyways, this tutorial is helping (not explicitly, but still) to understand the structure of a project directory: [[File:Folder-tree-eleventy.png|500px|frameless|center]] | ||
This tutorial is pretty neat for the fact that it contains and explains some accessibility tips. | |||
I am beginning to see the potential of eleventy. Since we use nunjucks, markdown and html we can build templates and reusable code snippets, which is extremely handy when a website has recurring elements on every page (a logo, a menu, a footer, etc.)! | |||
I am now reaching a part where we need to use javascript. Eleventy already runs through node.js, so little note to myself: check the website weight and compare with W ---> is JS really necessary? | |||
</div> | </div> | ||
</div> <!-- end of the page is here --> | </div> <!-- end of the page is here --> | ||
Revision as of 18:45, 5 January 2026
| Research Contents |
|---|
| General page |
| — Notes |
| — Project Proposal |
| — Thesis Outline |
| — (more or less) Rapid Prototypes |
Prototype #0 Invoking the Holy Handmade Web
Single webpage made during methods class to mock J.R. Carpenter's text
https://hub.xpub.nl/cerealbox/~kiara/methods/handmade-web/
Prototype #1 Pure HTML home page
This is a 99% HTML home page (1% of CSS)
https://kirayana.codeberg.page/xpub-GRS-prototypes/prototype_01/
Prototype #2 Nomai home page
A home page using the Nomai Script[1] to map out the website.
Each branch of the script links to a page, allowing for a non-linear reading, wandering and mystery.
The script is acting as a code, making also a mise en abîme between the script itself and web languages.
[1] The Nomai Script
The Nomai Script is an ancient fictional language created for the video game Outer Wilds. The Nomais were an ancient population that explored galaxies and left traces of their passage by writing on various surfaces. The script resembles spirals with branches and complex architecture. The spirals almost loop into each other, forming entire conversations.
Resources:
- Nomai Writing, blog post by Evan Fields (no game spoilers)
- nomai-writing.com, the online translator built by Evan Fields
- changing the handwriting factor or seed integer: not really interesting, for future tests I use handwriting: 0.5 and seed: 2500
- the website offers a "download" option that is not super practical (it save the web page) but inspecting it allows to get the svg paths to replicate the shape!
Examples of "spell ring" in Nomai script, using nomai-writing.com:
Prototype #3 Nomai spiral and translation concepts
As seen in the Prototype #1, I wrote a draft of introduction for the website. Then I gave it to nomai-writing.com and got this much more relevant result:
From this, I could draft a shorter text so the spiral is smaller and the details more accessible and usable as links to the other pages. To make the text readable, the interface could have a button offering the actual text on-click.
Prototype #3 The web-based prototype
The text used for this prototype is the following:
Here gather the Guardians of the Web. The enchant..e..r..esses, sorcere..rs..ses, witches and wizards of CSS and online-caring. Through CSS rituals, cyber incantations and various other magic interventions, they work quietly towards a common unspoken goal: caring, cherishing, nurturing the sacred space that is the web.
and this is the Nomai output:
14-10-2025 The homepage is looking good -- the spiral is a svg path though, breaking it down into different chunks to circle into <a> tags is going to be quite a mess...
Also remains the enigma of the content, since the intro text mentions people, it could be a repository of references for my research (actually: genius??? I'm having the idea while writing, didn't think about it before!!)
~ Coming soon: list of the references present on the website ~
Prototype is still available at https://kirayana.codeberg.page/xpub-GRS-prototypes/
Prototype #4 Neocities code-a-thon
Page made during the neocities code-a-thon of 10-11-2025, hosted at .zip by Roos Groothuizen https://for-the-record.neocities.org/05_Nightmare
Prototype #5 The Indie Web Puzzle
This is a poster puzzle, showcasing some of the websites listed on https://smallweb.cc/
The idea is to group together visually websites that pertain to the indie web, to build a non-exhaustive map of the indie web.
The puzzle is made out of screenshots of those websites.
Some characteristics for curation:
- special attention to visual/graphical materiality
- text-only pages are chosen only if they have very recognisable characteristics (font, colours, etc.)
- the screenshot is not necessarily taken from the homepage
Here's a first composition:
Prototype #6 The Ultimate Prototype
https://for-the-record.neocities.org/
this is a webring
containing webrings
grouping together all my web prototypes (chronologically)
it is hosted on neocities
it is indie
it is not complying with the web accessibility guidelines
but it is very singular and personal for sure
tbc...
Prototype #7 CMS
This prototype is actually a journey. I will log my exercises and experiments into discovering eleventy and [ W], in order to pick one as the running engine for my website (grad project).
7.1 Eleventy
05-01-2025
To learn eleventy, I used the first step described on the official website and this tutorial.
The tutorial is a bit confusing after the official guide. I would recommend starting directly with one of the tutorials linked at the bottom of the official guide (here).
This tutorial is pretty neat for the fact that it contains and explains some accessibility tips.
I am beginning to see the potential of eleventy. Since we use nunjucks, markdown and html we can build templates and reusable code snippets, which is extremely handy when a website has recurring elements on every page (a logo, a menu, a footer, etc.)!
I am now reaching a part where we need to use javascript. Eleventy already runs through node.js, so little note to myself: check the website weight and compare with W ---> is JS really necessary?
