Opened on 01/19/2017 at 11:04:31 AM
Closed on 01/30/2018 at 07:05:58 PM
#4824 closed change (rejected)
Add deeplinking capability to the pages
| Reported by: | saroyanm | Assignee: | |
|---|---|---|---|
| Priority: | P5 | Milestone: | help.eyeo.com 1.1.0 |
| Module: | Websites | Keywords: | |
| Cc: | juliandoucette, jeen, wspee, ire | Blocked By: | |
| Blocking: | Platform: | Unknown / Cross platform | |
| Ready: | no | Confidential: | no |
| Tester: | Unknown | Verified working: | no |
| Review URL(s): | |||
Description
Background
In website projects we noticed that often we do need to have deeplinking capabilities the way it's explained here(ex.: on FAQ pages).
What to change
Implement deeplinking capability similar way as what AnchorJS is doing as a part of website defaults.
Attachments (0)
Change History (10)
comment:1 Changed on 01/19/2017 at 11:05:02 AM by saroyanm
comment:2 Changed on 02/13/2017 at 09:20:22 PM by juliandoucette
- Blocking 4606 removed
- Ready set
Let's include this in the next release of website-defaults.
comment:3 Changed on 02/13/2017 at 09:24:08 PM by juliandoucette
- Cc jeen added
- Component changed from Unknown to Websites
- Priority changed from Unknown to P2
comment:4 Changed on 02/16/2017 at 01:26:55 PM by juliandoucette
- Milestone set to acceptableads.com/committee 160301
comment:5 Changed on 02/16/2017 at 01:27:11 PM by juliandoucette
- Milestone acceptableads.com/committee 160301 deleted
comment:6 Changed on 04/25/2017 at 01:03:09 PM by juliandoucette
- Cc wspee added
- Milestone set to help.eyeo.com 1.1.0
- Priority changed from P2 to P3
This will be important for help center later.
comment:7 follow-up: ↓ 8 Changed on 07/31/2017 at 10:00:24 AM by ire
- Cc ire added
I wonder if this is something that can/should be added via the cms. Assuming that we decide on how we want the styling to be, sitescripts can automatically add this to headings we specify individually, or all headings within a certain element (e.g. a .content element for example). The ID for the headings can also be automatically applied based on either the actual heading text, or the translation identifier since that will be unique.
comment:8 in reply to: ↑ 7 Changed on 08/02/2017 at 08:20:04 AM by wspee
Replying to ire:
I wonder if this is something that can/should be added via the cms. Assuming that we decide on how we want the styling to be, sitescripts can automatically add this to headings we specify individually, or all headings within a certain element (e.g. a .content element for example). The ID for the headings can also be automatically applied based on either the actual heading text, or the translation identifier since that will be unique.
FWIW I like how it's done on github. The id is generated out of the heading text and when you hover the heading an icon with the link appears. Bitbucket prepends an a string to the id generated from the heading (#markdown-header-ID-BASED-ON-HEADING-TEXT) which I cannot remember and because they don't have the "hover icon" feature it's always a hassle to link to subsection of document on bitbucket. Of course all this applies to writing specs but it might still be relevant for our cms.
comment:9 Changed on 09/04/2017 at 05:14:34 PM by juliandoucette
- Priority changed from P3 to P5
- Ready unset
comment:10 Changed on 01/30/2018 at 07:05:58 PM by juliandoucette
- Resolution set to rejected
- Status changed from new to closed
I agree that this is a nice-to-have feature for the CMS. I will reject this ticket and create a separate CMS ticket as needed.
@Julian please let me know if the Description is fine with you, so I'll mark this as ready.