undefined | Better HN

0 pointsnprateem1y ago0 comments

One of the saas hosting companies made one for Hugo iirc, but it looks like crap and is pretty basic.

It's a pretty easily solvable problem but I guess developers are focussing on bigger markets.

I'd want to keep the build step since I may pull markdown from other sources like I think astra allows.

I really just want to be able to give access to a marketing team to update the blog etc as a nice UI over using markdown and git (which is never going to happen).

0 comments

arch1e1y ago

> I'd want to keep the build step since I may pull markdown from other sources like I think astra allows.

Pushing without building is not a difficult thing to do, in-fact it will make changes much faster too. But you mention pulling markdown files from other places, merge conflicts are bound to happen that way right? And AFAICS there would not be an easy way to manage that automagically without human intervention.

nprateemOP1y ago

No I think it'd be enough to have them separate to avoid merge conflicts.

It could probably be done in a separate step or something so users can edit files once they've been pulled in from other sources, at which point the repo becomes the source of truth.

j / k navigate · click thread line to collapse