ServerGrove is looking for great material to publish on it’s blog. We are interested in how-to guides, tips and tricks of a technical nature, and tutorials. Our main focus will be on the subject of web development technologies we offer our customers. So basically texts covering any of these topic areas would be of interest to us: PHP, Zend Framework, Symfony, Ruby on Rails (both Ruby and Rails as well as related subjects), GIT, JavaScript and JavaScript frameworks, Flex, ActionScript, Flash, CSS, HTML/XHTML, etc… The complete list would be quite extensive, but we think you get the picture. If you have an idea, pitch it to us! Send us a short email to with a title and description of the article you want to write. Include if you think this is a short format article ($50) or a long format article ($200) and if you have any articles you have previously written, send us the link to it.

For longer tutorials, that would result in multiple posts, please contact us to discuss possible rates. We will send you a check 20 days after your article was published, if during this time we receive any complaints about plagiarism, copyright infringement take down notices, or see your article published elsewhere on the web, we will remove the material immediately and you will not be paid. Additionally you will be given full credit for your work wherever we publish it (Blog, Electronic Magazine, etc…). The only exception to this rule would be in the case of a small portion of your work being quoted or used in knowledge base article made available to our customers.

Before submitting an article, please make sure you are familiar with and agree to the following ground rules:

  • This must be your original work. It must have been created by you and cannot have been published elsewhere.
  • Your work may be edited by us if we feel changes are needed to enhance the quality of the post prior to publishing it.
  • Portions of your work may be used in producing further materials, for example, knowledge base articles. In this case, no credit will be given to the author.
  • We try to keep our publishing guidelines as simple as possible, but you should review them and follow them in order for us to accept your submission.
  • We encourage you to use completely original content you created yourself, including code snippets, screen captures and other content. However, if you feel using material created by a third party would be beneficial to the article, we will consider it under the following conditions: 1. You must have permission to use the material (through a license or through the explicit permission of the owner of the material), and 2. You must credit your sources.
  • Keep in mind that not all submissions are accepted. We will work with the author to try to correct any problems in most cases, however we reserve the right to reject any submissions we feel are unfit for publishing for whatever reason. Even ideas that were previously pitched to us might be turned down during the submission phase, but this will only happen in extreme cases where poor quality is a significant issue or our publishing guidelines were clearly disregarded or ignored.

Publishing Guidelines

  • Only articles written in English will be considered for publication at this time.
  • The use of correct grammar and spelling are expected in articles that are submitted to us. Please proof your text and use a spellchecker before submitting it. We are not very strict about this, and will gladly make minor corrections and adjustments before publishing, however a sloppy and/or unreadable text might simply get turned-down or sent back for further work. The use of American English for spelling is preferred, but is not a requirement.
  • Try to be clear, concise and informative in your writing style.
  • Linking to external assets, such as a software library or plugin that may be required to execute code in order to run the examples from your article is encouraged.
  • Linking to external information sources, such as online documentation or other articles in order to provide further in-depth reading and a path for further exploration by your readers is encouraged.
  • The main text body of the article must be submitted as a Rich Text Format (.rtf) document.
  • If you are including additional supporting materials, place your whole project inside a directory or folder named according to the title of your article, and include additional sub-directories for each type of asset you are including (for example: your_article_title/images for anything that is a an image you want displayed within your article, your_article_title/code for code snippets in text format, etc..). We don’t want to impose a strict naming convention, so as long as you name you sub-directories with clear and descriptive names that we can we quickly identify when putting your post together, that should be fine.
  • If your article only contains text, without any supporting files, please upload only the RTF file using our article submission form. There is no need to compress the file.
  • For submitting articles with additional files (images, code snippets, etc..), please follow the directory structure mentioned above and compress everything being submitted using the ZIP (.zip), RAR (.rar) or SIT (.sit) file compression formats. This will allow you to upload a single file on the submission form, and will enable us to evaluate and publish your article faster, since your directory structure and organization will be kept once we expand the archive on our side.
  • You must read, be familiar with, agree with and follow our “ground rules” stated above.

Pitch your article: send an email to