Move demo docs to pages/_docs, add lingua.md; update site submodule

pages/_docs/astro-bloomz.md

@@ -0,0 +1,12 @@
+---
+title: Astro-Bloomz
+date: '2023-10-04'
+---
+
+Astro-Bloomz is a [[digital-garden]], whose defining feature are [[wikirefs]] (aka "bidirectional link"). These are links using the `[[double-square-bracket]]` syntax that link between files within a collection of markdown files. They can be used in any and all markdown files across the site, though unique filenames are required.
+
+"Bloomz" are the parts of a [[wikibonsai]] style digital garden meant to be shared, shown off, and cross-pollinatated -- but be careful not to get stung! 🐝
+
+[[wikibonsai]] style gardens in particular add a [[semantic-tree]], which is viewable as a sort of #tag tree called the [map-page](/map). It is built from [[index-type|index files]] whose content defines its structure using markdown lists and `[[wikirefs]]`. The files linked in the semantic tree are primarily [[entry-type|entries]] which act as concept summaries, much like a Wikipedia page. Each entry also displays back references, such as which posts link to those entries.
+
+These syntaxes and workflows aim to make large amounts of content more easily navigable without the need for algorithms and opaque search mechanisms (though those are also generally readily accessible).

pages/_docs/digital-garden.md

@@ -0,0 +1,13 @@
+---
+title: 🪴 Digital Garden
+date: '2021-08-04'
+---
+
+The defining feature of a [digital garden](https://twitter.com/wibomd/status/1703946098589548622) is the `[[wikiref]]` (or "[[wikirefs|bidirectional link]]"). By adding dense internal links, the pages of a site become descriptive of a topography of concepts which describe or are used in said site.
+
+Techniques found in the wild are typically a mix derived from [personal knowledge management](https://en.wikipedia.org/wiki/Personal_knowledge_management), [personal wikis](https://en.wikipedia.org/wiki/Personal_wiki), [tools for thought](https://numinous.productions/ttft/), [zettelkasten](https://en.wikipedia.org/wiki/Zettelkasten), and [evergreen notes](https://entries.andymatuschak.org/z4SDCZQeRo4xFEQ8H4qrSqd68ucpgE6LU155C) among others.
+
+_[[wikibonsai|WikiBonsai]]_ is the culmination and curation of what this particular gardener has learned and built.
+
+Also, "gardening" is a surprisingly common metaphor that [pops up](https://twitter.com/wibomd/status/1704147337738654189) in many unexpected places.
+

pages/_docs/doctype.md

@@ -0,0 +1,9 @@
+---
+title: Document Type
+---
+
+Document types, or 'doctypes', are synonymous with [Astro content collections](https://docs.astro.build/en/guides/content-collections/). They are types of markdown documents that are used to render content in specific ways. The following are the doctypes expected to exist in a [[wikibonsai]] [[digital-garden]]:
+
+- [`posts`](https://docs.astro.build/en/guides/cms/keystatic/#creating-a-new-post)
+- [[index-type]]
+- [[entry-type]]

pages/_docs/entry-type.md

@@ -0,0 +1,22 @@
+---
+title: Entry DocType
+---
+
+Like in a dictionary, encylopedia, or wikipedia, entries are one of the central document types to this template (besides [[index-type]]s and [[post-type]]s). They are atomic concepts and ideas that are meaningfully [[wikirefs|linked]] so as to understand how those concepts relate to one another.
+
+The breadcrumb trail is formed by the current entry's position in the [[semantic-tree]]. And footer links are built from both its position in the tree as well as the fore and back [[wikirefs]].
+
+### Markdown
+
+Entries will typically contain frontmatter and/or wikiattrs, and markdown text respectively:
+
+```markdown
+---
+frontmatter: attributes
+---
+
+:type::[[wikiattr]]
+
+Then follows the rest of the text for the document, 
+some of which might contain some more [[wikilinks]].
+```

pages/_docs/index-type.md

@@ -0,0 +1,62 @@
+---
+title: Index DocType
+---
+
+Index documents are the primary method of structuring the [[semantic-tree]]. They are one of the central document types to this template (besides [[entry-type]]s and [[post-type]]s).
+
+### Navigate
+
+- Via the [[map-page]].
+- Via [[wikirefs]].
+
+### Markdown
+
+Index files build the [[semantic-tree]], which can be viewed on the [[map-page]]. They are placed in the `./content/index/` directory and each file should contain a markdown outline with [[wikirefs]] that typically point to [[entry-type]]s (but can point to any [[doctype]]). They may or may not contain yaml [[frontmatter]].
+
+Documents should look like this (minus comments):
+
+(escape chars '\\' added to ensure raw text display)
+
+```markdown
+// file: i.bonsai.md
+
+- [[bk.how-to-read-a-book]]
+  - [[read]]
+    - [[4-levels-of-reading]]
+      - [[elementary-reading]]
+      - [[inspectional-reading]]
+      - [[analytical-reading]]
+      - [[syntopical-reading]]
+```
+
+The tree may also be broken up into multiple index files:
+
+```markdown
+// file: i.bonsai.md
+
+- [[bk.how-to-read-a-book]]
+  - [[i.read]]
+```
+
+```markdown
+// file: i.read.md
+
+- [[4-levels-of-reading]]
+  - [[elementary-reading]]
+  - [[inspectional-reading]]
+  - [[analytical-reading]]
+  - [[syntopical-reading]]
+```
+
+Both of the above examples will generate a tree that looks like this:
+
+```markdown
+i.bonsai
+└── bk.how-to-read-a-book
+    └── i.read
+        └── 4-levels-of-reading
+          ├── elementary-reading
+          ├── inspectional-reading
+          ├── analytical-reading
+          └── syntopical-reading
+```

pages/_docs/map-page.md

@@ -0,0 +1,5 @@
+---
+title: Tag Map Page
+---
+
+This page displays the full [[semantic-tree]] generated from the [[index-type]] documents.

pages/_docs/remark-wikirefs.md

@@ -0,0 +1,5 @@
+---
+title: Remark-WikiRefs
+---
+
+The `remark-wikirefs` package is responsible for handling the [[wikirefs]] markdown syntax. It can be found on [GitHub](https://github.com/wikibonsai/remark-wikirefs).

pages/_docs/semantic-tree.md

@@ -0,0 +1,13 @@
+---
+title: Semantic Tree
+---
+
+:plugin::[[semtree]]
+
+The semantic tree is built with the [[semtree]] plugin (see docs for details).It is defined by the documents in the [[index-type]] markdown files. It forms a conceptual hierarchy with the purpose of orienting one within the concepts of a site.
+
+In case it needs repeating:
+
+> “It is important to view knowledge as a sort of semantic tree. Make sure you understand the fundamental principles, i.e., the trunk and big branches before you get into the leaves/details or there is nothing for them to hang on to.”
+> 
+> ~ [Elon Musk](https://www.reddit.com/r/IAmA/comments/2rgsan/comment/cnfre0a/?utm_source=share&utm_medium=web2x&context=3)

pages/_docs/semtree.md

@@ -0,0 +1,5 @@
+---
+title: SemTree
+---
+
+The `semtree` package is responsible for building the [[semantic-tree]]. It can be found on [GitHub](https://github.com/wikibonsai/semtree).

pages/_docs/test-render.md

@@ -0,0 +1,6 @@
+---
+title: Test Render
+date: '2023-10-05'
+---
+
+This file is specifically to test [[wikirefs]] rendering of wikiembeds.

pages/_docs/test.md

@@ -0,0 +1,287 @@
+---
+title: Test
+date: '2021-08-04'
+---
+
+This is a page is for testing and showcasing the markdown styles in this template.
+
+## Markdown
+
+(some escape chars `\` are added to ensure raw display)
+
+### WikiRefs
+
+#### A Prefixed WikiAttr (see attrbox for output)
+
+```markdown
+:prefixed-wikiattr::[[wikirefs]]
+```
+
+:prefixed-wikiattr::[[wikirefs]]
+
+#### A Prefixed WikiAttr List (see attrbox for output)
+
+```markdown
+: prefixed-wikiattr-list :: 
+- [[wikirefs]]
+- [[feedback]]
+```
+
+: prefixed-wikiattr-list :: 
+- [[wikirefs]]
+- [[feedback]]
+
+#### An Unprefixed WikiAttr (see attrbox for render)
+
+```markdown
+unprefixed-wikiattr::[[wikirefs]]
+```
+
+unprefixed-wikiattr::[[wikirefs]]
+
+#### An Unprefixed WikiAttr List (see attrbox for render)
+
+```markdown
+unprefixed-wikiattr-list :: 
+- [[wikirefs]]
+- [[feedback]]
+```
+
+unprefixed-wikiattr-list :: 
+- [[wikirefs]]
+- [[feedback]]
+
+#### A WikiLink
+
+```markdown
+[[digital-garden]]
+```
+
+[[digital-garden]]
+
+#### A Typed WikiLink (check html for linktype css class)
+
+```markdown
+:typed-wikilink::[[digital-garden]].
+```
+
+:typed-wikilink::[[digital-garden]].
+
+#### A WikiEmbed (Markdown)
+
+```markdown
+![[test-render]]
+```
+
+![[test-render]]
+
+#### A WikiEmbed (Image)
+
+```markdown
+![[wikibonsai-way.png]]
+```
+
+![[wikibonsai-way.png]]
+
+#### Zombies
+
+#### A Prefixed WikiAttr (see attrbox for render)
+
+```markdown
+:zombie-wikiattr::[[zombie]]
+```
+
+:zombie-wikiattr::[[zombie]]
+
+#### A Prefixed WikiAttr List (see attrbox for render)
+
+```markdown
+: zombie-wikiattr-list :: 
+- [[zombie-1]]
+- [[zombie-2]]
+```
+
+: zombie-wikiattr-list :: 
+- [[zombie-1]]
+- [[zombie-2]]
+
+#### An Unprefixed WikiAttr  (see attrbox for render)
+
+```markdown
+zombie-wikiattr::[[zombie]]
+```
+
+zombie-wikiattr::[[zombie]]
+
+#### An Unprefixed WikiAttr List  (see attrbox for render)
+
+```markdown
+zombie-wikiattr-list :: 
+- [[zombie-1]]
+- [[zombie-2]]
+```
+
+zombie-wikiattr-list :: 
+- [[zombie-1]]
+- [[zombie-2]]
+
+#### A WikiLink
+
+```markdown
+[[zombie]]
+```
+
+[[zombie]]
+
+#### A Typed WikiLink
+
+```markdown
+:zombie-typed-wikilink::[[zombie]].
+```
+
+:zombie-typed-wikilink::[[zombie]].
+
+#### A WikiEmbed
+
+```markdown
+![[zombie]]
+```
+
+![[zombie]]
+
+#### Headers
+
+```markdown
+# Header 1
+## Header 2
+### Header 3
+#### Header 4
+##### Header 5
+###### Header 6
+```
+
+# Header 1
+## Header 2
+### Header 3
+#### Header 4
+##### Header 5
+###### Header 6
+
+#### Lists
+
+```markdown
+Lists:
+- One
+- Two
+- Three
+```
+
+Lists:
+- One
+- Two
+- Three
+
+#### Blockquote
+
+```markdown
+> Blockquote.
+```
+
+> Blockquote.
+
+#### Weblink
+
+```markdown
+[Weblink](https://astro-bloomz.netlify.app)
+```
+
+[Weblink](https://astro-bloomz.netlify.app)
+
+#### Code Block:
+
+```markdown
+```javascript
+// javascript
+for (var i=1; i < 101; i++){
+    if (i % 15 == 0) console.log("FizzBuzz");
+    else if (i % 3 == 0) console.log("Fizz");
+    else if (i % 5 == 0) console.log("Buzz");
+    else console.log(i);
+}
+\```
+```ruby
+# ruby
+ 1.upto 100 do |i|
+  string = ""
+  string += "Fizz" if i % 3 == 0
+  string += "Buzz" if i % 5 == 0
+  puts "#{i} = #{string}"
+end
+\```
+```
+
+```javascript
+// javascript
+for (var i=1; i < 101; i++){
+    if (i % 15 == 0) console.log("FizzBuzz");
+    else if (i % 3 == 0) console.log("Fizz");
+    else if (i % 5 == 0) console.log("Buzz");
+    else console.log(i);
+}
+```
+```ruby
+# ruby
+ 1.upto 100 do |i|
+  string = ""
+  string += "Fizz" if i % 3 == 0
+  string += "Buzz" if i % 5 == 0
+  puts "#{i} = #{string}"
+end
+```
+
+#### Inline Code
+
+```markdown
+Alright, `alright`, alright.
+```
+
+Alright, `alright`, alright.
+
+#### Tables
+
+```markdown
+| Rabbits | Foxes | Hedgehogs |
+|:------- |:-----:| ---------:|
+| 25      | 3     | 12        |
+| 100     | 10    | 20        |
+```
+
+| Rabbits | Foxes | Hedgehogs |
+|:------- |:-----:| ---------:|
+| 25      | 3     | 12        |
+| 100     | 10    | 20        |
+
+#### Text
+
+```markdown
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nulla imperdiet, eros in aliquet eleifend, felis tellus laoreet velit, a feugiat purus mi at arcu. Sed tempor congue gravida. Suspendisse sodales ultricies lacus, nec consequat mauris dictum in. Aliquam at lacus sodales, porta velit in, consequat mauris. Maecenas consequat fermentum tortor, vitae tincidunt sem porta vel. Sed elementum dui libero, vitae bibendum est imperdiet non. Curabitur sit amet libero quis nulla faucibus euismod. Cras condimentum ante tortor, a sollicitudin elit accumsan eget. Phasellus scelerisque mi nunc, nec finibus tellus volutpat et. In et finibus dui, eget commodo massa. Pellentesque vitae dapibus quam, sed venenatis augue. Mauris semper a leo ut rutrum. Curabitur sed ante nisl.
+
+Cras nec dictum turpis, ut tristique lectus. Duis posuere erat a dolor cursus interdum. Nulla sed turpis justo. Donec tempus turpis magna, in tempus dolor vulputate at. Nullam eget velit elementum, consequat lorem in, volutpat eros. Donec non dui sapien. Donec sed ultrices dui, eget interdum ipsum.
+
+Nunc a sapien eros. Suspendisse sollicitudin semper ligula. Praesent ut laoreet ante, nec blandit nulla. Pellentesque ac venenatis nisi. Integer tincidunt nisi ut eros consequat condimentum. Duis a odio tristique, malesuada lorem eget, mollis leo. Quisque in neque nec mauris sodales mattis ac molestie risus.
+
+Aenean et tortor lacinia lectus pulvinar tempus. Sed consequat nunc sed sagittis tempus. Integer consectetur turpis et suscipit posuere. Orci varius natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Etiam ultricies mi nec euismod ultrices. Aenean mollis tellus et magna semper, in gravida mi bibendum. In ex urna, fringilla sit amet viverra nec, euismod venenatis velit. Duis tincidunt erat semper est sollicitudin, a aliquet enim fermentum. Fusce in dui semper, suscipit dolor tincidunt, elementum nulla. In massa velit, finibus a felis ut, elementum bibendum nulla. Nunc malesuada consequat tellus, a auctor sem maximus eget. Donec eleifend enim sit amet libero finibus commodo. Vivamus at auctor eros, sed vulputate tortor. Nullam semper pellentesque eros, eu pretium leo pharetra et.
+
+Nunc luctus turpis sed leo scelerisque mattis. Aliquam pellentesque non risus a placerat. Vivamus congue ipsum eget vestibulum tincidunt. Sed vitae urna dolor. Suspendisse ac fermentum magna, ut iaculis ligula. Nam fermentum ante egestas, porta justo pharetra, euismod sapien. Integer eu feugiat lorem. Aenean vestibulum, justo in pretium facilisis, magna elit aliquam risus, a vestibulum orci enim vel turpis. Suspendisse potenti. Sed aliquet est vel sapien porta, eu lacinia arcu porta.
+```
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nulla imperdiet, eros in aliquet eleifend, felis tellus laoreet velit, a feugiat purus mi at arcu. Sed tempor congue gravida. Suspendisse sodales ultricies lacus, nec consequat mauris dictum in. Aliquam at lacus sodales, porta velit in, consequat mauris. Maecenas consequat fermentum tortor, vitae tincidunt sem porta vel. Sed elementum dui libero, vitae bibendum est imperdiet non. Curabitur sit amet libero quis nulla faucibus euismod. Cras condimentum ante tortor, a sollicitudin elit accumsan eget. Phasellus scelerisque mi nunc, nec finibus tellus volutpat et. In et finibus dui, eget commodo massa. Pellentesque vitae dapibus quam, sed venenatis augue. Mauris semper a leo ut rutrum. Curabitur sed ante nisl.
+
+Cras nec dictum turpis, ut tristique lectus. Duis posuere erat a dolor cursus interdum. Nulla sed turpis justo. Donec tempus turpis magna, in tempus dolor vulputate at. Nullam eget velit elementum, consequat lorem in, volutpat eros. Donec non dui sapien. Donec sed ultrices dui, eget interdum ipsum.
+
+Nunc a sapien eros. Suspendisse sollicitudin semper ligula. Praesent ut laoreet ante, nec blandit nulla. Pellentesque ac venenatis nisi. Integer tincidunt nisi ut eros consequat condimentum. Duis a odio tristique, malesuada lorem eget, mollis leo. Quisque in neque nec mauris sodales mattis ac molestie risus.
+
+Aenean et tortor lacinia lectus pulvinar tempus. Sed consequat nunc sed sagittis tempus. Integer consectetur turpis et suscipit posuere. Orci varius natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Etiam ultricies mi nec euismod ultrices. Aenean mollis tellus et magna semper, in gravida mi bibendum. In ex urna, fringilla sit amet viverra nec, euismod venenatis velit. Duis tincidunt erat semper est sollicitudin, a aliquet enim fermentum. Fusce in dui semper, suscipit dolor tincidunt, elementum nulla. In massa velit, finibus a felis ut, elementum bibendum nulla. Nunc malesuada consequat tellus, a auctor sem maximus eget. Donec eleifend enim sit amet libero finibus commodo. Vivamus at auctor eros, sed vulputate tortor. Nullam semper pellentesque eros, eu pretium leo pharetra et.
+
+Nunc luctus turpis sed leo scelerisque mattis. Aliquam pellentesque non risus a placerat. Vivamus congue ipsum eget vestibulum tincidunt. Sed vitae urna dolor. Suspendisse ac fermentum magna, ut iaculis ligula. Nam fermentum ante egestas, porta justo pharetra, euismod sapien. Integer eu feugiat lorem. Aenean vestibulum, justo in pretium facilisis, magna elit aliquam risus, a vestibulum orci enim vel turpis. Suspendisse potenti. Sed aliquet est vel sapien porta, eu lacinia arcu porta.
+```

pages/_docs/wikibonsai.md

@@ -0,0 +1,12 @@
+---
+title: WikiBonsai
+---
+
+![[wikibonsai-way.png]][^twt]
+
+Astro-Bloomz is a [WikiBonsai](https://github.com/wikibonsai/wikibonsai) project.
+
+![[astro-bloomz]]
+
+
+[^twt]: [explain](https://twitter.com/wibomd/status/1703930973371412699)

pages/_docs/wikirefs.md

@@ -0,0 +1,19 @@
+---
+title: WikiRefs
+---
+
+plugin::[[remark-wikirefs]]
+
+
+`[[WikiRefs]]`[^names] are a crucial part of the world of [[digital-garden|digital gardening]]. They are the basic building block of the interlinking accomplished in many gardens, including this one. They are rendered with the [[remark-wikirefs]] plugin, are rendered in a different color than external web links, and you can check out those docs for more details.
+
+But in short, This particular flavour of `[[wikirefs]]` includes three kinds of wiki constructs: wikiattrs, wikilinks, and wikiembeds.
+
+_WikiAttrs_ are formalized attributes of a file. They include a descriptive attrtype and a wikilink to another file. They look `:like-this::[[wikilink]]` (with a newline after) and are rendered in the attributes box (attrbox).
+
+_WikiLinks_ are traditional bidirectional links using the square bracket syntax and may appear anywhere in a file. There are `:typed::[[wikilinks]]` and regular untyped `[[wikilinks]]`. They are highlighted in a different color than external web links.
+
+_WikiEmbeds_ embed the content of the linked file into the current one in-place. Markdown files may be embedded as well as images, audio, or video files. WikiEmbeds look like `![[this]]`.
+
+
+[^names]: "wikiref" actually goes by many names: "[wikilink](https://en.wikipedia.org/wiki/Help:Link)", "[bidirectional link](https://maggieappleton.com/bidirectionals)", "[wikitext linking](https://tiddlywiki.com/#Linking%20in%20WikiText)","backlink", "[internal link](https://help.obsidian.md/How+to/Internal+link)", "humble double bracket internal link", to name only a few...

pages/lingua.md

@@ -0,0 +1,31 @@
+---
+title: Lingua e Internazionalizzazione
+---
+
+# Lingua e Internazionalizzazione
+
+Questo wiki è principalmente in italiano. Di seguito le opzioni valutate e la decisione presa.
+
+## Opzioni considerate
+
+### A — Solo italiano (1–2 ore)
+Sostituire le ~8 stringhe di interfaccia in inglese con italiano. Tutto il contenuto viene scritto in italiano. Nessun cambiamento strutturale.
+
+### B — Italiano di default, lingue miste tolerate (zero effort)
+Il wiki è una raccolta piatta di pagine: chi scrive in italiano lo fa, chi vuole contribuire in inglese può farlo. I `[[WikiLink]]` funzionano per nome file indipendentemente dalla lingua del contenuto. Opzione adottata per ora.
+
+### C — Bilingue completo `/it/` e `/en/` (1–2 giorni di sviluppo)
+Astro 6 supporta l'i18n routing nativo. Richiederebbe:
+- Dividere `pages/` in `pages/it/` e `pages/en/`
+- Aggiornare la content collection e la generazione degli URL
+- Aggiungere un selettore di lingua nella nav
+- Decidere come i `[[WikiLink]]` attraversano i confini linguistici
+- Un indice semtree per lingua o condiviso
+
+Il punto 4 è quello genuinamente complesso: il sistema wikibonsai non ha una risposta standard per i link cross-language.
+
+## Decisione attuale
+
+**Opzione B.** Si scrive in italiano. Se il wiki cresce e serve un mirror curato in inglese, si migra a C. La migrazione da B a C è breaking (gli URL cambiano), ma gestibile quando ci sarà abbastanza contenuto da motivarla.
+
+Le stringhe dell'interfaccia possono essere tradotte in italiano in 30 minuti, indipendentemente dal resto.