-
Notifications
You must be signed in to change notification settings - Fork 30
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. Please get familiar with the writing tools available in this guide.
-
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 Gravatar
-
Depending on what you are writing, please have a look at the relevant templates: Case Study, Designer Spotlight, Developer Spotlight, Studio/Agency Spotlight, Creative Process, Artist Feature.
-
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 a duplicate should not be published anywhere else.
-
We'd love for you to write your first draft in your own words, and then use AI just to help polish or clarify things. Please don't stress if your English isn't perfect. What matters most to us is your voice, your story, and your authenticity.
-
Pick a submission date: To help us stay organized and ensure a smooth publishing process, please pick a date from this calendar (it's not a real meeting). We'll then coordinate a publication date together after draft submission.
-
Please don't edit the article after publication! 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.
- VERY 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
loadingclass 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, 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 :-)
- Don't worry about the demo/code buttons, we will add those!
Please note that, unless agreed otherwise, the article should be exclusive to Codrops and should not be published anywhere else.
Any questions? Just shoot us an email