Closed nicholas-haggerty closed 2 years ago
We should discuss this story. There might be other ways of achieving the desired behaviour.
Duplicate of #178?
I can't see this anywhere in the priority list for going live or switching off AEM @nicholas-haggerty @meols cc @pradeepvenurao (It wasn|t suggested in the list from the dev team either btw)
If it is not in the dependent list, we should postpone this.
@nilsml @meols Its on the figjam board. Discussed several times including at the workshop. I believe is also on the PPT overview @pradeepvenurao. Does it absolutely stop us switching off AEM? No. Is it yet another missing component that the editorial will use extensively on pages, Yes. Does it majorly impact on the editorial workflow if not in place. Yes.
This story needs to be split into TOC and anchor link
Do we need support for anchor linking to static pages? That will complicate this issue and require more time for development.
Do we need support for anchor linking to static pages? That will complicate this issue and require more time for development.
This will also complicate things if we make the static link selection more easy/intuitive as discussed in previous meeting. Best would be to limit it to only dynamic pages.
Anchor links that already exist on static pages will continue to work (if linking to other static pages or to content on the same page). No guarantees that existing anchor links on static page will continue to work if the page they link to has been converted to a dynamic page in Sanity.
For discussion: Currently the anchor link component can be utilized for in page navigation. Does this fit as part of this user story?
Currently AEM fails from a UX perspective as there are various ways to solve inpage navigation. We need a clear definition of how it should appear and behave.
Best example: https://www.iea.org/fuels-and-technologies/renewables (appears/hides on scroll)