A good taxonomy is invisible when it works and infuriating when it doesn't. The trick is to build on an industry standard for completeness and interoperability, then lay a human-friendly navigation over the top, and to keep your filters separate from your tree.
Search is splitting into three audiences: the ranking algorithm, the answer engine, and the generative model. The good news is that one well-structured article can serve all three, if you write for the passage and the source, not just the page.
If you have decided to build your own website and want it to last for years, you need to understand the financial commitments involved before you begin.
If you publish images with a script instead of the media library, WordPress may generate only two sizes of each. The page still works, so nothing looks broken — but every visitor downloads your full-size file.
Hosting is the one decision under every other decision. Get it wrong and no amount of theme-tuning or caching rescues a slow, flaky site. The good news: the things that matter are few, and most of them you can test before you pay.
You change a few lines in a snippet, press Save, and get "Could not update snippet. Request failed with status code 403". Press Save on the unchanged snippet and it works. Your login is fine. Something between you and WordPress is reading the code itself.
Run the test by itself and it passes, every time. Run the whole suite in parallel and it fails, but only some days, and its failure looks exactly like a real bug. In our case the code was fine. The test was waiting on a clock.
You put a "create an account" link on one site of a WordPress multisite. Visitors who click it land on the main site, which either says "Registration has been disabled" or signs them up there instead.
Every feature arrives with its tests. Nobody times the hook. Then one day git push takes 25 minutes for a one-line change, and the suite is still running one test at a time on a 16-core machine.