penthouse VS docco

It is a wrapper around Penthouse, the original critical path CSS generator, and performs two additional functions:

It is easy with a little automation :). In the build process, adding a step to calculate critical path css helps. This should probably be the last step and run on production post deploy. The calculated CSS is stored in redis which will be appended in the head for subsequent requests. This tool had inspired me to build this process at multiple orgs I have worked with https://github.com/pocketjoso/penthouse.

Agree on the async JS part but I guess browser makers will solve it soon.

inline critical css (here is a useful tool https://jonassebastianohlsson.com/criticalpathcssgenerator/) , and here an explanation (https://web.dev/extract-critical-css/).

pocketjoso/penthouse - Generate critical css for your urls

Critical CSS uses as its engine penthouse which has in turn a lot of configuration options. One of them, is forceInclude.

i have seen those in annotated javascript documentation. but it was the other way around. (comment on the left, and code on the right).

they all seem to use docco[0] with the option to display comment in "parallel". the author of docco used it in their library underscore[1].

[0]: https://github.com/jashkenas/docco

Side note - it's been a while since i've seen a Docco-style annotated-source-style documentation! http://ashkenas.com/docco/

Backbone.js was the first time i saw it, and I loved it! https://backbonejs.org/docs/backbone.html It demonstrated to me that the libraries I use are just normal code that other people write, and i myself can read it to understand a problem.

jashkenas/docco - Literate Programming can be Quick and Dirty.