# Feature request: automatically generated ids for headers

**URL:** <https://talk.commonmark.org/t/feature-request-automatically-generated-ids-for-headers/115>\
**Category:** Uncategorized\
**Created:** [September 3, 2014, 9:49pm UTC](https://talk.commonmark.org/t/feature-request-automatically-generated-ids-for-headers/115 "2014-09-03T21:49:39Z")\
**Posts on this page:** 1\
**Showing post:** 87

<div class="post-metadata">

**Author:** ![vas](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/vas/32/1267_2.png) [@vas](https://talk.commonmark.org/u/vas)\
**Post date:** [October 25, 2017, 10:50pm UTC](https://talk.commonmark.org/t/feature-request-automatically-generated-ids-for-headers/115/87 "2017-10-25T22:50:10Z")

</div>

I’m kinda in favor of the simplest solution, the one [that GitHub has adopted](https://help.github.com/articles/basic-writing-and-formatting-syntax/#section-links), even at the risk of collisions (though GitHub avoids collisions by appending a suffix when a collision is detected).

The thing to remember is that links should be **easy to author** , just as with the rest of markdown/commonmark.

I haven’t thought through the implications enough, hence the “kinda”.

---

_[View the full topic](https://talk.commonmark.org/t/feature-request-automatically-generated-ids-for-headers/115)._