Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
Antora
Antora
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 172
    • Issues 172
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 35
    • Merge Requests 35
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Antora
  • AntoraAntora
  • Issues
  • #190

Closed
Open
Opened Mar 05, 2018 by Dan Allen@mojavelinuxOwner

Allow page alias to be an explicit URL pathname

In addition to a page ID, allow the value of a page alias to be an explicit URL pathname. The value must begin with a forward slash (e.g., /path/). For example:

:page-aliases: /path/

This enhancement satisfies the use case of defining a vanity URL for a page. The vanity URL does not have to be expressed using the coordinate system and is therefore not constrained to its structure.

When the value of an alias begins with a forward slash, Antora still creates an alias entry in the content catalog. However, the value is assigned directly to the pub.url property on the content file instead of that property being computed. Antora sets the out.path on the content file so the site responds to the URL when the static redirect facility is in use.

Edited Mar 05, 2018 by Dan Allen
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
TBD
Milestone
TBD
Assign milestone
Time tracking
None
Due date
None
Reference: antora/antora#190