this post was submitted on 22 May 2025
30 points (94.1% liked)
Programming
20435 readers
191 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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?
I think essentially I would like to achieve something like this
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.