Feat: Enable/Disable Landing Page #227
Open
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.
PR: Enable or disable the landing page via configuration
✨ Feature: Toggle for the landing page
This change introduces a new configuration option in
hugo.toml
that allows you to easily enable or disable the landing page. It adds flexibility for environments where a direct redirect to/docs/
is preferred.🔧 Added configuration
Enable landing page (default) No action required. The landing page will be shown as usual.
Disable landing page Set
enabled
tofalse
. Visitors will then be automatically redirected to/docs/
.🛠 Updated logic
The logic in
layouts/index.html
has been updated to check whether the landing page is disabled. Ifenabled = false
, it performs an automatic redirect to/docs/
. Otherwise, the landing page is rendered based on the data indata/landing.yaml
.✅ Changes
landingpage.enabled
parameter tohugo.toml
layouts/index.html
based on this parameter/docs/
if landing page is disabled🔍 Checklist
🎨 Dark mode
🔗 Related Issues and/or Discussions
Issues
Discussions