Yes, I was talking about the real life case where I was posting
and the two link previews were the same, making my post look silly.
So I was battling with the (Discourse) interface, trying to figure out a way to disable
all that magic — with no documentation on how to do it.
So it all had to be trial and error…
Then I experimented with
https://www.openstreetmap.org/ .
https://www.openstreetmap.org/edit .
This gives the odd combination of
https://www.openstreetmap.org/ .
OpenStreetMap .
which, yes, has it’s logic, but that’s not my point.
It is still not what I wanted my post to look like to others.
By this time I thought “I will just look at the official documentation instead of hours of trial and error.”
OK, so I looked and looked and found Supported formatting in posts (markdown, BBCode, and HTML) .
OK, that mentioned the
[url]http://bettercallsaul.com[/url]
format, but with
[url]https://www.openstreetmap.org/[/url]
[url]https://www.openstreetmap.org/edit[/url]
something isn’t working:
[url]https://www.openstreetmap.org/[/url]
[url]https://www.openstreetmap.org/edit[/url]
Therefore Supported formatting in posts (markdown, BBCode, and HTML) is probably out of date, etc.
So how did I finally solve my problem, using
[https://www.openstreetmap.org/](https://www.openstreetmap.org/), not
[https://www.openstreetmap.org/edit](https://www.openstreetmap.org/edit)
to get
https://www.openstreetmap.org/, not
https://www.openstreetmap.org/edit
Well, I remembered you guys use “Markdown”, and I remember Markdown had that syntax,
and it worked.
All
I
am
saying
is
there should be an official document somewhere that tells users what will happen when they type this and that character.
They shouldn’t need to read the source code to find out. Thanks.
Fine, put it in a FAQ, then link the FAQ to the interface somewhere.
OK, let’s say you put the future formatting FAQ on the Discourse website. Problem solved…
except how does the user even know he is using Discourse? Yes I am talking about users, not admins. Thanks again.