Skip to content

Rich Text Formatting

Rich text formatting adds visual emphasis and structure to your content. All formatting works across paragraphs, headings, callouts, lists, and other text-based blocks.

Basic Formatting

Bold Text

Use double asterisks for strong emphasis.

**This text is bold**
This is **partially bold** text

Result: This text is bold

Italic Text

Use single asterisks or underscores for emphasis.

_This text is italic_
_This text is also italic_
Mixed with **bold and _italic_**

Result: This text is italic

Underline

Use double underscores for underlined text.

**This text is underlined**
**Important:** regular text follows

Result: This text is underlined

Strikethrough

Use double tildes for ~~deleted or crossed-out~~ content.

~~This text is crossed out~~
Original price: ~~$99~~ Now: **$49**

Result: ~~This text is crossed out~~

Inline Code

Use backticks for code snippets and technical terms.

Use the `install` command to set up the package
The variable `user_name` stores the login information

Result: Use the install command to set up the package

Combining Formats

Multiple Formats

Combine different formatting types for complex styling:

**Bold _and italic_** text
**Underlined and **bold**** content
~~Struck through with _italic_~~ text

Nested Formatting

Layer formatting for sophisticated emphasis:

_This is italic with **bold inside** and continues_
**Bold text with `code snippet` embedded**
**Underlined with **bold** and _italic_ sections**

Create clickable links with bracket notation:

[Notion Homepage](https://notion.so)
Check out the [documentation](https://developers.notion.com) for details

Apply formatting to link text:

[**Important Link**](https://example.com)
[_Documentation_](https://docs.example.com)
Visit our [~~old~~ **new**](https://new.example.com) website

Integrate links naturally within formatted text:

**Important:** Please review the [quarterly report](https://reports.company.com) before the meeting

Practical Examples

Documentation

**Getting Started:** Install the package using `npm install notionary` and follow the [setup guide](https://docs.notionary.com/setup).

Task Lists

- **High Priority:** Complete the ~~draft~~ _final_ version by **Friday**
- Review the `config.json` file and update [deployment settings](https://deploy.company.com)

Callouts with Rich Text

[callout](**Warning:** The `production` environment requires **careful testing** before deployment)

Table Content

| Task                | Status        | Notes                                     |
| ------------------- | ------------- | ----------------------------------------- |
| **API Integration** | _In Progress_ | See [documentation](https://api.docs.com) |
| ~~Legacy Support~~  | **Complete**  | `deprecated` functions removed            |

Best Practices

Semantic Formatting

  • Bold for important concepts and strong emphasis
  • Italic for subtle emphasis and introduction of terms
  • Code for technical terms, commands, and file names
  • ~~Strikethrough~~ for outdated or deleted content

Readability Guidelines

✅ Good - Clear and purposeful
**Project Status:** The _initial phase_ is complete. Next: update `config.yaml` and deploy.

❌ Avoid - Over-formatted and hard to read
**_~~Important~~_** **_update_**: **check** the `file` **now**

Consistency Tips

  • Use the same formatting pattern throughout your workspace
  • Bold for section headers in lists and callouts
  • Italic for introducing new concepts or terms
  • Code formatting consistently for all technical references

Troubleshooting

Common Issues

Missing Spaces: Ensure spaces around formatting markers

❌ word**bold**word
✅ word **bold** word

Nested Quotes: Use different quote types to avoid conflicts

❌ "The command is "install package" to begin"
✅ "The command is `install package` to begin"

Special Characters: Use backslashes to escape formatting characters

❌ The price is $**50**
✅ The price is \$**50**