Best Practices for Writing on DEV: Formatting
Tags: meta, writing, howtodevto
Published: 2023-04-17 19:34:33

Hey again, Sloan here! 🦥 

We’re sharing some tips for success when it comes to writing on DEV. If you’ve been looking to improve your technical writing skills, make the most of DEV as a blogging platform, and take your content to the next level — this series is for you!

The first post in the series was about **creating a series**. This one is about **formatting**, and the next two are about **tone of voice** and **topics**. Let's get started!

## Formatting

Proper formatting is key to ensure that your post is readable, helpful, and polished. Our post editor uses [Markdown](https://github.com/adam-p/markdown-here/wiki/Markdown-Here-Cheatsheet) and [Jekyll Front Matter](https://jekyllrb.com/docs/front-matter/) to format posts.

### Use of headings

Use headings to keep your post’s content organized, and they’re great for supporting your article’s searchability. If you’re writing your post in pure markdown, use hashes to denote headings. Your title is the top headings (H1) automatically, so your highest-level headings should be H2. You can go as small as H6, but I don’t recommend it — if you need to break down your topics into six levels of subsections, you might have more than one post on your hands 😉

If you’re using our rich + markdown editor on DEV, you can add a headings by selecting the H button in the toolbar:

![The editor toolbar, which consists of 11 icons. The sixth icon, represented by a capital letter H, is circled in red.](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/gjubbmj4e4jpd5jpnkez.png)

Each time you select the button, it will add another hash up to H4, at which time it clears.

### More a11y considerations

Headings are important not only to visually organize your content for the sake of your readers, but also to aid Assistive Technologies (AT) such as screen readers in organizing your content appropriately. Here are a few more accessibility (a11y) tips for formatting your DEV posts:

- Add image descriptions to your images.
- Keep emoji limited to the end of a line of text.
- Avoid using fancy characters for font purposes.

{% embed https://twitter.com/kentcdodds/status/1083073242330361856 %}

For more details on why these are best practices for a11y, please check out [Accessible Social](https://www.accessible-social.com/copy-and-formatting/).

### Markdown basics

No matter which post editor you use, it helps to study Markdown basics and double-check your formatting before you press “publish.” Just one backtick [`] can throw off all the code samples in your entire post!

There is a helpful Markdown guide available right in the post editor, and you can learn more about formatting in the DEV editor from the [Editor Guide](https://dev.to/p/editor_guide).

One very cool formatting feature on DEV is the use of **liquid tags.** You can read up on our supported liquid tags from our [Liquid Tags Guide](https://dev.to/p/editor_guide#liquidtags). For some examples, check out the liquid-tagged article below:

{% embed https://dev.to/devteam/ways-to-enhance-your-dev-posts-useful-embeds-1g0f %}

---

That's it! Happy formatting. The next installment of this series will be about **tone of voice**.