Skip to content

[Site] Add getting-started guides as "Guides" to the web site#3550

Open
snazy wants to merge 1 commit intoapache:mainfrom
snazy:guides-on-site
Open

[Site] Add getting-started guides as "Guides" to the web site#3550
snazy wants to merge 1 commit intoapache:mainfrom
snazy:guides-on-site

Conversation

@snazy
Copy link
Member

@snazy snazy commented Jan 26, 2026

This change follows up on the dev-mailing list discussion and adds the guides under getting-started/ to the web site as "Guides".

  • The guides had to me moved from the getting-started/ folder into the site/content/ folder structure, because symlinks from the site/content/ folder do not work (the contents are not pulled in).
  • Each guide's README.md file has been renamed to index.md, added a front-matter, which instructs Hugo to that also lets Hugo include the guide in the top-level menu.
  • Assets for each guide are listed at the top of each guide, so users do not have to go via GitHub.
  • Links in the guides have been updated.
  • A new layout named guides has been added for this use case.

Two changes on the Ceph guide:

  • updated the misplaced yaml type on a code snippet
  • renamed .env.example to dot-env.example, because files starting with a . are not included

@github-project-automation github-project-automation bot moved this to PRs In Progress in Basic Kanban Board Jan 26, 2026
@snazy snazy force-pushed the guides-on-site branch 4 times, most recently from 2b3a442 to 1aba13e Compare January 30, 2026 17:15
@snazy snazy added the documentation Improvements or additions to documentation, especially web site content label Feb 2, 2026
@snazy snazy marked this pull request as ready for review February 3, 2026 14:00
This change follows up on the [dev-mailing list discussion](https://lists.apache.org/thread/gwxn34nzvhdqdjw2bst6kwlqt8jhb91d) and adds the guides under `getting-started/` to the web site as "Guides".

* The guides had to me moved from the `getting-started/` folder into the `site/content/` folder structure, because symlinks from the `site/content/` _folder_ do not work (the contents are not pulled in).
* Each guide's `README.md` file has been renamed to `index.md`, added a front-matter, which instructs Hugo to that also lets Hugo include the guide in the top-level menu.
* Assets for each guide are listed at the top of each guide, so users do not have to go via GitHub.
* Links in the guides have been updated.
* A new layout named `guides` has been added for this use case.

Two changes on the Ceph guide:
* updated the misplaced `yaml` type on a code snippet
* renamed `.env.example` to `dot-env.example`, because files starting with a `.` are not included
Copy link
Contributor

@dimas-b dimas-b left a comment

Choose a reason for hiding this comment

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

Good idea to host guides on the site 👍


```shell
docker compose -f getting-started/minio/docker-compose.yml up
docker compose -f site/content/guides/minio/docker-compose.yml up
Copy link
Contributor

@dimas-b dimas-b Feb 5, 2026

Choose a reason for hiding this comment

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

Is it worth having "assets" downloadable from the site, when this command assumes running in a local source repo clone?

For example, the docker-compose script refers to ../assets/polaris 🤔

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

Labels

documentation Improvements or additions to documentation, especially web site content

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants