Thanks Jason, however you’ve made an assumption that I have a theme selected, which I didn’t. I had simply enabled the
hello plugin. I’m suggesting Manton creates a true idiot’s guide, with step-by-step instructions for someone that has just signed up, with screenshots.
Edit Custom Themes and created a new theme with the title
aaa with no GitHub template and selected it as my custom theme.
Then I edited the
aaa theme but don’t see where to
add to Custom Templates a file named config.json. Edit - I’ve subsequently clicked on
New Template (which I didn’t realize would create a custom template) and created the
config.json with the contents you suggested, but this didn’t change the markdown preview.
I’ve gone back to using GitHub Pages for now. I really don’t want to invest time in grokking Hugo, since I’ve already spent too much time getting my head around Jekyll - the whole point for me was to move to system that just worked.
I appreciate that code fences are just one aspect of GFM, but I don’t want to have to go through more config changes when I want to use another aspect of GFM.
Many thanks for working with me on this - I didn’t expect to have to dive into custom json config files just to enable formatted code.
@manton perhaps create a support page for someone that has literally just signed up, explaining step by step how to enable code fences, and ideally full support for GFM:
- Update Hugo to the latest in the design page
- Create a custom theme by tapping
Edit Custom Themes, name the theme “My Theme”
- Select the theme on the Design page
- Create a JSON file per Jason’s spec, and place it … somewhere …