After someone suggested posting about my project on the Hugo Forum, I though it would be a good idea. I hope it can be helpful to a lot of people. You can read more about the project (including Screenshots) on the GitHub page: https://github.com/iakmds/buhocms
Here is a shortened description of what BuhoCMS is:
BuhoCMS is a free and open source local CMS for Hugo on your Desktop. See it as a GUI for static site generators.
BuhoCMS would be for you if you land in at least one of the following categories:
You already have a Hugo site and want to easily edit your content from now on
You want to create a new Hugo site from zero with a graphical user interface
You are a beginner looking for a simple way to begin your journey in using static site generators
A (non-exhaustive) list of the features:
Add new posts and edit your Markdown content and Front matter with ease
Edit content: Use the Markdown toolbar for quickly adding styles
Markdown preview: Use the Markdown viewer to check your syntax
Front matter: Graphical User Interface (GUI) for each field like a Text field, Switch, Date picker, Tag editor, and more
Switch between GUI and raw text mode
Start, open and stop your local Hugo server with a click
…and much more!
Currently, Windows and Linux are supported. I would love to get your feedback. Thank you!
Hello. Thanks for a great tool. I’m sure many people would find it useful.
Does it parse front-matter from existing sites/projects?
Are Hugo command line switches supported (and how so) in start/stop/build etc?
Is there a non GUI way to easily edit front matter on a GUI editor? Meaning, the GUI editor should have an option for both quick/easy manual front matter editing, as well as GUI if that’s what people want. Switching the entire display to text only just to edit a few quick things may get tedious.
Does the markdown preview use Hugo serve or a client-side only preview? I am curious whether the preview supports short-code rendering.
Thanks, and I’ll try it sometime and provide actual feedback.
If I understand that correctly, yes – that is, after adding your entries to the global Front matter list of BuhoCMS. Once they are added, all posts with the corresponding schemes will appear in the GUI. By default, there are 4 Front matter list entries:
Are you referring to the command flags, like here https://gohugo.io/commands/hugo? If so, not yet – but it’s a great idea I will note down. Let me know if I misunderstood you.
I think I get what you mean, are you talking about a switch in the Front matter section while using GUI mode that will display the Front matter text, instead of switching to Text mode altogether? If yes, I will note down that feature!
It uses a client-side markdown preview, so unfortunately it doesn’t support short-code rendering. If it would use Hugo server, are you thinking about a Web view of the localhost, i.e. displaying the whole Website as a preview?
I hope I could help, let me know if you have any further questions
You have understood correctly. Though it seems we need to manually add our front matter directives to the CMS first before it can use it? Can you parse front matter and auto create whatever that needs be created in the CMS? So this step isn’t manual, where we need to add front matter to the CMS manually before it can process it.
Correct. Would like to see a checkbox option to enable/disable most useful command line hugo arguments. Or a box to enter our own args.
You understood correctly. The GUI should have the option to stay in full GUI, while displaying the front matter or the article source in TEXT. Should be a radio box that we can select that displays GUI markdown editor, or a simple textarea etc.
An embedded webview would handle shortcode generation. It’s pretty easy to open a webview control or an iFrame (not sure what stack you’re building in) and give the source as localhost:1313
Let me know if I can help out with coding or anything else. Thanks.
another new release (0.3.0) is out on GitHub , which includes the 1. feature request by @Hash_Borgir, that is, is an Auto-Detect Front matter feature (+ other improvements, fixes etc.).
Would love to know what you think.
Seems counter intuitive, but if you put everything Boho in its own directory in the build directory root, ‘.boho/’, and use the paths in the UI as paths to render Boho files, there will be more flexibility.
A ‘Save’ button (if no auto-save) will save text files in ‘.boho/’, with whatever extension the user chooses.
A render button will render the current file (in the editor input) to markdown, or scss, or whatever, in the directory at end of path specified in the UI.
Files in ‘.boho/’ can contain multiple blocks wrapped in a start delimiter, with the path specified, and an end delimiter (with folding).