Go with a standard time-series journal. This is about the simplest way to do things. It works well enough for me with minor additions.
Eventually you've referred back to your journals enough to know what kinds of information you'll be looking for. I've gotten part way there, so far. I'm still trying to sort out details for a lot of stuff; where does the plan of a project live? In the journal? In the projects files? What about the day-to-day entries? What about troubleshooting epilogs? Like I said... I'm still trying to sort out where each of these live.
I'm tempted to just throw all the things in project folders (because they're all projects anyway) and then grep for stuff if I need to find it.
Then, just throw your notebooks into MkDocs (using a plugin) and voila, you get a statically hostable version of your notebooks!
Easily coupled with Git and CI/CD practices, you have a nice, easy to use setup for prodyctive work and knowledge sharing if needed!