Beginning to write Dev.to articles was intimidating for me, and a tutorial on writing articles would have helped reduce the barrier to entry. Now t...
For further actions, you may consider blocking this person and/or reporting abuse
This looks kinda like the workflow I've used.
Saving all the posts to a private GitHub repo so I can access them in any pc.
Using VSCode with the
markdown-all-in-oneand Vim extensions and boom much more efficient writing than when I used the dev.to simple markdown editor and had to got go back and forth between the edit and preview tabs 😅Great post, it's a nice intro for those who haven't found their workflow yet
Thanks for sharing, that’s exactly what it’s intended for 🙂
I’m also selfishly looking to hear what others are doing so I can refine my setup further.
Thanks for getting straight to valuable content, without shameless self-plugs and unnecessary preamble... I too hope to avoid this, as it's been a pain point in my years on the consuming end of like content.
I am now also getting into dev content creation; I'm not sure if you've exactly worked out your target audience, but I'm it (or partially representative of it). Currently, my main struggle is knowing how much information is enough, and what I can assume that my will-be audience already knows. Sure, time will tell; but sometimes you need to sharpen an axe before it can chop down a tree.
For example, a current dilemma is for a tutorial article and video: I'm really stoked about where web components are finally going, so I chose it as my first topic. To work with web components irl, there remains this inherent tooling step, and so the dilemma is this: should I walk through setup stepwise (i.e. webpack and babel installation and configuration) or provide a starter repo, introduce the subject and why I believe it's so important, and get straight to it?
I understand this is not your problem, and I may very well represent competition on some level (trust, you're miles ahead of me, my friend)... I only wrote this so that you might consider elaborating on your process of content selection and your scoping for your articles as well.
I'm, so far, very impressed with Write Good, and plan to add the "Listen to it" step to my workflow. Thanks again for pouring your hard-earned time into creating content for people like me.
Thanks, I’m glad it was helpful! Honestly, I’m doing this to improve my writing, and to try to be less afraid of learning and even failing in public.
For me, my audience is either me X days/weeks/months/years ago, or someone that I’ve interacted with recently that I didn’t have the words to help them as effectively as I would have liked.
I don’t think I’m any authority on what will be popular, but one thing I’ve noticed is that the more accessible the content is to a beginner audience the better it does. It’s not gonna stop me from writing about developer ergonomics when writing an ESLint plugin, but I need to be ok with that article not getting much of an audience.
This is really similar to my workflow as well. It's really important to have a solid structure/outline before you start writing.
Also, I use StackEdit with a GitHub workspace for writing. I'll have to try VSCode though!
That’s a cool idea, maybe that can skip my iPhone notes step at least.
I (perhaps wrongly) assumed that the native editors would be better, but kept finding myself getting tripped up by its assumptions of wanting to undo entire paragraphs instead of a bad formatting.
Very helpful
Nice article, very helpful, thank you!
Thanks for this post, I am very new to writing technical posts and I did struggle with my workflow! I guess there's no reason why we shouldn't employ the same approaches to writing articles as code 👍
Are you using this repo for all your articles? (I am looking for the current here My Dev.to Writing Process)
The articles repo is private, that’s a template with examples for anyone that wants to use it as a starter.
Cool setup I have just been using Typora and storing all of my files on my local machine. Might try adding a version control setup instead.