Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-36940

Anchor syntax is so difficult to use, our users cannot use anchors

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.

      There has been much said about how difficult anchors are to use, because of the esoteric syntax (see the comments in the Anchors page), especially as it relates to anchors linking to target pages different from the source page ... or, say, sending a colleague an email with a URL anchor link to your page.

      The syntax often recommended by Atlassian tech writers is:
      http://myconfluence.com/display/spacekey/pagename#pagename-anchorname

      ...but there are problems/bugs with this syntax:

      • this breaks for pages that begin with a number (e.g., the very commonly used "2015-04-04 Meeting Notes" naming convention) ... in actuality, you need to use the "id-" prefix after the hash symbol, if the page name begins with a number
      • the #pagename-anchorname part of that syntax actually needs to be #pagenameWithSpacesRemoved-anchorname; which is poorly documented, poorly understood by most users, and leaves the anchor link susceptible to broken links if the page is subsequently renamed
      • the syntax is so convoluted, that anchors are unusable for our users, making anchors not a collaborative gadget tool, but a gadget only for developers or Confluence administrators.

            [CONFCLOUD-36940] Anchor syntax is so difficult to use, our users cannot use anchors

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3427418 ] New: JAC Suggestion Workflow 3 [ 3607623 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 2249828 ] New: JAC Suggestion Workflow [ 3427418 ]
            Status Original: Needs Verification [ 10004 ] New: Gathering Interest [ 11772 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 - TEMP [ 2145814 ] New: Confluence Workflow - Public Facing v3 [ 2249828 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 1900784 ] New: Confluence Workflow - Public Facing v3 - TEMP [ 2145814 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v2 [ 1789740 ] New: Confluence Workflow - Public Facing v3 [ 1900784 ]
            jonah (Inactive) made changes -
            Description Original: There has been much said about how difficult anchors are to use, because of the esoteric syntax (see the comments in the [Anchors page|https://confluence.atlassian.com/display/DOC/Working+with+Anchors]), especially as it relates to anchors linking to target pages different from the source page ... or, say, sending a colleague an email with a URL anchor link to your page.

            The syntax often recommended by Atlassian tech writers is:
            {{http://myconfluence.com/display/spacekey/pagename#pagename-anchorname}}

            ...but there are problems/bugs with this syntax:
            * this breaks for pages that begin with a number (e.g., the very commonly used "2015-04-04 Meeting Notes" naming convention) ... in actuality, you need to use the "id-" prefix after the hash symbol, if the page name begins with a number
            * the *#pagename-anchorname* part of that syntax actually needs to be *#pagenameWithSpacesRemoved-anchorname*; which is poorly documented, poorly understood by most users, and leaves the anchor link susceptible to broken links if the page is subsequently renamed
            * the syntax is so convoluted, that anchors are unusable for our users, making anchors not a collaborative gadget tool, but a gadget only for developers or Confluence administrators.
            New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *Confluence Cloud*. Using *Confluence Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFSERVER-36940].
              {panel}

            There has been much said about how difficult anchors are to use, because of the esoteric syntax (see the comments in the [Anchors page|https://confluence.atlassian.com/display/DOC/Working+with+Anchors]), especially as it relates to anchors linking to target pages different from the source page ... or, say, sending a colleague an email with a URL anchor link to your page.

            The syntax often recommended by Atlassian tech writers is:
            {{http://myconfluence.com/display/spacekey/pagename#pagename-anchorname}}

            ...but there are problems/bugs with this syntax:
            * this breaks for pages that begin with a number (e.g., the very commonly used "2015-04-04 Meeting Notes" naming convention) ... in actuality, you need to use the "id-" prefix after the hash symbol, if the page name begins with a number
            * the *#pagename-anchorname* part of that syntax actually needs to be *#pagenameWithSpacesRemoved-anchorname*; which is poorly documented, poorly understood by most users, and leaves the anchor link susceptible to broken links if the page is subsequently renamed
            * the syntax is so convoluted, that anchors are unusable for our users, making anchors not a collaborative gadget tool, but a gadget only for developers or Confluence administrators.
            jonah (Inactive) made changes -
            Link New: This issue is related to CONFSERVER-36940 [ CONFSERVER-36940 ]
            vkharisma made changes -
            Project Import New: Sat Apr 01 14:06:06 UTC 2017 [ 1491055566265 ]
            Katherine Yabut made changes -
            Katherine Yabut made changes -

              Unassigned Unassigned
              8898dd70d397 Raymond Santangelo
              Votes:
              11 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: