https://www.kernel.org/doc/html/v4.10/process/coding-style.html – linux kernel coding style guide.
This is a short document describing the preferred coding style for the linux kernel. Coding style is very personal, and I won’t force my views on anybody, but this is what goes for anything that I have to be able to maintain, and I’d prefer it for most other things too. Please at least consider the points made here.summary
nice docbook format too… is there a theming guide for doctools css? let’s have a look.
http://www.sphinx-doc.org/en/stable/theming.html – sphinx doctools theming guide.
there may be style guides for other org tools i use…
Do use HTML5
Do not use tables for layout. Tables may only be used when the content is actually table data.
Do not put business logic in the templates – Using PHPTAL templating engine will assist with security (automatically escaping strings to prevent XSS attacks), internationalisation and ease of template maintenance. The templates are valid XML documents and can be rendered directly in a web browser without needing to be parsed through the templating engine.first thing. must be important.
https://codex.wordpress.org/WordPress_Coding_Standards – i mean, half the web uses this thing for some reason, instead of yanking out the useful parts and dropping them into something predictable. filters, for example, are lovely.
The WordPress coding standards have been moved to the Core Contributor Handbook:first search result. i guess there’s a handbook now…
you can probably go to that link in archive.org for old versions’ documentation, in your wordpress archaeology projects.
https://archive.org/ – a pretty big public library. nice microfilm collection.
https://manpages.ubuntu.com/manpages/xenial/en/man1/man.1.html – output of “man man”, converted to an html format. i wonder if there’s links to doctools in here?
https://manpages.ubuntu.com/manpages/xenial/en/man1/manconv.1.html – open source file conversion util, btw.
https://assets.ubuntu.com/v1/vanilla-framework-version-1.8.1.min.css – there’s a framework called “vanilla” that provided an output point for something like manconv.
https://gcc.gnu.org/onlinedocs/libstdc++/manual/documentation_hacking.html – official guide for creating documentation
https://www.w3.org/TR/html401/ – world wide web spec for html4.01. goodness, do i have a lot of dusty old projects from my youth.
HTML 4 is an SGML application conforming to International Standard ISO 8879 — Standard Generalized Markup Language [ISO8879].the publishing language of the World Wide Web
https://peopleshader.com/media/js/domchanger.js – by the way, you need to add the namespace bit to get svg node editors working, then you can just basically code your ui’s in s-expressions.
https://codepen.io/xgundam05/pen/KjqJn – a lot of ideas from this went into media/js/page/node.js, which is the domchanger version.
https://codepen.io/xgundam05/pen/bNeYbb – v2 looks really nice.
might need to actually download the full sources and docs to “man” and have a look for pointers in there.
https://www.gnu.org/software/coreutils/ – the core of any old LOAF system. iirc, they used argv to determine what command to execute, and just made a butt-tonne of softlinks to a single executable.
https://superuser.com/questions/130457/what-linux-fits-on-a-floppy-disk – the Small Linux Site is down? :'( that website was rad.
https://superuser.com/tags – might be a useful index. a lot of people have usually been where you’re at, on the internet, and asked right there out in the open.
https://cs.wmich.edu/~gupta/teaching/cs4850/sumII06/The%20syntax%20of%20C%20in%20Backus-Naur%20form.htm – i may have mentioned before, but this BNF grammar for C is fantastic for making code generators in scheme