Collect best-practices we (want to) follow

[carstingaxion]

• semver conform versioning, powered by PR labels, automatically updated in ONE file per repo
• we "keep a changelog", automatically updated
• we have version controlled source code
• automated deployment to production server
• automated update-checks for plugins, themes, core, (translation files), almost everything powered by dependabot
• we took "decisions not options" by heart and removed many, many plugin-settings-pages as well as core UI for several options and site-options without compromising flexibility (that much)
• we use, test for and align with WordPress Coding Standards
• we comply with phpstan level 8 rules on every, and level 9 rules on almost every line of code
• we (try to) stay as close as possible to WordPress core APIs
• we contribute back to the WordPress project and to multiple libraries of different authors within the wider ecosystem
• we rely on and follow the principles of FOSS
• we are open to contributions (in several ways)
• ANTIPATTERN: we use 50+ plugins
• ANTIPATTERN: we life on a shared hosting
• also humans read our server log files
• we do use blocks, wherever we can
• FUNFACT: we use a README.md for our wp.org/plugins
• we avoid plugins that bring in their own custom UI
• we use composer for dependency and version management
• we have and provide you with an imprint
• we know for sure that 161 > 88
• we do not allow weak passwords
• we remind you about public data-leaks containing your password
• we use 2FA by default for everyone
• we have hidden our /wp-login.php page
• we track and block failed login attempts
• we do regular backups of files and databases
• we provide and run on SSL out of the box
• outages will be alerted to admins immediately via email
• the servers are powered by sustainable electricity
• the hosting company is well-known in linux security and around for 30 years
• allow import AND export of all your content
• try to use block variations over custom blocks whenever possible
• we do not query by post_meta, NO, NO, we use taxonomies
• your frontend (but maybe not yet the backend !) will be GDPR compliant
• relevant statistics without the need for Google Analytics
• absolutely free to use, as we don't use any so called PRO or PREMIUM dependencies