SAP Community HTML Tags Reference Guide (updated Oct 1, 2025)
SAP Community has historically lacked official HTML docs, which left bloggers guessing about what works. Based on community feedback and fresh platform updates, here’s a practical reference of what actually works in practice.
New (this week): the platform now supports the <code> tag and advanced HTML, enabling table-of-contents (TOC) links in blog posts and documents. See the platform’s “What’s New” note for details.
Use this guide to convert existing posts or create new ones without “unsupported HTML tags” errors. If you encounter allowed/forbidden tags not mentioned here, please comment so we can keep this up to date.
Supported HTML Tags
| Category | Tags | Notes (incl. allowed attributes) |
| Text Formatting | strong, b, em, i, u, strike, font | <font> supports face, size, color (e.g., <font color="#ff6600">). Use semantic tags (<strong>/<em>) where possible. |
| Structure | h1–h6, p, div, span, center, blockquote, hr, br | <p> supports align. <div> supports align, class. <span> supports class.
Headings get auto-generated IDs for deep linking; see “TOC & Deep Linking” below. The legacy <a name="..."> pattern does not work. |
| Lists | ul, ol, li | Standard ordered/unordered lists and list items. |
| Tables | table, tbody, tr, td | <table> supports cellspacing, cellpadding, border, width, height.
<tr>/<td> support width, height.
Tip: add border="1" if you want visible grid lines. |
| Links | a | <a> supports href, target. (No rel.) Anchors can target heading IDs for in-page TOCs. |
| Code | code, pre, li-code | New: <code> is now supported (great for inline snippets).
<pre> is allowed for preformatted blocks (monospace, no syntax highlighting).
<li-code lang="..."> remains the best option for block code with syntax highlighting. Known languages include: javascript, abap, json, bash, xml, css, html. |
| SAP Community Custom | li-code, li-emoji, li-image | li-code: syntax-highlighted blocks (see examples below).
li-emoji: use via the editor for best results.
li-image: use the platform’s image uploader; supports width, height, align, size. |
TOC & Deep Linking (Advanced HTML)
Thanks to Sandra for documenting this behavior.
- When you save a post, each heading (
<h2>, <h3>, …) gets an id like toc-hId-1366081506. - You can link to that section with
<a href="#toc-hId-1366081506">Section title</a>. - Important: heading IDs are assigned top-to-bottom on save. If you insert/delete/move headings, IDs can change below that point. Create/update your TOC late, when headings are final, and re-check after saving.
- Custom legacy anchors like
<h1><a name="tag">…</a></h1> do not work.
Code Examples
Block code with highlighting
// JavaScript with syntax highlighting
function sapCommunityRocks() {
console.log("This code block looks amazing!");
return true;
}
Inline code
Use const title = "SAP Community"; inside a paragraph.
SAP Community Custom Tags
| Tag | Example | Notes |
| li-code | <li-code lang="javascript">
console.log('Hello!');
</li-code> | Use for block code with syntax highlighting. Inline code should use <code>. |
| li-emoji | | Recommended to insert via the editor UI. |
| li-image | <li-image width="200" alt="description" align="center"></li-image> | Use the SAP Community image uploader. Supports width, height, align, size attributes. |
Formatting Tips from the Community
- Block quotes:
<blockquote> produces clean quoted sections. Many prefer adding it manually over the editor button that pastes an entire previous post. - Tables: add
border="1" if you want visible lines; otherwise the table may render without borders.
Forbidden (or Not Supported) Items
| Problem | What Gets Stripped/Blocked | Use Instead |
| Embedded content | <iframe>, <noscript> | Not supported — use screenshots/images or links. |
| Image sources | blob: URLs, certain external sources | Upload via the SAP Community image uploader (<li-image>). |
| JavaScript | Inline handlers like onclick, onload | Not supported (security). |
| Custom styles | Many CSS classes / arbitrary inline styling | Use the supported HTML formatting options above. |
| Legacy anchors | <a name="..."> | Link to auto-generated heading IDs instead (see TOC section). |
Quick Reference Cheat Sheet
| What You Want | Use This |
| Inline code | <code>yourInlineCode()</code> |
| Code blocks (highlighted) | <li-code lang="abap|javascript|xml|…">your code</li-code> |
| Code blocks (monospace only) | <pre>your preformatted text</pre> |
| Images | <li-image width="..." alt="..." align="center"></li-image> (via uploader) |
| Emojis | Insert via editor (or ) |
| Bold / italics | <strong>…</strong> / <em>…</em> |
| Colored text | <font color="#ff6600">text</font> |
| Tables | <table border="1" cellpadding="4" cellspacing="0">…</table> |
| TOC links | <a href="#toc-hId-123456789">Section title</a> (add after saving, IDs may change if headings change) |
For AI / Markdown Conversion
Try this community-shared Claude artifact to convert Markdown→HTML that’s SAP-Community-compliant (you might need to hit Save twice due to trailing <p> quirks):
Markdown → SAP Community HTML converter
Credits: Anne (new <code> & advanced HTML), Sandra (heading IDs & TOC behavior), Josh (current allowed tags/attributes), Dominik (blockquote tip), AJ (Markdown→HTML artifact), and everyone adding examples & corrections. Keep the comments coming!
Bluesky