Unfortunately, due to lack of <one page to rule them all>, the https://github.com/CovertLab/WholeCellEcoliRelease/blob/7e4cc9e57de76752df0f4e32eca95fb653ea64e4/docs/README.md#relevant-papers[on-Git tree publication list is meager], some of the most relevant ones seems to be:
* 2021 <open access> <review paper>: https://journals.asm.org/doi/full/10.1128/ecosalplus.ESP-0001-2020 "The E. coli Whole-Cell Modeling Project". They should just past that stuff in a <README> :-) The article mentions that it is a follow up to the previous <M. genitalium whole cell model by Covert lab>. Only 43% of known genes modelled at this point however, a shame.
* 2020 under <Science (journal)> <paywall>: https://www.science.org/doi/10.1126/science.aav3751 "Simultaneous cross-evaluation of heterogeneous E. coli datasets via mechanistic simulation"


Publications

E. Coli Whole Cell Model by Covert Lab <span class="meta">/</span> Publications

{c}
{wiki}

Please, use <AsciiDoc> and <one page to rule them all>.


README

That which does not exist, cannot be broken.

And of course:
* <one page to rule them all>
* https://motherfuckingwebsite.com


The CSS of Ciro Santilli's website looks broken

https://zettelkasten.de/posts/overview/ mentions <one page to rule them all>:
> How many Zettelkästen should I have? The answer is, most likely, only one for the duration of your life. But there are exceptions to this rule.


Zettelkasten

{tag=Monolithic system}

It is true that one image is worth a thousand words, but unfortunately it is also true that one image takes up at least as much bytes as a thousand words!

Having one single page to rule them all is of course the <ideal> setup for a website, as you can Ctrl + F one ToC and quickly find what you want.

And, with <Linux Kernel Module Cheat> Ciro noticed that it is very hard to write so much intelligent prose that becomes larger than reasonable to load on a single webpage.

He then started using this technique for everything he writes, including this page and <Ciro Santilli's campaign for freedom of speech in China>[Chinese government].

However, if there are too many images on the page, the loading of the last images would take forever in case users want to view the last sections.

There are two solutions to that:
* be traditional and create separate web pages
* be bold and load images as they appear on the viewport: https://stackoverflow.com/questions/2321907/how-do-you-make-images-load-only-when-they-are-in-the-viewport/57389607#57389607

  Edit: OK, it was standardized with `loading=lazy`, without need <JavaScript>!

  Now the last awesome thing would be a method that loads first images in viewport, then those below, and then those above, that would be the ultimate solution.

  This question comes close: https://stackoverflow.com/questions/7906348/change-loading-order-of-images-already-on-page

Ciro is still deciding between those two. The traditional approach works for sure but loses the one page to rule them all benefits.

The innovative approach will work for interactive viewing, but archive.org will fail to load the images for example, and there may be other unforseen consequences.

Wikimedia Commons is awesome and automatically converts and serves smaller versions of images, so always choose the smallest images size needed by the output document. Readers can then find the higher resolution versions by following the page source.

This also comes to mind: https://motherfuckingwebsite.com

https://zettelkasten.de/posts/overview/ from <zettelkasten>:
> How many Zettelkästen should I have? The answer is, most likely, only one for the duration of your life. But there are exceptions to this rule.


Ciro Santilli @cirosantilli 37

 Incoming links: One page to rule them all