# Genera - a generated web engine

Generate a web rendering engine from specs and tests.

Early ideation phase.

Ingredients:

- web specifications all in one repo, constantly updated: https://github.com/w3c/browser-specs
- the web features project - all web apis (from bcd), curated into logical features: https://github.com/web-platform-dx/web-features/
- browser compat data - every tiny bit of every piece of the web surface area: https://github.com/mdn/browser-compat-data
- wpt - validation and verification of web implementation: https://web-platform-tests.org/
- wpt-gen - generate wpt test from the specification: https://github.com/GoogleChromeLabs/wpt-gen

Process, use-cases, ideas, examples, random thoughts:
- we'll need to do some testing, and ideating on approaches, the surface area is massive
- should pick some simple html block level elements to begin with, and try different approaches of implementing them in isolation?
- Servo's modularity is worth examining, from a "glue it all together" approach later down the line
- what aspects of Ladybird enabled it to get far relatively quickly?
- Rust seems a good choice from a multiprocess and type safety pov
- architecture that lets us modularly include/exclude web features would mean scaling generated engines up/down as needed for specific use-cases, which is a huge win
- could even imagine analyzing a web app, and then "tree shaking" the *engine* to ship a standalone engine+app