💾 Archived View for rawtext.club › ~sloum › geminilist › 005426.gmi captured on 2023-11-14 at 10:06:29. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Louis Brauer louis at brauer.family
Mon Feb 22 10:00:58 GMT 2021
- - - - - - - - - - - - - - - - - - -
Am Mo, 22. Feb 2021, um 01:46, schrieb Oliver Simmons:
I think something like this would be nicer:
```
# Boop, a website :)
Free hugs for all!
^^^
favicon: 🤗
author: Bob McBobface
last-edited: 22nd Feb 2021
```
That is:
```
<PAGE>
^^^
<METADATA>
```
For the metadata format I think a simple key:value list would work
fine, nothing overcomplicated.
To someone without support for it it should just look like a human
list of metadata.
Giving my two cents, I agree with Oliver here. I don't think page metadata deserves it's own mime/type and shouldn't be JSON encoded in a data link. Goes against the human-friendly philosophy of Gemtext.
Oliver's proposal seems to be quite right because it makes everything optional, very easy to parse and can also be displayed without any special rendering support by the client. This way it's purely conventional and would still work for clients with and without support.
Regarding color schemes etc. Is it part of the plan that Gemtext pages will control the browser color scheme? Gemtext is a text-based markup, there should be no style information. The user should control the theme of their client/browser, not the page that is currently displayed.
Lagrange is a great example how rendering of Gemtext can be very beautiful without CSS-like styling whatsoever.
Louis