Submit Article


Updated: Thursday, 10. October 2019 10:27 PM UTC


If you have written an article and feel like sharing with the rest of the world, feel free to contact us with the details. You can send us an email from our contact page.

Preferred topics

We are happy with the following topics:

  1. Anything programming related
  2. Networking
  3. System administration
  4. Anything that can be on stackoverflow or unix.stackexhange can be on our site too but not as question/answer, rather re-written as an article. Do not plagiarize, write the problem and solution in an etiquette that fits an article.
  5. Linux
  6. Open source
  7. Review of online services.

If your article does not fall in any of the above categories, you may contact us to find out if there is any exception.

Preferred document format

We accept articles in the following formats:

  1. HTML
  2. Markdown

Among above, markdown is our preferred document format. Our website supports all of the basic markdown syntaxes and a lot more common syntaxes you would see everyday being used on popular websites.

To know more about our markdown syntaxes you can see our markdown help page.

Contact us with details

Once you have decided on your article, you should contact us via our contact page with the following details:

  1. Category/Topic of the articles
  2. Title
  3. Summary
  4. Your Name and a valid email address.
  5. Your expected benefits (backlinking, citations, showcasing your author profile etc..)

If we like the topic, we may contact you and provide you with tools/support to complete the article with proper markdown/html. After you submit the article we will do a final review and if everything's okay, we will publish it on our website without much delay.

Submit the written article

You should send us a zipped archive (tar or any compression available on Linux is acceptable) of possibly the following files:

  1. config.yaml
  2. .desc
  3. content1.md (you can split your document in multiple content files: content1.md, content2.md etc.. If there are 10 or more (<100) content files, name them with index 01, 02, 03 etc.. An example of mixing md and html: content1.md, content2.html, content3.md)

Example

config.yaml

type: article
title: Some Title
keywords: this-topic, that-topic
description: A short description in less than 150 letters.
ctags: Tags that this article applies to
startdate: 20/02/2016

With git repo/s:

type: article
title: Some Title
keywords: this-topic, that-topic
description: A short description in less than 150 letters.
ctags: Tags that this article applies to
startdate: 20/02/2016
gitrepo:
 - name: repo1
   branch: 1.0.2
   org: user_or_organization
 - name: repo2
   branch: 1.0.2
   org: user_or_organization

.desc

This article explains this and that etc.. keep it short but not shorter than the description in config.yaml.

You can use markdown.

content1.md

This is a command: `sudo apt update`

# What happens to headers

Headers end up in the table of contents on the left pane.

Our publication policy

  1. We do not allow plagiarized content.
  2. We do not allow multiple publications of the same article. If we find out that you have published the same article with nothing to little modification on other places, we may take down your article without any prior notice.
  3. We check english spelling, grammar and we prioritize on the content and the topic. If it does not pass our review, your article may be rejected. We will also delete all information about that article from our system.

Report plagiarization

If you are sure that some content on our website is plagiarized, please contact us with the details.