Skip to content

Latest commit

 

History

History
52 lines (31 loc) · 5.88 KB

publish-on-our-blog-wip.md

File metadata and controls

52 lines (31 loc) · 5.88 KB
description
The DAO's loves publishing high-quality writing from our members. This page explains why it's great to do it, how you can get published and the guidelines you need to follow.

✍ Publish on our blog

Why write in the first place? 🤔

Writing is a superpower.

It helps consolidate your thoughts and understanding of topics, spreads knowledge and can have a compounding positive impact on your career, as once it's out there, it's there forever.

Check out the success stories below from members who've published on the blog.

Also, check out this 🔥 workshop from DAO technical writing legend DappaDan.

{% embed url="https://www.youtube.com/watch?v=gP6lVBt4PLQ" %}

What does the DAO publish?

Our blog aims to educate developers, give educated opinions on popular development topics, and share the experiences of the D_D members.

There are currently three types of blog submissions we're accepting that have associated rewards:

ThemeDescriptionReward
Technical TutorialsIntermediate and expert article content that educates developers about specific topics, concepts, protocols or tools.XXX USD
WAGMIA place for a community member to share their personal stories on the DAO blog to inspire others.XXX CODE
Open SubmissionOpen submission for opinion pieces or any other ideas you think would be valuable for our members and audience to readXXX CODE

We especially aim to cover topics that can't be found elsewhere or cover commonly discussed topics in greater depth so readers come away with a deeper understanding of essential topics rather than just a simple introduction.

You can read some of our most viewed articles below:

Mastering Midjourney Camera Angles by @Erik_Knoblhttps://blog.developerdao.com/mastering-midjourney-camera-anglesCapture-2023-08-24-145925.png
BUIDL a Solana Program - Explained for a Web2 Dev by @matanwriteshttps://blog.developerdao.com/buidl-a-solana-program-explained-for-a-web2-devCapture-2023-08-24-150013.png
A guide to Web3 for Web2 frontend devs by @dhaiwat10Capture-2023-08-24-150142.png
Solidity Basics for JavaScript Devs by @K4y1shttps://blog.developerdao.com/solidity-basics-for-javascript-devsCapture-2023-08-24-150359.png
How to Develop and Deploy Smart Contracts with Foundry & Openzeppelin by @pateldeep_ethhttps://blog.developerdao.com/how-to-develop-and-deploy-smart-contracts-with-foundry-openzeppelinCapture-2023-08-24-150635.png
How to Build a Full Stack NFT Marketplace by @mikleenshttps://blog.developerdao.com/how-to-build-a-full-stack-nft-marketplaceCapture-2023-08-24-150753.png

Publication Process

  1. Any member can submit an article idea via this form (please see the "What does the DAO publish" section below first)
  2. If accepted, our editors will get in touch and help you refine your title and outline. We will also decide on the mechanisms of the payout at this stage.
  3. Writing: using our content guidelines you author the article, and our editor will be available along the way if you need support.
  4. Once your draft is finalised, we will publish the article on the blog.
  5. Your reward will be issued in line with the DAO's monthly payroll on or around the last day of the month.

How do I get my employer's content published on the blog?

Thanks for your interest.

Publishing to our blog is reserved for Members to give them a platform to share their knowledge, be rewarded, and increase their profile in the industry. If you are a Member and you work for a protocol, the blog is not a platform for you to promote your employer.

We deal with such requests on a case-by-case basis. If your content is mostly agnostic of your employer's product or protocol (i.e. the content has value beyond just using their product), we may consider publishing it. However, it will likely be rejected if it is highly focused on the product or protocol and has no real value outside of using it.

You can reach out to [email protected] if you're interested in a partnership.