How to write technical blog posts
10
How to Write Technical Blog Posts
Transcript of How to write technical blog posts
How to Write Technical Blog Posts
Tehnical writing
1.You don’t need to be an expert on a topic to write about it.
2. As a developer one of the best ways of giving back,
beyond releasing code, is by writing about your experiences.
3. Think about all the people you follow on social media.
Chances are you follow the ones that are sharing knowledge and inspire you.
4. Do research, stay tuned to the world!
Article structure
Your technical blog post needs structure. Basically, an outline
Two common methods are:
● Introduction, body, and closing.
● Pain, dream, fix
- Reaction to news, someone post.
- Problem solving, use case, bug fix.
Article TitleFor developers the best titles are those that other developers will be searching for. Headline AnalyzerNew! Never-seen-before-insights to…10 Things you Need to Know in Order to Succeed
The Secret Trick to
How [Your Field] is Like…
How I [Did Something Unbelievable]
Amazingly Awesome things you Should Read About
Are you Making this Mistake that’s [Leading to a Bad Result]?
How do you do [Activity]?
10 Ways to [Improve in your Role]
Exlusive Startegies from...
IntroductionStart the story right at the top. Tell people what the post is about and why you’re writing it. Hook the readers by letting them know you’re going to tell them a story.
“The other day, I unfollowed someone on Twitter. At first glance, we appeared to have lots in common…”
Meta description (160 characters description of your post)
Content
- Including headings and scannable break points.- Blockquotes, lists, and images.- Use keywords and outbound links- Stay creative
http://goo.gl/vXfwYU
It’s also important to write clearly and keep your style consistent. A common example is writing the word JavaScript. Don’t mix between using js and JavaScript.
Telling a story
● The simplest type of story is a use case.
● Another good story is something that went wrong, and how you fixed it.
● Or you could tell a funny story, provided it relates to the main content of the post.
Moving on to the main part of the post:
● Describe your part in the story. Make it about you, or your team.
● Then move quickly to the main topic.
● Give plenty of factual information, preferably hard-won. That’s what people value. Code samples and
screenshots are great.
● Tell how the events changed you, changed the way you work, changed your product. That’s what a story is
all about.
Content
In copywriting the closing is typically your call to action. Most developers aren’t selling anything so this is a great spot to ask for comments
https://dzone.com/https://news.ycombinator.com/http://slashdot.org/
Closing
- Reference Other Bloggers
- Hyperlinks to other sites (inbound/outbound)
- LinkedIn Pulse
- Google +
- Quora / forums
Add-ons and further tips
Questions
?
