We’re looking forward to your Dev.Opera contributions!
- We pay a rate of $350 for a 2000 word article, so ideally you should try to stick to that word count. Note that we only pay this rate if the article is actually published on Dev.Opera. Also note that we do not pay this rate for article translations.
- We’re also happy to take in code improvements to the templates, styles and scripts powering Dev.Opera.
We use pull requests for article and translation submissions and code improvements. If you’re not familiar with how this works, check out GitHub’s Fork A Repo and Using Pull Requests guides.
If you have an idea for an article, file an issue with an article idea label, where we can discuss further details.
It’s important that you write your article in Markdown format. Once the article is finished, create a new folder under devopera/articles/_drafts, place the article and all its external resources (images, etc.) inside, and do a pull request.
We’ll then review your submission, possibly request you to make some changes, and once the article is found to be of sufficient quality, we’ll publish it on Dev.Opera.
We welcome translations of published articles. To make this process as smooth as possible, we suggest you keep the following points in mind when submitting a translation:
- make your translation in Markdown, just like the original article file
- give your translation the same file name as the original article and place it in
/xx/_postsunder devopera/articles/, wherexxis the relevant ISO 639-1 two-letter language code, e.g. devopera/articles/fr/_posts/2010-02-11-introduction-html5-video.md - translate the
titleandintrofields - leave the other fields untouched
- add a
language: xxfield, wherexxis the relevant ISO 639-1 two-letter language code, e.g.language: ja - add a
translator:field with the translator’s full name, e.g.translator: Andreas Bovens
If you want to file a bug report, or have an idea for an improvement to the site, file an issue with an appropriate label.
If you want to fix something yourself, fork the devopera repo, apply your fix, and do a pull request.
If you have any questions about the process, please ask @odevrel or contact andreasbATopera.com.