Get $500+ of the best After Effects files, video templates and music for only $20!

Tutorial Submission Guidelines

Sections: Jump to any Section of this page quickly by following a link below:

Getting Started

Content Types

Important Information

Getting Started

Learn about submitting content and getting published on Activetuts+. Our vision for the site is one where passionate creators of browser-based apps and games — designers and developers alike — can come to learn high-end techniques. We want every tutorial to demonstrate techniques that could easily be used in professional work

We are looking for detailed, many-step tutorials that create a complex and high-end final result. We’re covering the following topics, in no particular order of preference:

  • Flash games and browser-based apps
  • Unity games (both 2D and 3D)
  • HTML5 apps and games that run in a browser
  • Silverlight RIAs
  • General game design and UI
  • Tips on becoming a better designer or developer

Submitting Content to Activetuts+

Prior to submitting content we recommend that you read the entire instructions on this page. Be sure to review the sections on Asset Licenses and Plagiarism and Crediting Sources, as well as the Activetuts+ Author/Artist Agreement. Also, review examples of prior content published on our site. Search for the topic you’re writing on to see how your idea would fit on Activetuts+, and find out if it’s something we have already covered. Of course we’re looking for new ideas, workflows, and techniques.

We publish multiple content types on Activetuts+, such as: Written Tutorials, Video (Screencast) Tutorials, Quick Tips, Articles and Premium Content. Each content type has submission instructions, be sure to read the relevant sections thoroughly.

Submit Content for Review

Send in a short paragraph concept pitch for review, using the following form:

After this, our editors will review your pitch. If it’s suitable, they’ll help you develop the idea to make sure it fits the site, and then approve it for you to go ahead and write it up.

About Publishing on Activetuts+

Activetuts+ is a well established community with a focus on browser-based app and game creation that helps developers learn new techniques, theory, and practical know-how that will help them achieve their goals. If you have some helpful knowledge you would like to share, then we’d like to talk with you.

Working With You

We have a strong belief at Tuts+ that everyone has unique ideas to share and techniques they come across as they work and experiment. We’d love to here your creative content ideas and look forward to potentially working with you.

Payment

Want to submit a tutorial or other content to Activetuts+? We only accept content that matches the site’s writing and content standards. If your content is accepted, we’ll pay an agreed USD rate per item published, and you’ll get to help your fellow aficionados! You must have a PayPal or Moneybookers account for us to pay you. This fee will be paid within the first week of the next month, following publication.

Profile

As an author, you will be featured at the bottom of each tutorial you write. You can see an example of this here: AS3 101: Variables. When you submit your first tutorial you’ll be asked to provide a short bio, a homepage URL, and an avatar to go in this space.

You’ll also get an author page, with a list of all tutorials you’ve written for us, like this one: Dru Kepple’s author page. You can use our “awesome author” pennant to link to your author page from your blog, website, forum, or email signature… anywhere you like! Check it out:

Dru's Author Pennant

And if you’re an ActiveDen member, you’ll get a special “has completed a tutorial” badge for your AD profile, too!

What to Teach?

We are looking for detailed, many-step tutorials that create a complex and high-end final result. We’re covering the following topics, in no particular order of preference:

  • Flash games and browser-based apps
  • Unity games (both 2D and 3D)
  • HTML5 apps and games that run in a browser
  • Silverlight RIAs
  • General game design and UI
  • Tips on becoming a better designer or developer

We’re looking for tutorials and other content that combines high design, with theoretical foundations, workflows and tips. We’re especially looking for advanced-level content at the moment. Feel free to make any suggestions though.

Your Content Must Fulfill the Following Criteria

  1. Your content must be your original work and not published elsewhere.
  2. You will need to format your content as per the template, which the editors will send you if your pitch is successful.
  3. You must have a PayPal or Moneybookers account for us to pay you; your fee will be paid within the first week of the new month, following publication.
  4. Your content may be edited prior to publishing.

We recommend you pitch your concept to get feedback from us, prior to submitting the full content. Please note not every tutorial/content idea will be accepted.

Technical Points

To maintain consistency throughout the site, we have the following guidelines for Flash tutorials:

  • Code should be AS3 only – no AS2!
  • Avoid coding on the timeline. Use a document class instead. This makes the tutorial accessible to more readers.
  • For the same reason, avoid using the “auto-declare stage instances” option.
  • There’s no need to explain document classes to your readers; just link them to this Quick Tip.
  • Save your FLA files (if any) in the earliest version of Flash possible.

These rules aren’t written in stone, and sometimes a great tutorial idea will require breaking them. (For example, a haXe tutorial wouldn’t use AS3 code, and a complex animation technique may be impossible without timeline code.) But please let us know if you plan to do this, before starting the tutorial.

Content Types

Review information on the types of content we accept for submission and publish on a regular basis for Activetuts+.

Written Tutorials

These are long form written tutorials. We prefer more complete, practical and extensive tutorials, placed in the context of professional workflows with high quality final artwork. Tutorials should be 20 steps or more and have an image or code snippet accompanying each written step. Here are some examples of written tutorials on Activetuts+:

How to Format Your Written Tutorial for Submission

Your tutorial must come with:

  • Finished sample source files for readers to download.
  • A 200x200px preview image of the finished product to go on the front page of the site.
  • An HTML file with the tutorial written out. You’ll receive a template to use once your pitch is accepted.
  • All images for embedding in the tutorial (these should be no more than 600px wide).
  • A preview of the final effect. This preview should be a live demo (SWF, HTML, .unity3d, etc) unless this is not possible for you, in which case a screencast video or series of screenshots will suffice.

Also note that the tutorial must be original. The technique being shown must be one you have created, and the tutorial you submit may only appear on Activetuts+ (except in offline format, where it can be resold).

If you’ve used images in your source material, then please read the section on Photography and Source Images in the Plagiarism and Crediting Sources section below.

Submit Content to Activetuts+

To pitch us a content concept for review or to send final content for editing you can use our forms found here: Submitting Content to Activetuts+.

Video (Screencast) Tutorials

These are long form video screencast tutorials. The benefit of this format is that one can see exactly what the developer/designer is doing. We prefer more complete, practical and extensive tutorials, placed in the context of professional workflows with a high quality final outcome. Video tutorials should be well thought out, with clarity of voice, and show practical working methods. Here are some examples of video screencast tutorials on Activetuts+:

We’re looking for full unique video tutorials. While the examples above show video versions of tutorials, we’re not looking for people to remake any of the written tutorials on the site, as we already have that covered. We are only looking for unique video tutorials.

How to Format Your Video Tutorial for Submission

Please review the suggestions in the Written Tutorials section, as many of the same issues apply to video tutorials. Also, ensure that you adhere to the following rules when recording and submitting your video tutorial:

  1. Video length must be 15 minutes or more.
  2. Introduce yourself at the beginning of the tutorial and say you are making this tutorial exclusively for Activetuts+ (by the way, “tuts” rhymes with “nuts” and “cuts”, not with “boots” or “flutes”).
  3. Submit an MP4 format of the final video. MOV is also accepted. In either case, use H.264 encoding. Do not use FLV.
  4. Final video must be in High Definition (1280×720 (16:9) or 960×720 (4:3) for 720p).
  5. You must include a written description of your tutorial.
  6. Include a 200×200 pixel preview image to go on the front page of the site.
  7. Include a preview of the final effect. This preview should be a live demo (SWF, HTML, .unity3d, etc.) unless this is not possible for you, in which case a shorter “preview” video or series of screenshots will suffice.
  8. Include a Video Screenshot. This is a screenshot of the video that we include when we upload the video (should be different than the final image).
  9. If the video file is 100MB or more, then break it up into more than one video. Each part cannot be more than 100MB.
  10. Audio quality must be good and narration must be clear and well thought-out.

We use Blip.tv to distribute our video, you can see previous videos at Activetuts.blip.tv.

Submit Content to Activetuts+

To pitch us a content concept for review or to send final content for editing you can use our forms found here: Submitting Content to Activetuts+.

Articles

We do have a regular group of writers that contribute content such as interviews, roundups on resources, and inspirational posts. However, we are currently accepting this type of material from our general audience. As we only publish a limited amount of this material it is important that you pitch your submission first. Pitch your content here: Submitting Content to Activetuts+.

There are some types of articles though that we are always interested in, such as: articles that explain game design, those that cover UI and UX of browser-based apps, and case studies of high-end projects.

How to Format Your Articles for Submission

Ensure that you adhere to the following guidelines before submitting your article:

  1. An HTML file with the article written out. The article should have multiple headings, major headings get h2 tags, and you’re welcome to use h3 and h4 tags as needed. Additionally you should have a paragraph at the beginning giving an introduction. And include a well thought out conclusion.
  2. Include a 200x200px relevant preview image to go on the front page of the site.
  3. Images in the tutorial should be no more than 600px wide and please follow the guidelines in our Plagiarism and Crediting Sources section. Also, you’re encouraged to use examples from your own work to illustrate your points when relevant.
  4. When packaging your tutorial place all the images in the same folder as the HTML before sending.
  5. While some topics may require more length, aiming for 800 to 1200 words is a good range for article size.

Submit Content to Activetuts+

To pitch us a content concept for review or to send final content for editing you can use our forms found here: Submitting Content to Activetuts+.

Quick Tips

Quick tips are 3-5 minute screencasts, short articles, or short 6-10 step tutorials on how to do something simple, quick, but useful. There are lots of little tips, tricks and techniques that are too small for a long format tutorial, but would still be useful and beneficial to the community.

We post numerous quick tips each week, and pay $50 USD as the base rate for these.

Quick Tip: Short Written Tutorials

See our Written Tutorials section for information on putting together a written tutorial. Quick Tip tutorials are similar, except these are shorter and more focused (6-10 steps). Here is an example:

Quick Tip: Screencast/Videos

See our Video (Screencast) Tutorials section for information on putting together a video/screencast tutorial. Quick Tip screencasts are similar, except these are shorter and more focused (3-5 minutes). Here is an example:

Quick Tip: Articles

See our Articles section for information on putting together written articles. Quick Tip articles are similar, except these are shorter and more focused (around 500 words). Here is an example:

Submit Quick Tips

You can send in for review a short paragraph Quick Tip pitch, prior to writing or recording your quick tip. You can do this by following this link: Activetuts+ Preview Submission Form. Final content can be submitted here Activetuts+ Preview Submission Form.

Submit Content to Activetuts+

To pitch us a content concept for review or to send final content for editing you can use our forms found here: Submitting Content to Activetuts+.

Submit Content to Activetuts+

To pitch us a content concept for review or to send final content for editing you can use our forms found here: Submitting Content to Activetuts+.

Premium Content

Artists can earn more by submitting Premium content. In addition to our regular site, we also offer Premium tutorials for our premium members. These are generally advanced tutorials. They are an opportunity for members to learn how to create stunning, complex apps and games from master designers and developers.

If you have a fantastic in-depth written or screencast tutorial idea feel free to send us your idea. Note that we pay more for these and are happy to negotiate the payment amount. Feel free to pitch a concept using the forms below.

Formatting Premium Tutorials

If your Premium Tutorial is written, then review the Written Tutorials section above for formatting information. If you Premium Tutorial is a video, then review the Video (Screencast) Tutorials section above for formatting information. We will send you additional formatting information upon concept acceptance as well.

Submit Content to Activetuts+

To pitch us a content concept for review or to send final content for editing you can use our forms found here: Submitting Content to Activetuts+.

Important Information

Read and understand this important information prior to sending final content for the Activetuts+ editing team to review for publication.

Activetuts+ Style Guide

For style, spelling, grammar, etc., the Chicago Manual of Style and the Merriam-Webster Collegiate Dictionary are used, with the following customizations for Envato.

Summary

  1. Menus and Palettes – Prefer capitalization to any kind of formatting (bold, italics; em, strong, b tags, etc.), as it will probably be removed later by the editors.
  2. Italicize (with the em tag) – Use if (1) you are referring to a word as a word or letter as a letter (see Summary item #4 for an example), or (2) you want to emphasize a word.
  3. Spelling – Use American spellings if you can. This is something we’ll correct for you, however, so don’t worry if you’re not familiar with the conventions of American grammar and spelling.
  4. Keyboard Shortcuts – Use a + between commands but a hyphen if using the word click, as in Ctrl-click. Shortcuts should be spelled as they are written on your keyboard keys.
  5. Remember, only ONE space after a period.

See the full style guide below for a couple more items and examples of the above items.

Keyboard Shortcuts

  1. Keyboard shortcuts are capitalized and spelled Shift, Command, Alt, Enter, Ctrl.
  2. Use the + key to separate shortcut commands but a hyphen with the word click.
  3. Capitalize the keyboard letters you refer to.

Examples:

  • “Now press Command + Shift + I to inverse your selection.”
  • “Command-click the handle layer to select its pixels, go to Select > Modify > Expand, and use a value of 1px. Then in a layer below the handle layer, fill your selection with white. Then press Command + D to deselect and then press the right arrow twice to move it to the right. This is just to give our handle a bit of a thin white highlight.”

Menus, Palettes, and File Paths

  1. ONLY capitalize (no bold, italics or other emphasis) when you’re speaking directly about the menu/palette settings, but lowercase if you’re speaking generally: Opacity/opacity.

Capitalization

DO capitalize:

  1. Flash, Silverlight, Unity, and acronyms like AS3, FLA, SWF, XML
  2. Web, Web site, Internet
  3. Font names

DON’T capitalize:

  1. Colors
  2. The word e-mail.

Numbers

  1. If using a number between one and ten as a word in a sentence, spell it out in letters.
  2. Use numerals for all numbers that need to be entered in code, or in dialog boxes or panels.

Examples:

  • “Use the Rounded Rectangle Tool (Shift + U), and enter a Radius of 10px.”
  • “In fact, there are three gradients drawn, and three 1-pixel lines used.”
  • “As there are five options, we need to set the numOptions parameter to 5.

Code Inside Text

  1. Always surround code keywords, class names, variable names and variable values with the “code” tag.
  2. If you need to refer to a piece of code in text, again, use the “code” tag. For example: “You need to replace the call to startUpload(filename) with a call to enqueueUpload(filename).”
  3. Long snippets of code – anything more than a single line, or that doesn’t need to go in the middle of a sentence – should go inside a codebox.
  4. When using a function name in your main text, include an empty pair of parenthesis. For example: “The next step is to create the enqueueUpload() function we referred to earlier.”
  5. Similarly, when referring to an array, include an empty pair of square brackets. For example: “Our new army[] array will contain all the instances of the Enemy object.”

(Once your pitch is accepted, your editor will send you a template explaining the code and codebox tags.)

AS3-Specific Technical Writing Points

  1. Avoid the term “global variable”; use “public variable”, “private variable”, or “protected variable” as appropriate, to avoid confusion.
  2. Use all-caps when talking about an event name; for example: “We need to listen for the COMPLETE event.”
  3. “MovieClip” and “movie clip” are two different terms. The first refers to an instance of the MovieClip class, while the second refers to a movie clip symbol in a Flash Professional library. To avoid confusion, always write either “MovieClip” or “movie clip symbol”; never “Movieclip” or “movie clip.”

Asset Licenses

In a nutshell: if you have used any assets — images, sounds, music tracks, fonts, Collada files, source code libraries, anything at all — in your tutorial, and you didn’t create them, then you must obtain redistribution rights for the assets.

We will not publish any tutorials that use assets for which we don’t have redistribution rights.

But I Got the Assets for Free From Another Site!

Just because another site allows you to download and use an asset for free, that doesn’t mean you can use it in your tutorial. There are two reasons for this:

First, the assets might be given away under a “free for personal use” license. Since you will be paid for your tutorial, that means the assets will be used commercially, and therefore not covered under that license.

Second, there’s a difference between a “usage” license and a “redistribution” license. If you have a usage license for a font, for example, you are allowed to create interfaces that use the font as its main typeface. Unless you have a redistribution license, you are not allowed to give the font file to someone else, to let them create interfaces using it. Since we include all of the assets a reader needs in order to follow the tutorial in a ZIP file, we need redistribution rights for all of the assets.

How Do I Get These Rights?

The site where you downloaded the assets should state what kind of license the assets are released under. If this is not the case, you must contact the creator and ask them if you may redistribute the assets and use them for a commercial purpose.

In either case, make it clear to your editor that you have the license needed.

Plagiarism and Crediting Sources

There are a few issues to be wary of when writing tutorials and putting together content.

Credit All Sources and Use Common Sense

Always credit your sources. This regards the actual wording of your tutorial, as well as any assets used. When you credit your sources, it’s clear that you aren’t trying to hide something. For tutorial submissions it also lets our editors check that the tutorial is acceptable.

Use common sense and err to the side of caution. There are no hard and fast rules about copyright. Beware of “rules” like ‘copying 40% is OK’, there’s no such thing. And remember that even aside from exact words or images, it can be the idea or principle. If you think something might not be OK, then trust your gut and don’t do it.

Photography and Source Images

Some tutorials make use of photos for their effects. There are a few things you need to know in this regard:

  • DO NOT use images from Google Image search or simply taken from a website
  • DO NOT use images from Flickr UNLESS they have a Creative Commons License for Commercial Use. In this case you must provide an attribution link back to the Flickr page you found the image on, both in the tutorial itself and in the sample files, clearly visible. Note you can find CC Commercial images on Flickr using their Advanced Search feature.
  • DO use images you photographed yourself
  • DO use images from free stock sites like SXC.hu and StockVault.net, BUT make sure you check the agreement for use in files for distribution. Sometimes you need to ask permission from the photographer. We need this because if the image is included in the sample file, we can’t distribute it unless you have permission.
  • IF YOU USE images from a stock site like iStockPhoto, Dreamstime, or other THEN you are free to use the images in your screenshots, but in the source files you need to use a watermark over the image as they do in the previews on their sites. In other words you can purchase a stock image to use, but in the sample file you can’t be distributing the whole image (because the photographer isn’t receiving a royalty from the sale of files).

Please include links to the source of any images you have used in your tutorial wherever it has been used. If you do not include your image sources your tutorial will not be accepted, because we need to verify that the file is OK.

Thank you for taking the time to make sure the photos are OK, it helps protect the site, the photographer and yourself!

Activetuts+ Author/Artist Agreement

If Your Tutorial or Content is Accepted

  • You, the author, can use tutorial/content graphics in any commercial or non-commercial work, except in an online tutorial.
  • You may not redistribute the source files or code outside of Tuts+ and the Envato network, except when the tutorial is based on source files or code that were publicly available before the tutorial was made.
  • You grant a license to readers to use the knowledge and demonstrated effects shown in the tutorial/content in their own projects without reference to yourself, Envato, Tuts+, or this site. They may not reproduce the tutorial itself, but they can use the techniques you teach.
  • You grant a license to Envato to be the exclusive publisher of the tutorial/content online. You may republish extracts online – for example on your own site – however the tutorial in its entirety should not appear elsewhere. You may also republish the tutorial offline in any way you wish – e.g. sell it to a magazine, submit it to a book. However, source files and artwork may not be redistributed elsewhere, as explained above.
  • You consent to the full tutorial, content, extracts, samples or examples from it appearing in other Envato sites, products and services.