![]() ![]() It's not because its already written you shouldn't write.We define our words, but they don't define us. Writing for all types of audiences is not that easy. For better technical writing the Shoptalk Show Episode with Rachel Andrew is a good listen. On Writing Well by William Zinsser and Bird by Bird by Anne Lamott are good books to a bit more in-depth. There is still a huge list of writing related books on my Goodreads shelf to improve my writing skills but Writing for designers by Scott Kubie is a great starter. Quality Control (checking links, sources etc.).In steps it would look something like this: After writing the post I do some final checks based on this smashing article template and create the assets for social sharing in Figma. These tools are live-savers for me, it would otherwise take me tons of time to edit which I really don't like doing. If the flow of the text still feels off I sometimes let VoiceOver read the article to me. Editing: things like spell checking, punctutation, the flow of the sentences and any other small revisions.Īfter the final draft is finished I run the text trough Grammarly and the Hemmingway Editor.The goals is to put as many thoughts out of my head into notion. Drafting: Just write, it doesn't matter if its fast and bad.Hunting: the goal is to just gather as much resources and research material.Nothing really methodical but I have basically three stages (inspired by this Tim Ferris podcast) hunting, drafting and editing. Usually I'll also add a status and created by date. ![]() People (student in particular) ask me on my opinions, I usually take note of those and if I get that a questions frequently or that topics comes up frequently I write a post about it. I don't usually go 'hunting' for idea's they just accumulate over time. I'll add it to my writing Notion Board with initial thoughts and the resources where I got the idea from. Some must use extensions are:Įvery time a new idea of an article pops up in my head. I'll use cmd + b to toggle the sidebar to navigate files, cmd + shift + p to preview markdown and use ctrl + backtick to open the integrated terminal to commit markdown files. It then changes my color theme to White Night and sets the writing font to Duospace. So I have workspace that puts me in my posts folder of the website. It's easy to change color themes based on the folders you are in. With the introduction of workspaces you can configure settings for specific folders. That is a quick win to make it feel more like a writing app. VS Code has a zen mode to get rid of most of the UI. Since I'm spending most of my time looking at my editor anyways it's seemed like the obvious choize. Can I just use VS Code as my default writing app? Code editors have a bunch of useful features for editing text. After all that testing it struck me, VS Code has lots of these features already built-in. I thoroughly tested 12+ writing apps and explored their features. Commit markdown files to a repository after I'm done writing.Support syntax highlighting for the metadata (in yaml) format on the top of each file.To get a feel of how big sections are (flow of the article) and if all the links are displayed. Markdown Preview to see the text with formatting.Navigation and most UI elements should be out of my away. Distraction free, so no bells and whistles.This is my entire writing workflow, from initial idea to draft to published article. For me it's a way to understand the material I'm personally learning and write things to remember them. Writing is a general good skill to have and it's the best medium to voice ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |