Ndj support cloud merge demo

[ndjones]

got it building, trying for a preview

[github-actions]

Test deployment available at https://callumwalley.github.io/mkdocs-demo-deploy/nesi/support-docs/ndj-support-cloud-merge-demo

Seems the following pages differ;

• index
• 20230918-essential-building-blocks-v0.9
• 20231205-research-developer-cloud-updates-and-fixes-v0.10
• 20240205-research-developer-cloud-updates-v0.11
• summary
• index
• security-policy
• building-eff-rsp
• index
• summary
• shared-responsibility
• summary
• terms
• summary
• creating-and-managing-application-credentials-via-cli
• creating-and-managing-application-credentials-with-the-dashboard
• index
• summary
• create-and-manage-keypairs-via-cli
• create-and-manage-keypairs-with-the-dashboard
• index
• summary
• create-and-manage-network-ports-via-cli
• create-and-manage-network-ports-with-the-dashboard
• create-and-manage-networks-via-cli
• create-and-manage-networks-with-the-dashboard
• index
• manage-floating-ips-via-cli
• manage-floating-ips-via-the-dashboard
• manage-security-groups-via-cli
• manage-security-groups-with-the-dashboard
• summary
• create-and-manage-object-storage-via-cli
• create-and-manage-object-storage-with-the-dashboard
• creating-and-managing-ec2-credentials-via-cli
• index
• summary
• using-boto3-to-interact-with-object-storage
• using-cyberduck-to-interact-with-object-storage
• create-and-manage-volumes-via-cli
• create-and-manage-volumes-with-the-dashboard
• format-and-mount-volumes
• index
• summary
• index
• connect-to-instance-ssh
• default-user-nesi-images
• deployment-of-an-instance-with-terraform
• index
• launch-an-instance-from-a-volume
• launch-an-instance-from-an-image
• launch-an-instance-via-cli
• launch-an-instance-via-dashboard
• manage-security-groups-of-an-Instance-via-the-cli
• manage-security-groups-of-an-Instance-via-the-dashboard
• resizing-an-Instance-via-cli
• resizing-an-Instance-via-the-dashboard
• summary
• index
• summary
• converting_image-types
• image-filter
• index
• managing-images-via-cli
• managing-images-via-the-dashboard
• summary
• upload-an-image-via-cli
• upload-an-image-via-the-dashboard

See all deployed demo sites

[ndjones]

@CallumWalley @lbrick here's a demo of the two support sites integrated through a top menu.

https://callumwalley.github.io/mkdocs-demo-deploy/nesi/support-docs/ndj-support-cloud-merge-demo/

I've kept the changes minimal, in line with what we discussed a few months ago @CallumWalley - hopefully with where we landed on that conversation this is what you were expecting it would look like. something else has changed in the way the menu is expanded by default, I'm not quite sure why though - just noticed that difference in behaviour, i'm assuming it can be made to collapse by default.

Changes are to:

• navigation settings in mkdocs.yml and to
• sections and pages in .pages.yml, along with
• importing the res dev cloud content into a new folders docs/research_developer_cloud.

To do:

• nav for the new cloud section hasn't been customised, so isn't in the right display order.
• check all links work as expected
• collapse section menu by default

[CallumWalley]

Nav order is fixed in nesi/research-developer-cloud#39
Should probably rebase against that as it changes quite a lot.

[CallumWalley]

@ndjones Can you elaborate on the motivation behind this?
There would be some drawbacks to merging and i'm not clear to what end.

[ndjones]

key goal is to bring NeSI support into one place through an integrated information architecture. currently it is fragmented, and various aspects are somewhat hidden. this is to have one place to go for anything related to docs for NeSI.

would be useful to understand the drawbacks - the intent is for user experience for existing users to not change, other than they might discover something on the research cloud of interest. it would be good to understand any potential drawbacks, so they can be factored into any design work to see if they can be mitigated..

[CallumWalley]

@ndjones Did you want to pull in nesi/research-developer-cloud#39 or should I?
Needs to be done before merging in #345