# Fenced setext headings

**URL:** <https://talk.commonmark.org/t/fenced-setext-headings/2678>\
**Category:** Extensions\
**Created:** [December 31, 2017, 11:56am UTC](https://talk.commonmark.org/t/fenced-setext-headings/2678 "2017-12-31T11:56:50Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![chrisalley](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/chrisalley/32/906_2.png) [@chrisalley](https://talk.commonmark.org/u/chrisalley)\
**Post date:** [October 8, 2018, 10:52pm UTC](https://talk.commonmark.org/t/fenced-setext-headings/2678/3 "2018-10-08T22:52:00Z")

</div>

There is a discussion about adding Flowerbox headings to CommonMark in this topic:

> [@Flowerbox Headers on top and bottom of a header](https://talk.commonmark.org/t/flowerbox-headers-on-top-and-bottom-of-a-header/850):
>
> This is a minor annoyance, but I would like ============== Header Title ============== -------------- Header Title -------------- to be recognized as: Header Title Header Title not: ============== Header Title Header Title I use this in certain context, where it stylistically makes sense. For example you would use this in a resume. It makes a long document easy to scan with the eye, since you can recognize the double header as being a major section break.

This seems like a good feature to add to a [Markdown successor language](https://talk.commonmark.org/t/beyond-markdown/2787). I’m not sure how much value there is making this a CommonMark extension given that it will break existing documents and mainly exists for aesthetics.

---

_[View the full topic](https://talk.commonmark.org/t/fenced-setext-headings/2678)._