After taking a quick look at the "Prompt API" document, I decided to write some design notes towards a fork of the #Web.
-
@DLC @dillo i don't think stylesheets are fundamentally flawed, but i do think for certain things the website should be able to specify for example the layout, and a few cases benefit also from things like text colours (code highlighting in blog posts)
it should be minimalised, but style shouldn't be banned
@SRAZKVT I don't think so either, but they belong in the client? Not per website…
Let the website declare the layout it prefers:
<section layout="weblog, article">
Use semantic tags:
<note layout="footnote">text</note>
<note layout="panel">text</note>
<bq style="code:APL">code</bq><em font="color: red" >…</em>
<table id="tab1" src="rel/url/table.cvs">
Desc
</table>See <table id="tab1" />
<figure id="fig1" src="rel/url/img.jpg">
Desc
</figure>See <figure id="fig1" />
-
After taking a quick look at the "Prompt API" document, I decided to write some design notes towards a fork of the #Web.
On forking the Web
@dillo I remember reading the HTML 4.01 spec forwards and backwards, marveling at how well written it was. I'd start from it again and only backport the good parts from HTML 5: structural elements like header / nav / footer, newer HTML entities like ☆ and stuff like that. Might have to drop a few things in the process.
Heck, let's go back to HTML 3.2 and start again from there, like text browsers did.
-
After taking a quick look at the "Prompt API" document, I decided to write some design notes towards a fork of the #Web.
On forking the Web
From the orange site, "Strict grammar for declaring documents is merely a fetish".
Isn't that the best name for a document format to be load in the #Dillo browser?
-
@DLC @dillo i don't think stylesheets are fundamentally flawed, but i do think for certain things the website should be able to specify for example the layout, and a few cases benefit also from things like text colours (code highlighting in blog posts)
it should be minimalised, but style shouldn't be banned
@SRAZKVT @DLC the problem with CSS is not so much in design of CSS itself but in the complexity of HTML which make each page have its own set of unique CSS rules.
I agree with authors being able to suggest a set of styles, but those should be optional on the client. That way you can reliably set your own scheme for all the pages **and still be sure that it will reliably work**.
This is also important for readability, not only for the aesthetics of the page.
-
@SRAZKVT @DLC the problem with CSS is not so much in design of CSS itself but in the complexity of HTML which make each page have its own set of unique CSS rules.
I agree with authors being able to suggest a set of styles, but those should be optional on the client. That way you can reliably set your own scheme for all the pages **and still be sure that it will reliably work**.
This is also important for readability, not only for the aesthetics of the page.
@SRAZKVT in any case, for this initial approach I'm only considering structure not presentation.
Ideally it should be possible to output three formats: screen, print and non-visual output.
It is probably a good idea to start from the non-visual output and work backwards from there, so accessibility is guaranteed by design.
-
R relay@relay.infosec.exchange shared this topic
