Update the structure of the Package Registry documentation to make it easier to get started
Problem to solve
Our Package Registry documentation is confusing for new users that are looking to get started using the feature. For example, for the NPM Registry, we step right into package naming conventions and authentication, but do not detail the requirements for getting started, how to verify that they meet those requirements, or even how to build their first package.
Intended users
Further details
Proposal
Follow a similar outline to the newly launched Conan Repository, for NPM, Maven, and NuGet. This new outline makes it much easier to setup the development environment, get started also includes information on how to install packages.
- How to enable the repository
- How to setup and confirm the development environment
- Create a project
- How to build a package
- How to add GitLab as a remote
- How to authenticate
- How to upload a package
- How to find that pakage in the UI
- Notes on naming conventions
- How to install a package hosted in the GitLab repository
- How to delete a package
- How to publish or install a package via CI/CD
- Troubleshooting
Permissions and Security
- There are no permissions changes required for this change