Getting started with creating Practice Content at DataCamp for the first time, may feel overwhelming at first: what's the process you need to follow, what tools will you use, what are DataCamp's expectations?
To ensure you get a clear answer to all of these questions, the Practice Content Creator on-boarding experience takes you through the following steps:
- understanding the content creation process
- getting to know the tools you will use
- getting to know the communication channels
- understanding DataCamp's expectations
- getting to know where to find support
This article is where your on-boarding experience starts: the sections below refer you to a set of articles containing detailed written text and video's to get you started. Let's dive in!
The content creation process
The Practice content creation process consists of 5 steps:
- creating Practice content,
- testing & soft launch,
- maintenance & hard launch, and
- creating more Practice content.
Once you signed your contract with DataCamp, you enter the on-boarding experience. This crucial step ensures that you are in the perfect position to get started creating your Practice content.
Your on-boarding experience starts with the an email from DataCamp, pointing you to this article. It further includes:
- reading through this article and all referenced support articles,
- completing the on-boarding tasks in your Asana project (more information about Asana below), and
- a kick-off call with your CM to test your understanding of the process and tackle outstanding questions.
To get a good view of what the remaining 4 steps of the Practice content creation process entail, go to this article.
Throughout the content creation process, you will use various tools to manage your work and create content. More specifically, you will use:
- Asana, a project management tool that helps you getting a view of the different steps in the process and the associated due dates,
- Toggl to track the time you spent on each of these steps,
- DataCamp's Teach editor to create content, and
- GitHub to review the feedback on your work.
Get to know each of these tools, and our expectation on how to use them, by going through these articles:
- What is Asana?
- Setting your Asana user name and profile picture
- Tracking your time with Toggl
- DataCamp's Teach editor for Practice
- What is GitHub?
- Link DataCamp & GitHub
How to communicate with DataCamp
Throughout the content creation process you will interact with your CM at various moments, regarding various topics. Depending on the topic, you will use a different channel. Both on GitHub and Asana, remember to always tag your CM using their GitHub or Asana handle; on both platforms you do this by including
@user_name in our message.
Your CM will open a GitHub issue to give you feedback on your content. you, on the other hand, will create a GitHub issue when you have a question our comment about your content. Using GitHub to communicate about your content ensures that all relevant information is available in the repository, even long after your work at DataCamp has been completed. Take a look at this short video on the various issue templates available in your GitHub repository, for you to use.
When you or your CM have a comment or question about a specific task, you will use the dedicated comment field in that Asana task.
When you or your CM have a general comment or remark that is not related to your content or a specific task, you will use the "Conversations" section in your Asana project. You will find this section just below the project name in your Asana project
During your kick-off call, your CM will agree with you on a time slot for a weekly check-in call. This call is scheduled ideally right after your CM has provided feedback on your work for the chapter you have completed at that time. During the call you will discuss that feedback in detail, putting you in the position to implement that feedback efficiently.
Your CM will create a calendar event that includes a link to the Zoom platform which you will use for these weekly check-ins, and share this event with you.
Your Asana project will contain a due date for each task; this is the date by when you should complete this task. As many tasks depend on the completion of a previous task, having dedicated and transparent due dates allows all parties involved to plan their work accordingly. Read through this article to understand what we expect from you regarding task due dates.
We're here to help!
Curriculum Managers each work with a large number of content creators at the same time, so it’s vitally important that the process is a fun one for the content creator and for us at DataCamp.
We encourage you to not be a perfectionist but work hard to produce the best content you can. We’ll provide you with guidance, and we want to see your best work, but please keep in mind that content creation is a very iterative process and takes time and patience.
To ensure you're in the best position to create successful content, even when your CM is offline, we created this elaborate Instructor Support Help Center. Feel free to browse through all articles, you might find some valuable information. However, in additional to all articles reference to here, be sure to take a look at these articles:
- DataCamp dictionary
- Learning objectives
- Become a DataCamp power user
- Sources of data
- Datasets to avoid
- Format text as code
Finally, if there is anything we can do to improve your experience, please let us know, and we'll do our best to correct course.
You can contact us at email@example.com.