Skip to main content

Publishing process overview

Most initiatives for external users will be published by the Learn team, but you are a key stakeholder in that process.

YOUR CHARTER

All charters: required

Learn team sign-off​

When you have completed your final checklist and submitted your initiative, it will be reviewed by your learning experience designer (LXD) and any other approving Unity Learn stakeholder to confirm that it is ready for publishing. This is separate from your own sign-off process for the learning experience with any approving stakeholders in your team.

If your LXD confirms that the learning experience is ready, it will be passed on to the Learn Content Production team, who will schedule it for publishing (sometimes referred to as staging).

If the LXD finds any issues with your submission, one of two things will happen:

  • If the issue is minor but will have a notable user experience impact, your LXD will notify you and offer you the opportunity to make adjustments before the learning experience is staged. Acting on this feedback is optional, but we strongly that recommend you consider it to ensure that we maintain a users first approach to quality on Unity Learn.
  • If the issue is major, your LXD will notify you and tell you the critical changes or pending content required before your learning experience can be published.

Our standard publishing process​

When your learning experience is approved to be published, you'll be provided with an estimated publish date. If you have hard deadlines associated with your learning experience, please discuss them with your LXD and any supporting production stakeholders for Unity Learn as early as possible. Good notice means that we can plan our work and resources effectively, and will help you to avoid the disappointment of us being unable to commit to a required deadline at short notice.

Our Learning Content Production team will publish most learning experiences for external users. The team may have questions or identify minor content issues that have not yet been flagged (for example, missing alt text or an external link which is no longer available). If you receive a tagged comment from your LXD or a member of the production team, please follow up as soon as possible to avoid impacting the timeline for publishing your learning experience.

Self-publishing on Unity Learn​

If your initiative is for internal users, or you have made a specific agreement with the Learn team, you may be responsible for publishing your learning experience on Unity Learn. The self-publishing approach will have been agreed in the initial stages of project planning, to ensure that your designated publisher is granted the correct account permissions for Unity Learn.