# Content Block/Inline Syntax

**URL:** <https://talk.commonmark.org/t/content-block-inline-syntax/815>\
**Category:** Extensions\
**Created:** [October 15, 2014, 2:23pm UTC](https://talk.commonmark.org/t/content-block-inline-syntax/815 "2014-10-15T14:23:14Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![mofosyne](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/mofosyne/32/1438_2.png) [@mofosyne](https://talk.commonmark.org/u/mofosyne)\
**Post date:** [November 6, 2014, 10:51am UTC](https://talk.commonmark.org/t/content-block-inline-syntax/815/8 "2014-11-06T10:51:16Z")

</div>

Originally from: [What could a "spoiler tag" extension look like? - #61 by vitaly](http://talk.commonmark.org/t/what-could-a-spoiler-tag-extension-look-like/767/61)

> This is a strong indicator that the div element should not have it’s own Markdown syntax, even as an extension. We should aim to add more semantic elements on a case by case basis instead.

If I wanted to create a box that applies for “warnings” or “notices”, via say… “.warning” or “.noticebox” classname. Then how would I do it? I usually do it via a div container, but that’s not very markdownish.

e.g.

```
:::: Success Notification :::::
 ... lorem ipsum etc...
:::::::::::::::::::::::::::::::

:::: Error Notification :::::
 ... lorem ipsum etc...
:::::::::::::::::::::::::::::::

:::: Info Notification :::::
 ... lorem ipsum etc...
:::::::::::::::::::::::::::::::

:::: Warning Notification :::::
 ... lorem ipsum etc...
:::::::::::::::::::::::::::::::

:::: Print Notification :::::
 ... lorem ipsum etc...
:::::::::::::::::::::::::::::::

:::: Purchase Notification :::::
 ... lorem ipsum etc...
:::::::::::::::::::::::::::::::

```

![](https://cdn.commonmark.org/uploads/default/507/87033c5ef125c3f6.jpg)

```
<div class="success-notification" ><p>lorem ipsum</p></div>
etc...

```

---

_[View the full topic](https://talk.commonmark.org/t/content-block-inline-syntax/815)._