I often get a request for the guest posts and I usually deny them as the purpose of this blog is to share what I am learning every day. However, whenever I travel to various conferences, lots of people share lots of ideas with me which they would love to share with my audience. Many times, I capture them and share on the blog with due credit to them and quite often I just can’t remember them after a week. After my recent trip to a conference, I decided I will open a blog for a week of guest posts and will share the learnings from everyone on the blog with due credit to them.
Invitation for Guest Posts
First of all, this invitation to every SQL Enthusiast in the world and we are not limiting it to one technology. As time is very limited, I have created 3 people’s teams of experts who will look at the submission and will provide feedback about the blog posts. The team will decide to publish or not publish the blog post and also will modify it as needed. Please note that once the blog post is published, while we can make modifications it would not be possible to unpublish.
Here are the basic guidelines of the blog posts:
- Blog posts should contain a minimum of 350 words excluding any code.
- There should be at least one image of width 800 px.
- Your blog post should have a Title and Content.
- It should not be marketing blog posts for any third party vendors or products.
- The blog should not include any link to any other external webpage. (Not even to the official documentation of SQL product).
- The blog will contain your name at the beginning of the blog post and link to your twitter or LinkedIn handle or both.
- Feel free to include your short bio and photograph. (No links)
- The blog post can be of any SQL technology (or even No SQL is welcome) as long as it is informative and useful.
- The blog posts will be published from 9 to 13 December 2019. If there are more than 5 guest posts, we will publish them in the week of 16 to 20 December 2019. If we have more than 10 blog posts, we will publish multiple blog posts on certain days.
- The last date to submit the blog posts is December 2nd, 2019.
- There is no compensation for the blog posts.
- The blog post should be original (not published anywhere) and free from Plagiarism.
Popular Guest Post Award
Here is the most interesting part of this Guest Post Week. On the 6th of January, the 3 members team will decide the most popular guest post. They will decide this based on the various statistics and not personal opinion.
The winner will be decided with the help of the following statistics:
We will take a blog view for the first 15 days after it’s published date and divide it by 1000 and will keep the integer number to categorized which band it landed. If there are multiple blogs in a single band we will decide the winner based on the number of comments. If there is a further tie, we will announce all tied as a winner.
Let me give you a simple example of three blog posts with their first 15 days data.
Date 1: Blog A with 6999 Views and 15 comments
Date 2: Blog B with 6001 Views and 25 comments
Date 3: Blog C with 8000 Views and 10 comments
When we look at the statistics we will look at as follows:
Blog A: Band 6 with 15 comments
Blog B: Band 6 with 25 comments
Blog C: Band 8 with 10 comments
The winner will be in the order of Blog C, Blog B, and Blog A.
The top 1 winner will get FREE Access to SQL Server Performance Tuning Practical Workshop – Recorded Classes (worth USD 1000) for one month. If you do not want the free access, you can give it to one of your friends or anyone who has commented on your blog post.
We will not rank any other blog posts or publish any other rankings.
Submit Your Guest Post
The process to submit the blog post is very simple.
Just send an email to firstname.lastname@example.org with the title “Guest Post – Title of the Blog Post” before December 2nd. You will get confirmation from me in 24 hours and if the team accepts your blog post they will inform you on December 2nd, 2019.
I think it is going to be a fun party and everyone is welcome to join!
Reference: Pinal Dave (https://blog.sqlauthority.com)