-
Notifications
You must be signed in to change notification settings - Fork 113
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
Updated ToC for entire ManageIQ + added already existing topics within ToC #1806
Conversation
Added following additional topics to ToC: - Creating a Service in for Virtual Machine Provisioning - Service Provisioning Using an Orchestration Template - Assigning a Custom Analysis Profile to a Virtual Machine
@qasim-ahmed This PR is going to need a bunch of "prior" entries, so that the page detector can understand how the pages were moved around. Basically, the way it works is for each of these "moved" sections, just add a new key called "prior" which is the url for the old location of the file. Here's an example from when we moved one of the locations from morphy to najdorf: https://github.com/ManageIQ/manageiq-documentation/blob/najdorf/_data/site_menu.yml#L42 |
@qasim-ahmed Can you also update the original post here with maybe a screenshot or a manual type-out of the new layout? Also, please update the PR title / commit message to be more descriptive - this is a pretty big change, and the title doesn't really reflect that. |
@qahmed1998 how can I see a before and after? It's hard to visualize what's moving around and being added/removed. I'll add my comments but they're on the existing terminology so mostly unrelated to this PR. |
_data/site_menu.yml
Outdated
- title: Methods Available for Automation | ||
path: "/docs/reference/latest/methods_available_for_automation/index.html" | ||
desc: Advanced automation methods for ManageIQ Management Engine | ||
- title: Scripting Actions in ManageIQ | ||
path: "/docs/reference/latest/scripting_actions/index.html" | ||
desc: "Real-time, bi-directional process integration for ManageIQ Management Engine" |
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.
What's the difference between ManageIQ Management Engine and ManageIQ? I see both terminology here. Do we need to normalize on one term?
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.
FYI @Fryguy
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.
Note, I see this term elsewhere so we can potentially normalize the terms in a followup PR. It's more obvious here since I see both forms of what I think are the same thing.
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.
I bet this used to be CloudForms Management Engine. Probably best to just use "Real-time, bi-directional process integration for ManageIQ"
We can potentially merge and see the ToC? |
I think that defeats the purpose of PR review if we have to merge it to see it, agree with @jrafanie it is hard to review without seeing what has changed easier |
I have posted screenshots above as well. The ss might help! |
_data/site_menu.yml
Outdated
visualizing: | ||
title: Visualizing infrastructure |
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.
Hm I'm not sure "visualizing" is how I'd describe this section. It does include viewing inventory but also e.g. reconfiguring_a_vm_disk.md, refreshing_instances_and_images.md, removing_a_datastore.md, creating_a_vm_snapshot.md, etc...
If anything I'd call this "Inventory" or "Managing Inventory", @Fryguy wdyt?
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.
Oh actually that's what the section used to be called, https://github.com/ManageIQ/manageiq-documentation/pull/1806/files#diff-46686079121737af3636a6d1c95d842fc981118049ec6ece21ce578576eebd50L71
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.
Oh I see, I can make the top level heading Managing inventory
.
The changes in this PR include, adding new top level headings, moving topics from one heading to another and adding topics which existed but were not part of the ToC. The ToC changes that are in this PR currently aligns with the downstream (AIOps) ToC. |
_data/site_menu.yml
Outdated
desc: "How to create a service for virtual machine provisioning" | ||
- title: Assigning a Custom Analysis Profile to a Virtual Machine | ||
path: "/docs/reference/latest/assigning_custom_analysis_profile_to_vm/index.html" | ||
desc: "How to assign custom analysis profile to a virtual machine" |
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.
I don't know that most of these fall under "Administration", I do think administration for backup&restore or something like creating local users but these are all more related to managing inventory IMO.
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.
Good point. I don't know how to word it but one is administration of the application and one is using the application.
Perhaps a high level "using" section with categories...
- Using
- Authentication...
- Automation
- All of the provisioning, service, etc.
- Scripting actions ...
- Policy
- Monitoring, alerts, reporting...
- Policies and Profiles guide
- Manage Infra and Inv.
- Managing Providers...
- Configuration
- Assigning a Custom Analysis Profile...
- Deployment planning guide
- ...
- Administration
- Appliance backup/restore
- installation
- upgrading
...
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.
Note, I would prefer we move things one at a time if we can't have a good visual before/after screenshots. Ideally, each commit changes one thing and the PR changes aren't too much so it's easy to review and get merged. Anything that "feels" like it's a separate change should probably be done in followup PRs so the high level reorganization can go in first.
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.
I can make changes to each big heading (section) in a single commit. With regards to Installing, Upgrading, It will make sense for it to be its own heading and not be under Administration. Administration should contain stuff that can be done by a user once application is installed.
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.
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.
- Provisioning Virtual Machines and Hosts
- Service Provisioning Using an Orchestration Template
- Creating a Service in for Virtual Machine Provisioning
I think they would go in using -> automation
Okay it seems like some items might be in the wrong place there then also so lets put them in the best place upstream first ™️ and go from there |
Yeah sounds good to me. |
NOTE I don't see |
Do you have the URL/path of the file/content? |
Added Podified and Appliance categories for "Installing"
Okay so from our discussions in Slack, this is what we have as updated ToC. Installing Upgrading Using
Administering Infrastructure Management
Defining integrations
APIs
Reference
Troubleshooting (same as it is) |
Any final adjustments or am I good to make this as the ToC in the PR? |
Updated ToC as we discussed. Please review.
|
Hi Joe, I have addressed your comments. |
Checked commits qahmed1998/manageiq-documentation@3079587~...2557ad9 with ruby 3.1.5, rubocop 1.56.3, haml-lint 0.51.0, and yamllint **
|
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.
Looks good to me. It's hard to see the layout in this format but I think all of the concerns have been addressed.
This PR broke the build
|
Should be fixed by #1812 |
Weird it passed in the PR. 😕 |
This PR also "broke" the user reference page - https://github.com/ManageIQ/manageiq.org/blob/master/site/docs/reference/index.md?plain=1 I wonder if instead of hardcoding the sections we can more dynamically build it up. Even so, the |
@qahmed1998 see above |
Added following additional topics to ToC:
This PR is editing the current ToC for ManageIQ. No files in terms of their locations were moved in the process. 3 existing topics (as mentioned above) were added to the ToC.