Update sites/handbook/source/handbook/people-group/learning-and-development/level-up/index.html.md

Why is this change being made?

As more team members begin to build their own learning content in the site, we want to protect against internal content accidentally being published so it is visible for external users. Previously, just clicking Release would publish the content externally, which might seem like an intuitive step but isn't needed for publishing content internally.

We've now added the requirement to Tag content as Public for it to appear in the catalogue, as well as it being released. This means if a user designing internal content clicks Release thinking it would publish their content, it wouldn't immediately show up in the public facing catalogue.

It will also help with filtering / managing content in the admin panel.

Author Checklist

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
• If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

---