Contributing to Codrops

Welcome and thank you for your interest in contributing! We're excited to collaborate with creative individuals like you. Whether you're writing a case study, crafting a tutorial, or developing a demo, here’s a quick guide to get you started.

• We'll create an account for you on Codrops where you can write the article. You can find more info here: https://github.com/crnacura/CodropsTemplate/wiki/Writing-the-article

• Under your profile, please fill in your bio and social links. To make your profile image appear, you can upload one or associate your email with a picture on https://en.gravatar.com/

• If you are writing a case study, please check out these examples on Codrops or awesome-casestudy for inspiration.

• If you are writing a Designer Spotlight, please check out this page.

• If you are writing a Developer Spotlight, please check out this page.

• If you're writing a tutorial, see our tutorials section for examples. Note that, if not agreed otherwise, the article/demo should be exclusive, meaning that it should not be published anywhere else.

• Please don't edit the article after publication or it will turn a published post into a draft! Send us changes directly and we'll make sure to update the article.

• In case you are creating a demo that will be hosted on Codrops:

  • You can use the following HTML template https://github.com/crnacura/CodropsTemplate or, in case you are using your own, please include the links from the frame.
  • Important: please make sure that the demo build/dist has relative paths as we will deploy it to our server in a dedicated directory.
  • Make sure to use some sort of preloader if you use images/other assets. You can add the loading class to the body and remove it once assets are loaded.
  • Once you're finished with the demo(s), share a private GitHub repo with "crnacura" and "botelho" and, if applicable, we prepare the version for our server.
  • We add some final styles, the links and our sponsor.
  • All shared code/demos will be MIT licensed.
  • Once we let you know the publish date and time, make sure to set any GitHub repo to public shortly before :-)

Any questions? Just shoot us an email