This post was inspired by a comment I left on @dsteenman's post.
Article No Longer Available
Most of the time I prefer ...
For further actions, you may consider blocking this person and/or reporting abuse
If you use VS Code, you check out the Marky Markdown extension, which will create a TOC in markdown for you. It has a status indicator above your TOC telling you if it is up-to-date or not as you edit your document.
You can set it to update on save, so it's stays in sync with your headings always. I wrote it recently as I include TOCs in markdown documents regularly, and I don't want to be doing manual updates for this kind of thing! 🤯⛏
Awesome Tip!!! I will definitely be using this. I generally write in vscode, but often tweak and add liquid tags in dev.
You're welcome🙂 If you have any feedback or features requests, let me know! 👍
Great post buddy!
I realized that I don't put a TOC on my articles either because... 🤷♂️
That auto-generated console.log TOC is awesome!!!
I also started thinking that I should only write super posts but I tend to end up rambling a lot so now I'm moving towards single posts, I'm also thinking about making series but then it would just be 2 semi-long posts lol 😅
As an author I lean on the series. As a reader sometimes, I think just give it all to me in one so I don't have to dig. Depends on how tightly coupled the articles are. Mostly I enjoy reading concise thought out posts that gave good headings and get to the point.
This is the first time I have ever put a TOC in an article. As a reader I kinda blow by them and the feel like a waste of space, but I think other people appreciate them more than i do. I also like the point someone brought up about resuming a long article from a given point.
Usually, my real intention is not about the likes, unicorns, or even number of views. -- But it is comments / discussions. (Be it on Dev.to, or on my blog.) Not sure how to generate that...
After all, it is also about building my landscape.
Also, a lot of likes and bookmarks? But how do you measure impact? (However, chains of retweeting may tell something...)
I completely agree, the benefit that I get from DEV is in the discussion section. Posts that have a really engaging discussion are the most rewarding. ♥ 🦄 🔖 Feel good, but I grow the most from an engaging discussion.
Thank you for such an informative post.
Thank you for your the nice comment.
I'll use a lot of your suggestions in my next post & will post the link here.
I would love to get some feedback here if you could spare some time :)
Sure, I took a look at your past articles and it looks pretty good. I would say that you can probably make it a bit more scannable by adding a few more headings, and blockquote. I also prefer to split paragraphs up a bit in blog articles, I believe this is a preference, but it is one way I tailor my writing to the delivery mechanism.
Thank you for looking at my past article, I just finished posting my second post.
Like I said I have used a lot of your suggestions, can you check & see if you find any improvements there?
Here's the link.
I would recommend a few things. Utilize liquid tags to embed dev posts, and tweets rather than simple links or images. You might also want to block out the picture/username of anyone in negativity.
You never know what kind of day they were having and choose to delete their content later down the road when they realize. Screenshotting them and posting elsewhere takes away that choice for them.
"Praise in public and punish in private"
Thank you,
I will look try utilizing liquid tags next time.
Yeah, that's right, I myself felt bad about posting the details, In fact I blocked out the picture & username the very next day I posted my article.
And I really appreciate the way most people respect each other here.
I made a mistake & learned about it, I'll make sure I never do that again.
I'll remember the mantra "Praise in public and punish in private"
That was such a great tip I went back and added it to the article #compelling-introduction
Shows how much I read non tech material 😊. I've seen this reference several times.
👍
🤜
Great article!
I look forward to putting these tips into practice.
Great tips! I don't use TOC (dunno why). I will try to include them in my next posts. Yes, layout is key! For me the biggest learning is to write short paragraphs.
Yes, short paragraphs are a great hack for us mortals (Not Stephen King) to convey our messages in more digestible ways.
I have really shortened up my paragraphs over the past few months as I have started to be more active on DEV, I am learning to better communicate as I go.