Knowledge Base: Potentional Solutions for Future Problems

activate plugins depending on environment: https://github.com/PrimeTimeCode/wp-plugin-activation-manifest
Download Language Files via Composer https://github.com/inpsyde/wp-translation-downloader
generate .env from wp-cli (so could be part of a script): https://github.com/aaemnnosttv/wp-cli-dotenv-command
If WordPlate ever is not flexible/strong enough for us https://github.com/wecodemore/wpstarter/tree/version-3 WP Starter 3 is another setup to manage plugins etc. as composer dependencies. Other than WordPlate WP Starter is itself a flexible composer dependency. It is much less opinionated and more flexible. But sometimes a clear oppinion is easier than freedom and WP Starter 3 is still unstable. InpsyDe are using WP Starter.
Hardcode Settings or tightening our process of fresh install: https://ithemes.com/how-to-hardcode-the-wordpress-setup-process/
The idea: creating a theme that contains a couple of "update_options" and "delete_post" etc. functions and - as its last will - changes the theme to the intended theme. That way, there can be basic clean up activites (deleting placeholder content etc) done - or this could be a way to ship hardcoded options that are forced by activating the theme (and landing back to the intended theme) - shit might also be done by a plugin with versioned options updates.
automatic syncing tailwind colors to block editor colors: https://github.com/roots/palette-webpack-plugin (maybe just duplicating color values once is actually good enough ...)

Speed up translation through caching translations (mo file content) https://github.com/inpsyde/translation-cache

Faster cross linking with #hashtag and @at referencing: https://github.com/rtCamp/mention-links

Make it possible to edit CPT Archive pages like a pot https://github.com/inpsyde/CptArchives

Remove Action / Filter that are hard/not possible to remove normally https://github.com/inpsyde/objects-hooks-remover

Provide feedback