Update home page links#629
Draft
John15321 wants to merge 21 commits into
Draft
Conversation
Signed-off-by: thisisobate <obasiuche62@gmail.com>
Signed-off-by: thisisobate <obasiuche62@gmail.com>
Signed-off-by: thisisobate <obasiuche62@gmail.com>
Signed-off-by: thisisobate <obasiuche62@gmail.com>
…ndex The restructure of the docs site re-created the section index at the new path (content/docs/latest/deploy/virt-options/_index.md) using the listing as it existed before main's recent changes. Apply main's edits — drop Rackspace, add OracleCloud — to the new index so it stays consistent with the rest of the site. Signed-off-by: Jan Bronicki <janbronicki@gmail.com>
…rtualization platforms - Create new documentation for running Flatcar Container Linux on OpenStack. - Create new documentation for running Flatcar Container Linux on QEMU. - Create new documentation for running Flatcar Container Linux on Vagrant. - Create new documentation for running Flatcar Container Linux on VirtualBox. - Remove outdated virtual machines index documentation. Signed-off-by: Jan Bronicki <janbronicki@gmail.com>
Add documentation for deploying Flatcar Container Linux on various virtualization platforms
Signed-off-by: Seth McEvoy <mcevoy.jobs@gmail.com>
Signed-off-by: Seth McEvoy <mcevoy.jobs@gmail.com>
Signed-off-by: Seth McEvoy <mcevoy.jobs@gmail.com>
Signed-off-by: Seth McEvoy <mcevoy.jobs@gmail.com>
Signed-off-by: Seth McEvoy <mcevoy.jobs@gmail.com>
Signed-off-by: Seth McEvoy <mcevoy.jobs@gmail.com>
Signed-off-by: Seth McEvoy <mcevoy.jobs@gmail.com>
Signed-off-by: Seth McEvoy <mcevoy.jobs@gmail.com>
Signed-off-by: Seth McEvoy <mcevoy.jobs@gmail.com>
Signed-off-by: Seth McEvoy <mcevoy.jobs@gmail.com>
Signed-off-by: Seth McEvoy <mcevoy.jobs@gmail.com>
Signed-off-by: Seth McEvoy <mcevoy.jobs@gmail.com>
Signed-off-by: Seth McEvoy <mcevoy.jobs@gmail.com>
This was referenced Jun 30, 2026
Member
Author
|
Hey @mcevoy-building7, as we discussed on Discord. All of these home page link PRs (#617–#626, #628) have been consolidated into #629 on top of |
John15321
commented
Jun 30, 2026
Signed-off-by: Jan Bronicki <janbronicki@microsoft.com>
There was a problem hiding this comment.
Pull request overview
This PR relocates “legacy” home page link groups into the relevant documentation section landing pages (_index.md) so users find topic-specific links within the corresponding section overviews rather than only on the docs landing page.
Changes:
- Added short “overview + link list” content to multiple section landing pages.
- Reorganized the Virtualization Options landing page content to include a dedicated virtualization options list.
- Added new link lists for updates/releases, security, orchestration, storage, diagnostics, deployment targets, and developer guides.
Reviewed changes
Copilot reviewed 11 out of 11 changed files in this pull request and generated 11 comments.
Show a summary per file
| File | Description |
|---|---|
| content/docs/latest/updates-releases/_index.md | Adds an updates/releases link list to the section landing page. |
| content/docs/latest/security/_index.md | Adds a security link list to the section landing page. |
| content/docs/latest/os-config/storage/_index.md | Adds a storage link list to the section landing page. |
| content/docs/latest/orchestrate/clusters/_index.md | Adds a clusters link list to the section landing page. |
| content/docs/latest/orchestrate/_index.md | Adds container runtime/orchestration guidance links to the section landing page. |
| content/docs/latest/fb-provision/customize-image/_index.md | Adds image customization technique links to the section landing page. |
| content/docs/latest/diagnostics/_index.md | Adds diagnostics/debugging links to the section landing page. |
| content/docs/latest/devguide/_index.md | Adds an “APIs and troubleshooting” link group to the developer guide landing page. |
| content/docs/latest/deploy/virt-options/_index.md | Refactors content and adds a virtualization options list to the virtualization landing page. |
| content/docs/latest/deploy/cloud/_index.md | Adds a cloud providers list to the cloud landing page. |
| content/docs/latest/deploy/bare-metal/_index.md | Adds a bare-metal installation methods list to the bare-metal landing page. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+17
to
+21
| Manage releases and updates with these techniques: | ||
|
|
||
| * [Switching release channels][release-channels] | ||
| * [Configuring the update strategy][update-strategies] | ||
| * [Flatcar update configuration specification][update-conf] |
Comment on lines
+8
to
+12
| See these technologies for Flatcar security options: | ||
|
|
||
| * [Setting up LUKS disk encryption][luks-encryption] | ||
| * [Customizing the SSH daemon][ssh-daemon] | ||
| * [Configuring SSSD on Flatcar Container Linux][sssd-container-linux] |
Comment on lines
+11
to
+15
| Manage storage systems with these technologies: | ||
|
|
||
| * [Using RAID for the root filesystem][filesystem-placement] | ||
| * [Adding disk space][disk-space] | ||
| * [Mounting storage][mounting-storage] |
Comment on lines
+13
to
+17
| Manage clusters with these technologies: | ||
|
|
||
| * [Cluster architectures][cluster-architectures] | ||
| * [Clustering machines][clustering-machines] | ||
| * [Using Amazon EC2 Container Service][ec2-container-service] |
Comment on lines
+8
to
+14
| Flatcar Container Linux supports all of the popular methods for running | ||
| containers, and you can choose to interact with the containers at a | ||
| low-level, or use a higher level orchestration framework. Listed below are | ||
| some guides to help you choose and make use of the different runtimes. | ||
|
|
||
| * [Getting started with Docker][docker] | ||
| * [Customizing Docker][customizing-docker] |
Comment on lines
+11
to
+15
| Use the following tools to diagnose and debug Flatcar: | ||
|
|
||
| * [Install debugging tools][debugging-tools] | ||
| * [Working with btrfs][btrfs] | ||
| * [Reading the system log][system-log] |
Comment on lines
+23
to
33
| ### APIs and troubleshooting guides for working with Flatcar Container Linux. | ||
|
|
||
| * [Developer guides][developer-guides]: Comprehensive guides on developing for Flatcar, working with the SDK, and on building and extending OS images. | ||
| * [Integrations][integrations] | ||
| * [Migrating from cloud-config to Container Linux Config][migrating-from-cloud-config] | ||
| * [Flatcar Supply Chain Security (SLSA and SPDX SBOM)][supply-chain-security] detailing security mechanisms employed at build / release time as well as at run-time to ensure validity of inputs processed and outputs shipped. | ||
|
|
||
|
|
||
|
|
||
| [sdk-tips]: sdk-tips-and-tricks | ||
| [disk-layout]: sdk-disk-partitions |
Comment on lines
+27
to
+35
| ## Flatcar provides the following Virtualization Options: | ||
|
|
||
| * [QEMU][qemu] | ||
| * [libVirt][libvirt] | ||
| * [VirtualBox][virtualbox] (community support) | ||
| * [Vagrant][vagrant] (community support) | ||
| * [Hyper-V][hyper-v] (community support) | ||
| * [KubeVirt][kubevirt] (community support) | ||
| * [Proxmox VE][proxmoxve] (community support) |
Comment on lines
+12
to
+18
| ### Cloud Providers | ||
|
|
||
| Flatcar runs on these Cloud Providers: | ||
|
|
||
| * [Amazon EC2][ec2] | ||
| * [Microsoft Azure][azure] | ||
| * [Google Compute Engine][gce] |
Comment on lines
+10
to
+20
| You can install Flatcar on bare metal machines in different ways: using ISO | ||
| images, booting from PXE or iPXE, and even by running an installation | ||
| script on an existing Linux system. | ||
|
|
||
| * [Installing from ISO images][boot-iso] | ||
| * [Booting with PXE][pxe] | ||
| * [Booting with iPXE][ipxe] | ||
| * [Installing with flatcar-install][install-to-disk] | ||
| * [ Raspberry Pi 4][running-flatcar-container-linux-on-raspberry-Pi-4] | ||
|
|
||
|
No newline at end of file |
Collaborator
|
Thanks Jan - This PR targets several overview pages (_index.md) including the ones targeted by PR 613 (AI scaffolding for top overviews). After clearing out AI clutter, my PR address the intro part of the file while I've noticed that a lot of this PR would be additional links to those pages. So I will copy the additional links (previous home page links) in this PR into the _index.md files in 613 - mostly to the lower part of those pages. Then we should merge 613, and then remove those mutual overviews from this PR - those are: Overviews touched by this PR and 613, and all applicable links included: devguide/_index.md |
Collaborator
Collaborator
2 tasks
Collaborator
|
This PR is will be closed as updates have been incorporated into PR 613 |
John15321
force-pushed
the
expert-support-refactor
branch
from
8ef1eee to
409e44e
Compare
Collaborator
|
@John15321 - All updates in this PR were written into files for PR 613. I suggest closing with unmerged commits. |
John15321
force-pushed
the
expert-support-refactor
branch
from
b4e3147 to
2eed592
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Relocates the legacy home page link groups into the section overviews
under the new docs IA, so users find these links where the rest of the
topic already lives instead of on the landing page.
Each group is moved in its own commit, in the same order as the section
list, so the diff can be reviewed one section at a time. No content
rewrites — links and minor surrounding edits only.