Files restructure

[CallumWalley]

As discussed in meeting.

Main 'File Systems and Quotas' page needs good read over as I just pasted bits of Geoffs page over it.

[gemini-code-assist]

Summary of Changes

Hello @CallumWalley, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request streamlines and enhances the documentation for storage systems and best practices. It consolidates related information into fewer, more comprehensive files, improves navigation, and standardizes how users are directed to support resources. The changes aim to make storage-related information more accessible and coherent for users.

Highlights

• Documentation Restructuring: Significant reorganization of storage-related documentation, including renaming and moving several files to a flatter directory structure within docs/Storage.
• Content Consolidation: Information from Storage_best_practices.md and Data_Compression.md has been integrated into the new Filesystems_and_Quotas.md document, creating a more comprehensive resource.
• Navigation Updates: The primary navigation file (docs/Storage/.pages.yml) has been updated to reflect the new file paths and include newly introduced documents.
• Standardized Support Links: Direct mailto: links for support requests have been replaced with a reusable {% include "partials/support_request.html" %} partial for consistency across the documentation.
• Removal of Cloud Storage Section: The dedicated Cloud_Storage documentation and its navigation entry have been removed, streamlining the storage options presented.
• New Offsite Storage Guide: A new document, Offsite_Storage_Options.md, has been added to provide guidance on external data storage solutions.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

---

Files moved, paths now new, Docs align, clear for all to view. Storage wisdom, fresh and true.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[github-actions]

Test deployment available at https://callumwalley.github.io/mkdocs-demo-deploy/nesi/support-docs/files-restructure

Seems the following pages differ;

• Automatic_cleaning_of_nobackup
• Research_Developer_Cloud_Storage
• Data_Recovery
• Data_Compression
• Filesystems_and_Quotas
• File_permissions_and_groups
• Filesystems_and_Quotas
• Offsite_Storage_Options
• Storage_best_practices

See all deployed demo sites