You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Feature request #1279: Set up "l" or "s" as shortcut path for "links" controller

Kind feature request
Product wincent.dev
When Created , updated
Status closed
Reporter Greg Hurrell
Tags no tags

Description

One of the purposes of the "links" controller is to enable the creation of convenient shortcut links that redirect to hard-to-remember or cumbersome-to-type URLs both inside and outside the site.

For example, just say we had an wiki article called "How to file a good bug report", it would be painful to have to type "see [[How to file a good bug report]]" all the time when one could instead type "see [/links/bugs this]".

To make it even more convenient to use the short links, it would be nice to set up "l" as an even shorter route to the controller, so the above example would be just "see [/l/bugs this]".

Admittedly, when you're writing entries within the app it's not that hard to do the full links, but when you're not in the app but you still want to refer to specific pages (for example, when you're writing an email) it could be a real godsend to be able to write stuff like "see https://wincent.dev/l/bugs" instead of "see https://wincent.dev/wiki/How_to_file_a_good_bug_report".

Comments

  1. Greg Hurrell

    Summary changed:

    • From: Set up "l" as shortcut path for "links" controller
    • To: Set up "l" or "s" as shortcut path for "links" controller
  2. Greg Hurrell

    As noted in the new summary line, instead of "l" for "link", could also consider using "s" for "shortcut" as the abbreviated route for the controller. I actually used the "s" namespace for this purpose on the old site, so I have a bit of muscle and brain memory established for that shortcut already.

  3. Greg Hurrell

    Status changed:

    • From: New
    • To: Open
  4. Greg Hurrell

    Ok, now implemented. In the end went with "l" for "link" rather than "s" for "shortcut".

  5. Greg Hurrell

    Status changed:

    • From: Open
    • To: Closed
Add a comment

Comments are now closed for this issue.

Menu