As I read articles on here, and on other sites like Medium, I sometimes see people post pictures of their work.
Services like Carbon let you paste...
For further actions, you may consider blocking this person and/or reporting abuse
Hi Ben. I found your post through a link in a comment of a recent post. Very nice writeup. There is a way to actually show backticks in a code block without using a different symbol as a stand-in.
If you want to show the backticks in a code snippet, you can put 3 tildas
~~~
on the line before the opening backticks and then again on a line after the closing backticks. Here is an example.I don't know if this works in all flavors of Markdown, but it does here on DEV.
This is really Good
🙌
When I draft things they look fine in preview. Well, not 100%, previewing liquid tags in comments is a little shaky. But posts look ok to me in draft.
Is it possible that in drafts there are different classes on the page and you have a browser extension that's blocking something?
I'll do triple backticks here:
Does that look right for you? Can you try the same in a reply?
I could counter argue this with three points:
As someone who writes on both DevTo and for FreeCodeCamp. What I tend to do is do both. I place an image of the code with styling and formatting, so people can see the code as they would on an IDE / Code Editor. Followed by the code in a code snippet for accessibility (best of both worlds)
By using a snapshot of the code , it also offers the reader the opportunity to write it out by hand. In my opinion this is not a bad thing when teaching someone something. The task of writing something out by hand, (not just copy and pasting) can help readers to learn the concepts, familiarise themselves with the syntax and actually understand the code. More times than not, an article is being written to promote learning sharing knowledge, on the cases where it's to solve a problem / fix a bug. Then this is where I'd agree with you, just utiliae code snippet markdown.
It's also worth remembering code snap tools aren't just for writing articles. They can also be useful for just sharing code problems with team members via Slack, Jira and other forms. It's much nicer receiving a styled code snippet on Slack, than they're default code snippet markdown.
I see your points, but counter-counter with these:
Seeing the same thing twice in an article is just plain weird. It'd look like a mistake, especially since the platform will apply its own syntax highlighting, etc., which will look different.
While I guess I get the motivation, you're explicitly deciding to exclude people with accessibility needs in order to force people not to copy the code.
Another issue: poor internet connections and images don't mix very well. Being in the 25kb+ just for 400 bytes of code is crazy.
Thank you very much I did not know the triple ticks + language to add some colours and I loved it because it really makes the difference