The discussion focuses on the difficulty of distinguishing inline code in Discourse’s markdown rendering. bruno_at_dq shares an example and compares it to Stack Overflow and Slack, which provide better visibility for inline code.
omarfilip suggests adding a CSS code to the theme to make inline code more noticeable. However, this solution affects both inline code and code blocks. bruno_at_dq asks if it’s possible to target only inline code, as code blocks are already fine.
omarfilip explains that distinguishing between inline code and code blocks is challenging and suggests consistency between the two. bruno_at_dq thanks omarfilip for the help and mentions that their product uses Slack’s style.
The discussion concludes with sam recategorizing the topic to enable the “solved” button. bruno_at_dq has trouble marking a specific reply as the solution, but sam resolves the issue by marking the solution himself.
Inline code in Discourse’s markdown rendered is hardly discernible. Here’s a sequence of the word code with code formatting in every other occurrence: code code code code. It’s very hard to tell the difference.
Compare for instance with how it shows on Stack Overflow:
The discourse community my team manages is tied to our product and in our product, we aren’t consistent between these two types of code rendering. We use Slack’s style.
How do I go about marking this post as solved? I can’t for the life of me figure this out.