markdown code block title

[tonycody]

Select Topic Area

Product Feedback

Body

Show in docusaurus

Show in Github

This way of marking up the title in docusaurus is nice, and I suggest Github support it as well.

[NatoBoram]

I really like the idea of having a title to code blocks, but remember the core idea of markdown: It should be readable and make sense even in plain text form. Tags such as title="This is a title" are more suitable for BBCode or HTML. Here's my idea:

This would allow someone to set a "file name" for the code block in case it's useful. And not only that, but any title could fit there.

Another way to fit a title would be to just drop the title="" and put it next to the file extension. The rest of the line after the language name would be used as a title.

Although this format doesn't look bad either:

[ret2src]

I would love to see this enhancement, as it would allow people to semantically group things together that belong to each other.
Currently, titles and code blocks are not grouped together and people abuse things such as bold markup or Markdown headings, e.g.:

## hello.c

```c
#include <stdio.h>
int main() {
   printf("Hello, World!");
   return 0;
}
```

__hello.c:__

```c
#include <stdio.h>
int main() {
   printf("Hello, World!");
   return 0;
}
```

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[kutaycoskuner]

While it is understandable that there is a trade-off between feature creep and simplicity/ease of access; I would also be happy to see this feature. It may seem trivial but, folder structure and various architecture could make things complicated. Who owns and have access to what to achieve protected variations is one of the most strongest programming paradigms today.

On the documentation level. I do not know how many times I wanted too see not just the code but where it stands as well. Many of the packages and documents are presenting them in their own interface.