Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rich-text editor: Internal link autocomplete #3714

Open
simonedelmann opened this issue Apr 13, 2022 · 1 comment
Open

Rich-text editor: Internal link autocomplete #3714

simonedelmann opened this issue Apr 13, 2022 · 1 comment

Comments

@simonedelmann
Copy link

Context

I was playing around with ApostropheCMS this morning in order to evaluate if ApostropheCMS could be a good replacement for an old php-based solution I am currently using. (For reference: neos.io) It looks great (Congratulations!), apart from one small detail…

The problem to solve

A highly used feature of my editors is linking pages and anchors (I saw the official anchor extension!) within other pages‘ content. While this is absolutely possible now, it requires them to

  • navigate to the page they want to link
  • copy it‘s url
  • go back to the page where they want to create the link
  • paste the url in the rich-text editors url field.

Proposed solution

It would be great to have some kind of autocomplete suggestions for internal urls in the rich-text editor.

An example: Assuming there is a page „Lorem Ipsum“ at path /foo/bar/lorem-ipsum. When typing „Lor“ in the url field, there should be a clickable suggestion to select that page and paste its url.

Alternatives

There seems to be a similar thing for Apostrophe 2.0 with even more functionality: https://github.com/apostrophecms/apostrophe-rich-text-permalinks Maybe it is possible to port that to 3.0? (Although - just from looking at the screenshots - an autocomplete field seems to be easier to use.)

Additional context

Such an autocomplete for urls could be restricted to pages (+anchors when using that plugin) only or could also work with pieces and maybe even with files. Not sure if this would help or disturb the UX.

@boutell
Copy link
Member

boutell commented Apr 13, 2022

I believe we have some client requests for something like a port of our old support for this, so it's likely to happen in the next year.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants