Hacker News Reader

Comment by cyber_kinetist | Hacker News Reader

If there was a decent WYSIWYG editor (like Typora) bundled with Pandoc with a myriad of customizable export options, included with a bunch of high-quality themes and templates, while also having a one-click service to upload to a server for static serving, then I don’t see why not. Maybe the technology stack is not the problem, it’s the presentation of it that makes non-tech people gawk at the complexity.

Though the biggest problem with this stack is that everything breaks down when you’re doing anything serious with images or layouting.

View on HN

That's what I experienced building a static site generator for my dad. You would just dump markdown into a dropbox folder. A cron job would poll from dropbox and generate the website. But even markdown is too daunting for a non-techie. Non-technical users are probably not used to write "code"/"mark-up" and have a good grasp at what's coming out on the other side. The visual aspect, a sort of preview, is missing. There are a lot of options to preview markdown. That's just another hurdle, another tool they might have to learn. It's all just so loosely integrated, even I have a hard time putting it together. Might be fun for us to fiddle around, but it isn't if you just want to put your content out there. I've started to work on an alternative: Desktop app, with a block based editor (text, images, headings nothing more). Shows a local preview of your site. Outputs static assets and/or uploads directly to Vercel for hosting. Few knobs to fiddle around.

Why not a WYSIWYG HTML editor?

At the end of the day Markdown is just an intermediary shorthand for the eventual output, originally HTML; and HTML is actually standardized. If you’re not going to use the Markdown syntax, then wouldn’t an HTML editor that hides all the HTML do the job?

Actually, you’re right. The only thing people actually need is a good WYSIWYG editor; the format is probably uninteresting to the end user. Though there is a case to be made for using an open, well-documented format (whether it be Markdown or HTML or something else), since without this openness third-party developers would have trouble in developing and customizing their own exporters.

Well, if you’re suggesting HTML (or XML) for that job, then maybe it’s time to resurrect XLST instead of using Pandoc… (https://en.m.wikipedia.org/wiki/XSLT)

There would still be a lot of moving parts on the table. What to do with all these HTML files? How do I link them together? How do I get those files to a hosting provider? Where do I handle global styling? For the content creating itself a WYSIWYG editor would be fine, but there's more to the process. I'm also guilty of the builder mentality. It's just a fun project to work on and it benefits at least on other person :)

I think the larger part of the problem is exactly what the author seems to miss: even using Jeykll is scary for non-technical users, let alone git. (Try getting your grandfather to restore his accidently deleted posts)

How would content created with WYSIWYG editor work (and look decent) on any device other than it was created for, eg a phone?

Reply on news.ycombinator.com