Skip to content

Update System Requirements#377

Merged
kvaps merged 1 commit intomainfrom
sys-req
Nov 27, 2025
Merged

Update System Requirements#377
kvaps merged 1 commit intomainfrom
sys-req

Conversation

@kvaps
Copy link
Member

@kvaps kvaps commented Nov 27, 2025

Summary by CodeRabbit

  • Style

    • Improved tab and content area styling for better visual presentation on medium and larger viewports.
  • Documentation

    • Restructured hardware requirements with tabbed configuration options (Minimal, Recommended, Optimal).
    • Enhanced guidance with dynamic hardware configuration tables and clearer networking prerequisites.

✏️ Tip: You can customize this high-level summary in your review settings.

Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
@netlify
Copy link

netlify bot commented Nov 27, 2025

Deploy Preview for cozystack ready!

Name Link
🔨 Latest commit 2a423d1
🔍 Latest deploy log https://app.netlify.com/projects/cozystack/deploys/6928317d7a999f0008a61f41
😎 Deploy Preview https://deploy-preview-377--cozystack.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Nov 27, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

The changes introduce SCSS styling overrides for Docsy tabs, restructure hardware requirements documentation with templated tabbed configurations, and add a new Hugo include shortcode for dynamic content templating. These modifications shift documentation from hard-coded specifications to configurable tabbed options with reusable components.

Changes

Cohort / File(s) Summary
SCSS Styling Updates
assets/scss/_override-docsy-tabs.scss, assets/scss/_tabs_alerts.scss, assets/scss/main.scss
Added new SCSS partial to override Docsy's max-width rule for medium+ viewports (992px+) on tab content and list elements; removed border styles from tab panes; imported override partial into main.scss.
Documentation Restructuring
content/en/docs/getting-started/requirements.md, content/en/docs/install/hardware-requirements.md
Replaced hard-coded minimal configurations with templated includes; shifted Hardware Requirements from explicit numeric baselines to dynamic tabbed options; introduced configurable compute, storage, and networking prerequisites.
Hugo Infrastructure
content/en/docs/install/_include/hardware-config-tabs.md, layouts/shortcodes/include.html
Created new include shortcode with file existence checking and conditional rendering (RenderString or markdownify); added tabbed hardware configuration template with Minimal, Recommended, and Optimal tiers.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

  • Include shortcode logic: Verify file path construction, existence checking, and error handling for missing files
  • SCSS overrides: Confirm selector specificity and !important usage don't cause unintended cascading effects with Docsy
  • Documentation template content: Review hardware specification accuracy across Minimal/Recommended/Optimal tabs and ensure consistency with requirements guidance
  • Hugo rendering paths: Test both RenderString and markdownify code paths for templated content

Poem

🐰 Hops with glee through tabbed delight,
Hardware configs now shiny bright,
Shortcodes include what files may be,
SCSS tabs cascade fancy and free!
Documentation hops into place—
Tomorrow's templates embrace this space!

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch sys-req

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f53dcae and 2a423d1.

📒 Files selected for processing (7)
  • assets/scss/_override-docsy-tabs.scss (1 hunks)
  • assets/scss/_tabs_alerts.scss (1 hunks)
  • assets/scss/main.scss (1 hunks)
  • content/en/docs/getting-started/requirements.md (1 hunks)
  • content/en/docs/install/_include/hardware-config-tabs.md (1 hunks)
  • content/en/docs/install/hardware-requirements.md (3 hunks)
  • layouts/shortcodes/include.html (1 hunks)

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

  • Provide your own instructions using the high_level_summary_instructions setting.
  • Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
  • Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

  1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
  2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
  3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
  4. 📊 Contributor Summary — Include a Markdown table showing contributions:
    | Contributor | Lines Added | Lines Removed | Files Changed |
  5. ✔️ Additional Notes — Add any extra reviewer context.
    Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @kvaps, I'm Gemini Code Assist1! 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 aims to modernize and clarify the system requirements documentation by structuring hardware specifications into easily navigable tabs. It also introduces a reusable content inclusion shortcode and applies necessary styling adjustments to seamlessly integrate these new documentation features.

Highlights

  • Enhanced Hardware Requirements Documentation: The system requirements documentation has been significantly improved by introducing a tabbed interface for presenting different hardware configurations (Minimal, Recommended, Optimal).
  • New Content Inclusion Mechanism: A new Hugo shortcode include.html was added, enabling the reuse of content snippets across multiple documentation files.
  • Styling Adjustments for Tabs: New SCSS rules were introduced to override default Docsy tab styling, ensuring the new tabbed content displays correctly and without unwanted borders.
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.

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.

@kvaps kvaps merged commit 2d286d6 into main Nov 27, 2025
4 of 6 checks passed
@kvaps kvaps deleted the sys-req branch November 27, 2025 11:10
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the system requirements documentation by refactoring it to use a shared, tabbed view for different hardware configurations. This is achieved by introducing a new Hugo shortcode for including content, and updating the corresponding markdown and SCSS files. The changes improve the maintainability and readability of the documentation. My review includes suggestions to make a CSS selector more specific to avoid side effects, improve a new Hugo shortcode for better internationalization support, and clean up some minor formatting issues in the markdown files.

Comment on lines +3 to +5
.td-content > ul {
max-width: 100% !important;
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The selector .td-content > ul is quite broad and will apply max-width: 100% to any <ul> that is a direct child of an element with the td-content class. This could have unintended consequences on other lists throughout the site. To avoid this, I recommend using a more specific selector that targets only the tabs navigation, which uses the .nav-tabs class.

Suggested change
.td-content > ul {
max-width: 100% !important;
}
.td-content > ul.nav-tabs {
max-width: 100% !important;
}

Comment on lines +33 to +45
- Any Linux distribution, for example, Ubuntu.<br>
- There are [other installation methods]({{% ref "/docs/install/talos" %}}) which require either any Linux or no OS at all to start.

**Networking:**
- Routable FQDN domain.<br>If you don't have one, you can use [nip.io](https://nip.io/) with dash notation
- Located in the same L2 network segment.
- Anti-spoofing disabled.<br>
It is required for MetalLB, the load balancer used in Cozystack.
- If using virtual machines, there are extra requirements:
- CPU passthrough enabled and CPU model set to `host` in the hypervisor settings.
- Nested virtualization enabled.<br>
Required for virtual machines and tenant kubernetes clusters.

**Virtual machines:**
- CPU passthrough enabled and CPU model set to `host` in the hypervisor settings.
- Nested virtualization enabled.<br>
Required for virtual machines and tenant kubernetes clusters.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

There are a few unnecessary <br> tags in this list which can be removed for cleaner Markdown:

  • On line 33, the <br> is at the end of a list item, right before another list item starts. It should be removed.
  • On lines 39 and 44, the <br> tags are at the end of list items that are followed by an indented paragraph. The line break is automatic here, so the <br> is redundant and should be removed.

@@ -0,0 +1,13 @@
{{- $path := .Get 0 -}}
{{- $filePath := path.Join "content/en" $path -}}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The path to the content directory is hardcoded as content/en. This will cause issues if you add more languages to the site in the future. It's better to construct the path dynamically using the current language to make the shortcode more robust and i18n-friendly.

Suggested change
{{- $filePath := path.Join "content/en" $path -}}
{{- $filePath := path.Join "content" site.Language.Lang $path -}}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant