Sorry, we don't support your browser.  Install a modern browser

The browser URL should be the shareable URL.#422

Hopefully this makes sense and hasn’t been proposed already. I think this would be a useful UX improvement. First, for this scenario, let’s assume that anyone with access to the wiki shareable link counts as a viewer and I am the owner of the wiki.

I would like to be able to copy the BROWSER url (e.g., https://youneedawiki.com/app/page/...) and give it to a random person. Right now, if that random person opens the link, it asks them to login.

Instead, I think it should bring them to the wiki page I’m viewing as if I gave them the share link. They will see header buttons similar to the ones that already exist (see attached), but also a login and/or edit button that, when clicked, takes them to the destination described in the previous paragraph (the one that asks them to login).

I think this kills multiple birds with one stone:

  1. It’s analogous to the way Google docs works. With Google docs, I can copy the URL and give it to somebody and it functions like my proposal.
  2. It reduces the surface area for human error: the way ynaw currently works, I almost always give somebody the wrong link first, mainly because I’m used to the Google Docs UI. I only realize my mistake when someone informs me of it, and if our schedule has little overlap, this can waste hours.
  3. It reduces user interactions to share a page: I don’t have to click on that share button, click on the share link, and copy it (3 interactions). Now I just need to click on my browser address and copy it (2 interactions).
  4. Similarly, it’s confusing to both me and the person I gave the link to when they tell me I gave them a login page. That will no longer happen unless the permissions of that page say it should; instead of confusing me (and them), it’ll tell me exactly what mistake I made.
  5. As far as I can tell, there’s no way to link to an anchor/header/section in the middle of a wiki page. This provides a straightforward UI to implement this feature. If I click on a anchor/header/section on a https://youneedawiki.com/app/page/... page, it already updates the URL
2 years ago

Thank you for the detailed write up. I agree this is problem from a UX perspective and something that we need to fix.

I have this on the backlog, I will forward this to our project manager to review and see if we can get it scheduled.

In terms of linking to a header or section. This is currently possible when done from the doc, but not currently in the wiki UI.

I’ve added a doc here to show how:
https://docs.youneedawiki.com/app/page/14owfMCatMLdX0qrj1l79SS8xGDZ1MAN8fJ1lyI7JPzY?p=1NqCSiMuEfPfaHTumR_rX6J8zo7ygjx8q

I would also like to see this be possible from the wiki UI.

2 years ago
1

Thanks for talking to your project manager about this, because to be honest, this is the only issue that’s come up for me, but it comes up often.

In terms of linking to a header or section. This is currently possible when done from the doc, but not currently in the wiki UI.

Hmm. Maybe I missed it, but I couldn’t find how this was addressing the functionality I was looking for (at least not directly). We may be talking about different things. I’ll articulate this like a bug report (though I don’t believe this is a bug, just a feature request):

  1. Open https://docs.youneedawiki.com/app/page/14owfMCatMLdX0qrj1l79SS8xGDZ1MAN8fJ1lyI7JPzY?p=1NqCSiMuEfPfaHTumR_rX6J8zo7ygjx8q
  2. Click on “This link will scroll to the bottom heading, click to try it out!”
  3. The browser will jump to a lower part of the page

Expected: There is a way I can give somebody a link that opens up to that part of the page
Actual: I can’t find any way to give somebody a link that opens to that part, only ways to link to the top.

For me, I want to do this often because each of my pages has a table of contents and I want to direct readers’ attention to a specific section.

2 years ago

I’ve pushed an update that fixes this the header linking for youneedawiki.com wikis, an additional update is required for custom domains (including the docs website). I’ll follow up when that’s done.

2 years ago

I intend to use this format

I don’t think I have enough context to give feedback on that, if that’s what you’re looking for. Is that with the browser address would change to? As the child ID a link to the anchor like a # in a URL?

If you’re not looking for feedback at this time, feel free to ignore my questions.

Thanks again for working on this.

a year ago