You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
It would be great if Markdown was supported for the description (and any similarly large/open-ended) fields for components. Even better would be able to point to a markdown file in the repository and have that rendered from the config-as-code file.
This would make it really easy to add as much custom unstructured data as needed for components that are big and involve a lot of complexity or need extra context.
> Why would you need to display the markdown in Compass if its already in your source control, John?
I think a lot of the value add of this tool is making technical-adjacent information accessible to non-technical users. So while I personally may want to view markdown content in our repository, some users may not have access or even an account at all due to their job role.
Lastly, if the Markdown also supported https://mermaid.js.org/ like GitHub and GitLab do, that would be awesome to further increase the possibilities for unstructured information.
I like this idea very much. And while I so far more thought of just having editor features the Atlassian way (Jira, Confluence rich editor), I have to admit that markdown support certainly matches Compass' concepts much more, in terms of "open, not locked in" strategy.