diff options
Diffstat (limited to 'programming/the-content-web-manifesto')
| -rw-r--r-- | programming/the-content-web-manifesto/NOTES.org | 30 | ||||
| -rw-r--r-- | programming/the-content-web-manifesto/README.md | 42 |
2 files changed, 60 insertions, 12 deletions
diff --git a/programming/the-content-web-manifesto/NOTES.org b/programming/the-content-web-manifesto/NOTES.org new file mode 100644 index 00000000..b56c4bf1 --- /dev/null +++ b/programming/the-content-web-manifesto/NOTES.org @@ -0,0 +1,30 @@ +* [[README.md][README]] + +- https://www.fixbrowser.org/ + +** Document how terminal browsers can invoke a full browser to execute JavaScript + +See [[https://www.gnu.org/software/emacs/manual/html_node/eww/Advanced.html]], w3m has similar stuff. + +Also: + +- https://github.com/abhinavsingh/proxy.py Extensible Python proxy +- https://github.com/TempoWorks/txtdot +- https://github.com/4383/photonos +- https://sr.ht/%7Ebptato/chawan/ +- https://offpunk.net/ + +Browsers as a platform to manage content: + +- Just view the content as HTML with user-defined styling +- Archive all that we see so that we can locate content we have read easily, share with others, etc. +- RSS/Gemfeed/content subscription + +** Annotate URLs with another URLs + +- For example, add transcriptions to comic strips that do not have them +- The server pushes serialized bloom filters of annotated URLs (or entire annotation sets?) so that clients do not have to leak what they are browsing. +- Maybe https://dokie.li/ +- Alternative approach with Violentmonkey for accessibility purposes: [[https://github.com/alexpdp7/aelevenymonkey]]. + +** NoScript configuration merge diff --git a/programming/the-content-web-manifesto/README.md b/programming/the-content-web-manifesto/README.md index ec4577f3..fe582917 100644 --- a/programming/the-content-web-manifesto/README.md +++ b/programming/the-content-web-manifesto/README.md @@ -4,31 +4,49 @@ These are my recommendations for creating "content" websites. In a content website visitors mostly read content. Some example content websites are Wikipedia, news websites, and blogs. +Also see [further notes](NOTES.org). + ## General guidelines -### Make content usable without JavaScript +### Test your website with a terminal browser without JavaScript like w3m, lynx, or elinks + +If your website works with one of those browsers, then: + +* Your website does not require JavaScript to load. + This automatically addresses most annoyances with content websites. + Websites that do not require JavaScript tend to require less resources, making them faster and lighter. -By making your content usable without JavaScript, a content website automatically addresses most annoyances with content websites. +* Your website does not rely on non-text content. + Text content is uniquely flexible, it is frequently the most amenable media to being processed by the following systems and processes: -Websites that do not require JavaScript tend to require less resources, making them faster and lighter. + * Text-to-speech systems + * Translation (both human and automatic) + * Edition (making changes to text content) + * Quoting/embedding (readers can copy parts of your text to cite or promote your content) -### Avoid relying on non-text content + Images, audio, video or other interactive media might be required to convey the message of your content. + Therefore, the content web manifesto does not forbid their use. + However, non-text content should always be accompanied by at least a text description of the content, and ideally, an alternate text version of the content. -Text content is uniquely flexible, it is frequently the most amenable media to being processed by the following systems and processes: +* Your website will work with user styling. + Providing a visual style via CSS and others is fine, but users should be able to read your content with *their* choice of font, text size, color, and others. + This is important for accessibility, but also for everyone's comfort. -* Text-to-speech systems -* Translation (both human and automatic) -* Edition (making changes to text content) -* Quoting/embedding (readers can copy parts of your text to cite or promote your content) +And more importantly, this weakens browser monopolies controlling the web. +Not even massive companies like Microsoft dare to maintain a browser engine, leaving the web subject to the power of the very few browser vendors in existence. +But if your web content can be read under a terminal browser without Javascript, then your content is automatically accessible by a massive amount of browsers, including very simple ones. -Images, audio, video or other interactive media might be required to convey the message of your content. -Therefore, the content web manifesto does not forbid their use. -However, non-text content should always be accompanied by at least a text description of the content, and ideally, an alternate text version of the content. +(Alternatively, use [the Gemini protocol](https://geminiprotocol.net/).) ### Provide granular URLs When providing a significant amount of content, make sure readers can link to specific content of interest. +This can be achieved by: + +* Splitting your content in different pages +* Providing HTML headers with anchors + ### Date content Always make initial publication and edition dates available. |