docs: add Markdown formatting guidance for project descriptions#347
Merged
Conversation
Adds an Artist FAQ entry covering supported Markdown (bold, italics, headers, links) and the workaround for paragraph breaks, plus a cross-reference from the staging guide's description-writing section. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
grantoesterling
approved these changes
May 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
workaround for paragraph breaks (a recurring artist support question).Background
Artists frequently ask how to insert line breaks in the description field.
<br>tags and trailing double-spaces don't work because Markdown collapses whitespace; the working pattern is on its own line. This documents the supported Markdown (bold, italics, headers, links) alongside the line-break workaround.Test plan
2-staging-and-testing.mdresolves to the right FAQ anchor example renders as intended in the code block🤖 Generated with Claude Code