Feature request: ACE and Amber content files

[trombonehero]

It's great that Hugo can now support external content renderers (asciidoc, rst, etc.), but all of the currently-supported formats (except raw HTML) are quite Markdown-like. That is, they're great for writing a blog post, but not great for authoring more complex documents like dzslides/reveal.js with lots of control needed over HTML element classes, etc. For instance, dzslides will make any element with class="incremental" show its children one at a time as the slide builds, but none of Markdown/Asciidoc/reStructuredText allow this level of control. And HTML is... well, if I wanted to write raw HTML then I wouldn't use Hugo. :)

Hugo does support the use of the more detail-oriented ACE and Amber formats, but only for templates. It would be great if I could write an ACE-formatted file to get more HTML precision than markdown-like formats allow but still benefit from Hugo shortcodes, e.g.:

section
  h1 Functional programming
  ul.incremental
    li Higher-order functions:

    .centered
      {{% figure src="..." %}}

    {{< highlight rust >}}
    let f = |x| 2 * x;
    {{< /highlight >}}

[trombonehero]

In fact, what I really want to get from ACE-based content files is the ability to use a baseof.ace file as my "generic DZslides boilerplate" and then write individual presentations/lectures like so:

= content main
  section
    /* ... */

  section
    /* ... */

[bep]

I don't see this happening soon. I see your point, though.

As to slides, have you seen this? http://discuss.gohugo.io/t/howto-embed-remarkjs-com-slides-in-hugo/1403

[bep]

This issue has been automatically marked as stale because it has not been commented on for at least six months.

The resources of the Hugo team are limited, and so we are asking for your help.

If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.

If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.

This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.