-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add landing page for Galaxy project #267
Comments
@tvo318 should this be in the galaxy_ng repo itself for where the docs live? I'm not sure what the docsite pages can do to help out here. |
@samccann - do you happen to know why the galaxy_ng doesn't have an issues bucket? Should it just go into ansible/galaxy? |
Galaxy_ng uses JIRA only. All other requests go to the forum. I think there's a link on top of galaxy.ansible.com for where to post on the forum for help. |
I think this issue is OK in this repo, honestly. At least for the effort of capturing / defining whatever the journeys are for Galaxy NG. We could put them here: https://github.com/ansible/docsite/tree/main/data/journeys My thinking is we could extend the journeys from the docsite into Galaxy NG. Then we can develop some kind of prototype before going to the forum. That way it's not just seen as an abstract thought that adds noise. I get that it would be better to do this in the galaxy repo but I don't see a sensible place for that to happen. Anyway it does seem like it's premature for the forum. If we can put some work around the rough idea it will get more traction and engagement. |
Problem Statement: The current Galaxy documentation is organized in a way that causes confusion for readers since it does not distinguish between Galaxy as a server and Galaxy as a collection.
The Galaxy project documentation site would benefit from a landing page that allows users to select a scenario that best fits their use case so they are guided to the correct documentation. This would improve usability and encourage more contribution from the community.
Some helpful references:
The text was updated successfully, but these errors were encountered: