Guest Post Guidelines

Hi and thank you so much for considering to write a guest post on this blog! Here are some tips and hints for you, since even if you are familiar with WordPress, there might be differences due to plugins etc. If you have any questions that are not answered here, please let me know.

Your account

Hopefully, I already have sent you login credentials to your contributor account (You might also want to check your spam folder). You can use them to log in here. There’s also a link on the start page, further down in the sidebar. While you’re there, please write a few sentences about you in the “biographical info”, for example like Jonathan Boccara.

Your post

The topic of your post should fit well into the blog, i.e. it should be about something that enables us to write cleaner (C++) code, better tests etc. It should, however, not be about a specific commercial product. Please understand that this is not the right place for marketing for companies or commercial individuals. The length of my posts usually is roughly between 600 and 1200 words. Yours should not be much shorter. If it becomes much longer, we should discuss if we can split it into two parts or if the scope can be reduced.


You are free to structure your post as you see fit. The first heading should be an h1 heading, but it does not need to be before the first paragraph of your post. Be aware, that the table of contents for your post will be generated according to your headings. I will add a short paragraph as an introduction where I’d like to include a short bio of you, so please leave me two or three sentences describing what you do and where people can find you online.


I use a MarkDown plugin for formatting. See this MarkDown cheatsheet if you are not familiar with MarkDown. You can also use a few HTML tags, like <h1>, <h2> etc. for headers, <a> for links and <strong> and <em> for bold and italic text, respectively. Keep your paragraphs and sentences short for better readability. If you want to draft your post offline, please paste it as MarkDown or plain text, not as preformatted HTML, like you get it from e.g. MS Word. Such HTML contains lots of unnecessary styles that mess with the blog style and needs some tedious editing.

I don’t have a code formatting plugin like Crayon, because it does not cope well with the MarkDown plugin, so you will have to write code snippets in plain MarkDown. Simply indent the code by 4 spaces, or add a line with the usual triple backticks before and after your code.


When you are done, I will proofread and review your post. I might give you some hints where I think a different wording might be better, and I will fix the spelling and formatting when I find errors. It will help both of us if you use a spell checker, though, and I also find tools like Grammarly quite useful for non-native speakers like myself.

In the review phase, I will also add that introductory paragraph. After that, I will ask you to approve my changes one last time.


Your post will be part of the regular blog schedule, which is currently Wednesdays, 3 pm UTC. I will usually schedule your post to be published in the next two weeks after the review and your approval. On rare occasions, I might already have scheduled posts on those dates that I can not reschedule. In those cases, your post will be scheduled as quickly after those fixed posts as possible.

And now, welcome aboard and happy blogging!

Facebooktwittergoogle_plusredditlinkedinFacebooktwittergoogle_plusredditlinkedinby feather