Skip to content

Conversation

@daxelrod
Copy link

One of the use-cases for reading the manifest docs is
wanting to contribute a new package.

Add a link to the create command, which automates
many of the steps of writing the manifest and contributing
it.

One of the use-cases for reading the manifest docs is
wanting to contribute a new package.

Add a link to the `create` command, which automates
many of the steps of writing the manifest and contributing
it.

All available packages are hosted in our official [GitHub Repository](https://github.com/appget/appget.packages). You can review and propose changes to any of the manifests using a pull-request.

To create a new manifest and propose its addition to the repository, use the [`create` command](/commands/#create).
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This path structure should work on https://docs.appget.net/ but won't work correctly when browsing this repo locally. I'm open to other ideas for how to construct this path.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you leave off the leading slash, it's supposed to work as a relative path, I think?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leaving off the trailing slash is another option that works on docs.appget.net but not when browsing the repo locally, since manifests is a directory. There may not be a link scheme that works in both, but I was highlighting this because I don't know that the intended style in this repo is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants