Thank you for considering joining codedamn as an author. There's so much that needs to be done in the developer space - and writing blogs and helpful articles is one of the best ways to contribute back to the community.
codedamn has a simple motivation - help learn people to code who just need a little push. We can achieve it effectively only by creating an energy loop where we help people learn and those people help other people learn. Codedamn's news section is one of the major pillars of learning at codedamn.
As an author on codedamn, you can expect your content and presence to reach to hundreds of thousands of people every month who can benefit from your knowledge. Codedamn has a solid social media presence, SEO, and an established reputation as a serious learning resource. This will help you get more people to read your articles.
This is also a style guide you can use while you're writing your blog posts on codedamn. We'll give you tips for how you can maximize your impact by making your articles as strong as possible.
- codedamn publication is not for casual/personal updates and out-of-context posts.
- If your blog post is under 800 words, consider expanding more on the topic and sharing more research in form of words and paragraphs.
- Taking care of grammar, spelling, and formatting in your articles. You can use free tools like Grammarly to evaluate all these things. Well formatted articles get magnitudes more readership than a poorly written article - delivering same value.
- Proof-read your article: Often times, when you read your article again from a distance, you will catch tone errors, spelling mistakes and places to improve. Putting articles in front of a huge audience must be good. Therefore, to save time for everyone, it is recommended you proof-read your articles once you have completed them.
- Add syntax highlighting to your code wherever you include code snippets. You can create a code block by typing three backticks (```) and hitting enter key.
Before you start writing your story, spend time crafting a compelling headline. Your entire article will then spring forth from that headline and hook back in to support it.
Here are a few headline structures we’ve found that work well for deep technical articles:
- "How to fix…"
- "How to build…"
- “How to [task] with [tool]”
- "How [something] works"
- "The [adjective] guide to…"
- “What is a [noun]? In English, please.”
- “What exactly is [noun]?”
- “Why [something] matters.”
- “Learn [something] in N hours”
- "A history of [something]”
- “The story behind [something]”
And here are a few headlines structures that work well for personal narratives:
- "How I [did something]"
- “I [did something]. Here’s what I learned.”
- “How I went from [something] to [something] in N years”
- “Why I started [something]”
- “I’ll never [something] again. Here’s why.”
- “How I [did something] without [something]”
- "Why I don’t [something] anymore"
Once you’ve chosen your clear, informative headline, add a nice cover image. Click the gear in the top-right corner.
Some contributors create their own cover art for their article. A free site like Canva.com can help you with this process. (If you want to prevent the edges of your images from getting cut-off when your article is shared on Facebook or Twitter, use an image aspect ratio of 1.91:1.)
If you don’t have an image, you can add a Creative Commons Zero (no attribution needed) image by clicking the Unsplash button in the lower left hand corner.
Cross-posting articles - avoid it
If you want a lot of people to read your article through SEO and social network, we recommend you publish that article in a single publication – whether that's codedamn's publication, or your own blog, or an online magazine.
And if you want to feature your own writing from other publications on your own blog for potential employers to see, you can cross-post onto your own blog and just use a canonical URL to point back to the original publication. This will reduce the likelihood that Google gets confused and shows the wrong version in its results.
You can, however, take some of your personal blog posts on a similar topic (such as "Visual Studios Plugins" or "Advanced Bash Commands") and anthologize them into a single, longer article.
Our philosophy is that since we are going to spend hours coaching you on your article, meticulously editing it, and publicizing it to the broader community, we ask that you not cross-post it on open publishing sites like Medium, Hashnode, etc.
Self promotion is absolutely acceptable, and even encouraged to build your following, given the following rules:
- We ask that you keep this as tasteful as possible. It is perfectly fine to have a one-sentence call-to-action for your product at the end of your article.
- Don’t open your article with a link to your product, as this looks spammy. And don't use affiliate links in your articles unless they are links to books or courses that you have personally created.
- Your social media profile links and bio will automatically be picked up and displayed in the author box.
Becoming a Top Author
codedamn will feature selected Top Authors every 6 months (twice every year). To become a one of the top-author on codedamn:
- Be in the top 10 writers by readership for the time-frame. (Google Analytics statistics for the publication are shared with every author)
- Consistent articles quality and content.
The rewards for being a top author:
- Exclusive developer swag from codedamn - coffee cup, a developer hoodie and lots of laptop stickers.
- Upto 1 year codedamn 1337 membership license for giveaway/personal use (worth $150 USD)
- Permanent listing in Author Hall-of-Fame of codedamn.
Ready to apply?
Complete the application and we will review it and get back to you soon: https://forms.gle/bc1YfNjuZUUQ6iC88
Thank you for sharing your insights with the developer community.
We hope this guide will help you write better articles so the entire community can benefit from your insight.