Define a Pretty URL within source content - Fluid Topics - Latest

Empower Metadata with Fluid Topics

Category
Technical Notes
Audience
public
Version
Latest

It is possible to manually define a value for the ft:prettyUrl metadata key directly in the source content at the document and topic levels.

When users define pretty URLs manually, Fluid Topics removes the following characters from pretty URLs:

  • Colons (:)
  • Question marks (?)
  • Brackets ([])
  • Percent signs (%)
  • Number signs (#)

Using the previous characters in the value of the ft:prettyUrl metadata key can cause URL conflicts.

Fluid Topics may also remove dots (.) and slashes (/). For instance, for a ft:prettyUrl value of /foo/../bar/.., Fluid Topics creates a foo/bar pretty URL.

When users define pretty URLs manually, Fluid Topics may also percent-encode the following characters in pretty URLs:

  • At signs (@)
  • Dollar signs ($)
  • Ampersands (&)
  • Plus signs (+)
  • Commas (,)
  • Semicolons (;)
  • Equals signs (=)
  • All non-ASCII characters

The resulting pretty URLs may contain encoded characters, which are less legible.

The encoding of characters varies between browsers.