When I update my add-on page on AMO, the tag is not recognized and it appears as plain text. It seems that pages in all languages of that add-on are broken, not just in the language I updated. It happened with some of my add-ons. Did I do anything wrong?
It seems that it is restricted to only writing up to 5 links, I can’t show any other addons that have an issue.
Yes, you need to convert it to Markdown (you can use ChatGPT to convert it for you if your HTML is long/complex).
It was announced not long ago:
Watch out for broken lists though, more info:
Okay, but why does it break pages I haven’t changed?
This change is not retroactive. Any content authored while HTML was supported will continue to display as originally intended. Only content updated after Markdown support was added will be treated as Markdown.
Well, I would guess, releasing new version counts as update too 
.
I’ve checked some of my older addons and they still show proper HTML description.
Release a new version of the add-on does not break the page. What I want to say is that my add-on AMO has translated pages in multiple languages, and even though I only updated the description for one of them, pages in all languages are broken.
Thanks for the clarification, @wigheardkay. I think because we basically interpret any language update as a signal that the new formatting rules should apply. I can definitely see how that could be confusing; I’ll relay your feedback to the AMO team.
I had to manually convert nearly 100 pages across 10 add-ons to Markdown because of this, and will have to do the same thing if someone translates any of my other add-ons. This has taken (and will take) a lot of time. I don’t just need to update AMO, I also need to update the source on the translation sites to Markdown.
How can I write “<” or “>” in the AMO summary? If you write it as is, it will be converted to “<” and “>”.
Unfortunately you can’t use < (\u003C) and > (\u003E) characters in the summary, but you can use other similar characters:
﹤ (\uFE64) and ﹥ (\uFE65)＜ (\uFF1C) and ＞ (\uFF1E)I’ve included Unicode escape sequences for each character in parenthesis to make it more clear what each character is.