As a Live Training focuses on hands on coding activity, the environment you choose will be where you and your learners spend most of the session. These are the requirements for a DataCamp Live Training:
Free to Access
- Learners should not have to purchase an outside subscription or sign up for a "free trial" to be able to attend the session. For example: Getting Started in Tableau required access to the free Tableau Public service, and did not require learners to purchase Tableau
- Many Live Training Sessions will use Google Colab notebooks. These require a gmail account to access
- Note: Excel courses strongly suggest having access to Microsoft Excel, but learners may be able to follow along in Google Sheets
Easy to Set Up
- Learners will be sent a link at the start of the session, either to the coding environment, or to download a file
- Unless the training is dedicated to learning how to set up an environment, setting up the coding environment should take a minimal amount of time
- You can ask learners to create an account with a free open source software such as Tableau Public before the session is held, but be aware that not all attendees may have actually done so
Whichever technology you use, you should prepare a solution file that only you should have, and an empty file that you fill out in the session alongside learners. We will refer to these files as 'notebooks', but they may also refer to an Excel or Tableau workbook as well.
- A full solution notebook that you will rely on throughout the session and share with students only after the session is complete. Your solution notebook must have the naming convention session_name_solution.ipynb.
- A session notebook for you and learners to fill out throughout the session that has the naming convention session_name.ipynb.
We encourage you to develop the solution notebook first so that your Content Developer can support you in developing the best possible live training session.
You can find instructions on how to get started authoring your notebook in the final section of the README file of your GitHub repository.
If you do not see a solution that supports your technology and topic of choice, reach out to your Content Developer as soon as possible to discuss alternative solutions.
In order to empower learners to follow you at a reasonable pace, enable re-usability, and ensure the best possible content and user experience, here's a few guidelines to follow.