For those building bots, we propose signing the authority of the target URI, i.e. www.example.com, and a way to retrieve the bot public key in the form of signature-agent, if present, i.e. crawler.search.google.com for Google Search, operator.openai.com for OpenAI Operator, workers.dev for Cloudflare Workers.
They're proposing the request will include public key source information and request target. Through the public key source, you can verify the origin via source domain name.
Makes me wonder if the main content source would not be better separately, from which you generate the other stuff - e.g. Hugo Markdown page source.
I'm still not sure I grasp the fundamental structure of your data and desired workflows.
Hugo being simple Markdown files for content, if they can not be used as the source of truth, maybe that can be elsewhere, maybe even in Markdown, and you copy to Hugo? Then you'd be less restricted in your form of data and doing other things with separate tooling like sync to other services.
If you already invested into Hugo theming I'd also be hesitant about switching to a CMS/hosted solution. Especially since I suspect there's no ready solutions for your integrations? I assume you'd have to do the integrations yourself. If that's the case, my intuition says to better be independent of a CMS (with unknown efforts or how long it will remain useful). Once you're in a CMS env as a primary source it owns the data and exporting won't be as easy as if you have the primary source separately in a simpler, independent manner.
You say you have contacts, newsletter, events. You said you have Hugo (yaml), Thunderbird, Google Contacts, CSV.
Is it a matter of synchronizing contacts between them? Or more? Sending the newsletters?
Git / TortoiseGit
Have you considered Hugo Data sources (data subfolder)?
Synchronising a data format in there, synchronising the data through APIs and some tooling, and then generate the Hugo website from that data may simplify the process - make it viable despite still having some variance and complexity.
in 4 different ways: Hugo yaml, Thunderbird, google contacts, CSV (from earlier days)
Are you still using CSV? If it's integratable into one of the other three that could reduce complexity by dropping this fourth case?
What do you want your defining state to be? Or should it synchronise across, and changes must be possible in any of the places?
Thunderbird can use Google contacts and calendar. Some tooling could sync to or from or both your Hugo data folder.
That 10 years ago.
Looks like they weren't able to borrow a 'was' for the sentence.
AI-assisted coding […] means more ambitious, higher-quality products
I'm skeptical. From my own (limited) experience, my use-cases and projects, and the risks of using code that may include hallucinations.
there are roughly 29 million software developers worldwide serving over 5.4 billion internet users. That's one developer for every 186 users,
That's an interesting way to look at it, and that would be a far better relation than I would have expected. Not every software developer serves internet users though.
Unfortunately, that poisons not only the AI.
It's possible their communication happened before that, and it just took a while to write and post OP post. 16 days is not that long or delayed. I haven't checked the dates of the commits in question though.
My preference is Visual Studio. For some technologies, and mass-text-replace, I use Visual Studio Code.
A long time ago my main IDE was Eclipse for C++ and Java before that. Recently, I've tried RustRover for Rust as an alternative to VS Code.
https://github.blog/changelog/2025-05-01-github-now-provides-a-warning-about-hidden-unicode-text/ since may 1st (OP is from may 16th)
I guess the 11 MB micro was too big.
It does look like it has a lot of functionality for 250 kB.
Clickable menus instead of separate help functionality or lines are a good way to make them obvious and discoverable, teaching about them.
I'd guess trying anything is fine if you keep a prototype and experimental mindset. You could try a CMS that looks interesting or viable. Maybe that helps getting a better idea of viability with specific products or approaches?
Personally, I'd try/experiment with what I laid out in my last comment - have data files (maybe json or markdown files) and generate and push and pull data from and to that. But that may be because of existing experience and expertise. Not necessarily the best approach for others.
Using a CMS means more integration, which has upsides and downsides.