💾 Archived View for rawtext.club › ~sloum › geminilist › 005447.gmi captured on 2023-11-14 at 10:05:37. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
easrng easrng at gmail.com
Mon Feb 22 13:38:05 GMT 2021
- - - - - - - - - - - - - - - - - - -
On Mon, Feb 22, 2021 at 5:01 AM Louis Brauer <louis at brauer.family> wrote:
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.
I agree this is probably a better plan.
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.I was thinking of having a single color that the client could usehowever it wants, ex. to theme the title bar or color links orwhatever.
Lagrange is a great example how rendering of Gemtext can be very beautiful without CSS-like styling whatsoever.
Lagrange could take the hue from the theme color and use it, or ignoreit or whatever.I suppose this could be a slippery slope though.