Plenty.<\/p>\n\n\n\n
If you can write release notes or a page full of useful technical documentation, it\u2019s just as easy to write a blog post<\/a> with some commentary about your\u00a0project<\/a>, something you\u2019ve learned recently or some top tips you can share.<\/p>\n\n\n\n
Blog posts go hand in hand with\u00a0project releases\u00a0as timely commentary or an announcement that the feature you\u2019ve been working so hard on is available. Write about why it\u2019s so useful and how someone can get started.<\/p>\n\n\n\n
It doesn\u2019t have to wait until your release. You can provide regular updates on how things are going. But remember to think about the ‘why’ and not the ‘how’ to avoid repeating what you\u2019re putting into your technical documentation.<\/p>\n\n\n\n
People love lists of quick,\u00a0readable tips\u00a0for languages<\/a> they\u2019re learning about or tools<\/a> they are new to. You will be surprised how many things you think are obvious, that others have not considered.<\/p>\n\n\n\n
Have you been studying something in your spare time? Working on your professional development<\/a>? You have a unique point of view, so get writing and share it in a blog post.<\/p>\n\n\n\n
The best way to get started is to get started.<\/p>\n\n\n\n
It can be nerve-wracking to put yourself out there, so I\u2019ll reiterate what has been said in posts before:<\/p>\n\n\n\n
Be prepared for friendly comments and questions \u2026 and start thinking about the next blog post.<\/p>\n\n\n\n
Photo by Jess Bailey<\/a><\/strong> from Pexels<\/a><\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"