Improving documentation for Plutus Developers

Currently, effective usage of Plutus in production pretty much requires reading of the Plutus specification and the extended EUTXO model. However these documents are not necessarily optimized for quick-reference in the ways a programmer may need, they're really intended for implementors and early integrations.

Additionally, a developer using Plutus will typically also make use of Haddock Generated documentation available for the Plutus Library or other related tool in Haskell.

This leaves a number of deficiencies in documentation:
- documentation should be searchable and discoverable through means that are convenient for developers (example: [MDN](https://developer.mozilla.org/en-US/)
- users of alternative languages will often need to cross-check for specific parts of the plutus API (such as scriptcontext) - perhaps something akin to internationalization can be supplied in documentation to have equivalent code examples in multiple languages