-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Create AWX docsite with RST content #14328
Conversation
looks like the api checks failed with this:
Would it be too much to patch that indentation up in the file? If not, it can be added to the yamllint exclude list. |
Thanks! Should be fixed now. It's great to have ci tests catching formatting issues with the content etc. |
Ready to take this out of draft status? |
@AlanCoding Hello. Sorry for the slight delay here, I've been on PTO. @tvo318 has gone through all the content and added several commits and I think we're ready to go. We're looking at a few last relics in the images but should have that sorted out here shortly. Let the reviews commence! Thanks! |
@tvo318 Thanks for the awesome work to port the content over! I think we're pretty much ready to go. I added a couple of commits to remove a few relic images that were downstream specific. I also dropped some unused insights images. Please take a look. I guess we could prune more stale images but I'd rather do that in a follow up PR. As long as it's appropriate to hand over to the community it should be fine. One other thing I think we might want to address are some of the lurking instances of "controller" and "tower". For example, on these lines you can see controller is mentioned. Should these change to AWX?
Also for the REST API should we
|
@tvo318 One other that I haven't checked yet. Does |
I tried to build this with
I wanted to ask if you could help me figure out that error. It looks like it's at the "api_start" point. |
hey @AlanCoding yes it looks like there's a problem with a Sphinx ref from this commit: ea46505#diff-2a3bdf96e33ef2c6f65306a401b9874e7b7a1acdd7af9ea124deee3b040a26afR170 The fix is to modify that to use the Thanks for catching this. After we get this merged I'd like to add a step to CI to verify the docs build so we can get PR checks for this stuff too. |
Nice one @tvo318 I've removed the old theme and static content. They're no longer needed with the Ansible community theme! I guess we still need to figure out translations but we can do that when we set things up on Read The Docs. We don't need those translation strings in the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We understand that there's still some things to iterate on, but everyone is excited about getting this content and the build system in.
Remaining tower references to keep or revisit later (unsure of AWX equivalent):
|
Thanks @tvo318 I forgot that the api reference (api_ref.rst) was pulling in some assets from the static folder but we can restore them - and make sure they're all good for the community docs - when we add in the swagger generation step. |
Removed all of introductory text and graphic from User Interface section except for the include from the configure_awx.rst file.
Replaced text with new text from operator-docs.
Remaining controller references to keep or revisit later (unsure of AWX equivalent):
|
Co-authored-by: Thanhnguyet Vo <tvo@ansible.com> Co-authored-by: TVo <thavo@redhat.com>
Co-authored-by: Thanhnguyet Vo <tvo@ansible.com> Co-authored-by: TVo <thavo@redhat.com>
SUMMARY
This PR adds AWX documentation in RST source migrated from the private
ansible/product-docs
repository.This is currently a work in progress. The following items must be completed before final review/merge:
ISSUE TYPE
COMPONENT NAME
AWX VERSION
N/A
ADDITIONAL INFORMATION
N/A