This looks like a good post here. Can you share this in full on DEV, instead of linking to it?
The SEO could also be taken care of via canonical_url frontmatter, which you can find more in the Editor Guide.
DEV generally asks that folks share their posts in full if possible and there is tooling provided (dev.to/settings/publishing-from-rss) to make it so that it's relatively easy to repost from outside blogs.
Hope you'll consider sharing the full post going forward.
I'll read more about how to do this and i'll work to publish full articles okay? (I'm new on this platform, i see another article doing exactly the same..)
Hi Igore,
This looks like a good post here. Can you share this in full on DEV, instead of linking to it?
The SEO could also be taken care of via
canonical_url
frontmatter, which you can find more in the Editor Guide.DEV generally asks that folks share their posts in full if possible and there is tooling provided (dev.to/settings/publishing-from-rss) to make it so that it's relatively easy to repost from outside blogs.
Hope you'll consider sharing the full post going forward.
Hi Sung,
Thank you by your recommendations.
I'll read more about how to do this and i'll work to publish full articles okay? (I'm new on this platform, i see another article doing exactly the same..)
Thank you!
Bye bye!
Sounds good, Igor & welcome to DEV 🙂
There are so many posts that slip thru 😅 but we try to suggest to post a full content as much as we can.
Done. Is it ok now? Thank you! ;)
Looks much better~ 😃 Thank you, Igor.
And as a tip, you can also highlight code using triple backticks with language.
Wow! This looks better!! Thank you Sung! I appreciate your help!
dev.to has a tutorial with best practices?
Thank you!
You're welcome there, Igor :)
Unfortunately, there isn't a best practice but there isn't a "best practice" documentation 😅. (The syntax highlight is a nice-to-have).
It's a good idea so would you be able to create an issue requesting a best practice documentation?
github.com/thepracticaldev/dev.to/...