I started my client's site on Hugo, withing 2 days I was editing something for them every 30 mins (slight exaggeration). They wanted something they could edit, they don't do Markdown, they don't manually write URLs they want to drag images into their posts and pages.

So bye bye Hugo.

▲

krisgenre a day ago | parent | next [-]

Eleventy + Decap CMS + gitlab has been working well for our marketing team for the past 3+ years. Also, with Claude/Gemini/Copilot it is a lot easier to edit templates and add new pages when all of the files are right there on your filesystem.

▲

jaza 2 days ago | parent | prev | next [-]

Check out TinaCMS. Works for editing Hugo sites. Not as nice as WordPress admin, but it's good enough for simple editing tasks.

▲

ozim 2 days ago | parent | prev | next [-]

Normal people refuse to learn markdown - they want RTF editor.

I could understand someone might refuse learning LaTex but markdown is so simple.

RTF editing sucks badly if you have to include it in your project. No one wants to specifically pay for implementing it but they also expect it to be there.

▲

trinix912 2 days ago | parent | next [-]

Nowadays you can just use one of those WYSIWYG markdown editors that come with a toolbar (incl. buttons for inserting images) and hide the formatting syntax by default.

	▲	ozim 2 days ago \| parent [-]
		That's the easy part, yes. But each editor also has its issues with generating "backend html" doing bunch of wonky stuff so it works for this editor — using that text in various other places and when you have multiple rich text fields and not single big one to edit whole document is always a major PITA. Then you get whatever they write to PDF report so for example you have to render HTML correctly there. Amount of ways it can break is basically infinite, getting paragraphs page breaks is non trivial amount of work, especially when customer wants their own layout for the report and not generic looking or just broken layout. So problem is mix and match display of whatever they write in different places. Not to mention, everyone wants prefilled templates, so they don't start from scratch, oh and your templates need to have dynamically filled in placeholders, now you have to put something like tags that will be updated by your back end. Maybe you need to send it via API and all kind of companies have WAF on incoming/outgoing data then you have to strip tags. Yes you can encode/decode, limit options, white list allowed tags, and I was doing that for years now, but amount of things that break is still big and another customer wants you to enable lists when you wanted to support just italic, bold, then you have whole blast radius and feature creep is real. ROI is just not there, as I mentioned no one wants to specifically pay for all that, we have a really good run telling customers to just use plain text, amount of regressions to be tested, amount of expectations of things to work out of the box once you go with rich text is really high. Bar to jump to is basically re-implement MS Word — oh did I mention everyone will expect copy pasting from Word to work perfectly - just imagine how much time your customer support has to spend explaining you limited options in that field to be just bold and italic.

▲

notpushkin 2 days ago | parent | prev [-]

> RTF editor

Is that what they call WYSIWYG? :eyes:

▲

ozim 2 days ago | parent [-]

RTF editor may be part of WYSIWYG solution but it also might be used to edit text that on publication will be looking entirely differently or will be used in various places.

	▲	notpushkin 4 hours ago \| parent [-]
		Ohh, I think I get it now – is this about literally using RTF as an intermediate format? I really don’t think I’ve heard about it being used in the context of static sites, but I see how it might make sense as a way of storing, well, rich text. Pandoc is your best friend in such cases: https://pandoc.org/

▲

ymolodtsov 2 days ago | parent | prev [-]

This is generally solvable unless they wanted radical layout changes. There are headless CMS solutions, just ensure that no texts are hardcoded and instead put in a config. Such configs can be made editable in the CMS.