theCrag/website — Issue #385: Allow image embed format in markdown
Author: brendanheywood
Created: 2011-11-14 05:25:29+00:00
State: open

Just noticed Lee McDougall has added a few photos to Wye Creek and referenced them in the markdown:

http://www.thecrag.com/area/11872453

Follow the highway out of Queenstown towards Milford Sound. The entrance is a small gate with a sign. Be sure to close the gate behind you ('Approach1.jpg') Follow the small road up to a grassy area where you can park your car, or if you have a 4WD keep going up to the top, there is space for 2 or 3 cars closer to the track entrance. Once up the top you'll see a sign saying track and toilet ('Approach2.jpg'). Follow these signs and you'll pass a toilet. It's the last one so keep that in mind. (Approach3.jpg') This is the track to all all of the walls at Wye Creek

http://www.thecrag.com/area/11872453/photos

What are your guys thoughts on this? Obviously it's not really going to work well in the difference media, so we need to treat is somehow. I think the simplest thing is as topo's attached to the top node without any routes attached to them.

But semantically it's not really a topo. Or it kinda is, I can argue it either way depending on when we add the ability to add locations to topos and names and paths, this could be a lot better.

But I'm also wondering wether there might be any value in some sort of markdown code to embed any photo into the text? It's a small fringe case, but could be an easy way to add things like FA photos into the history section, approach photos like Lee, perhaps a pic of a sign in the access section.

[image:12345]

And it pulls all the metadata from the image and embeds it. On the backend it would pass through all the metadata similar to what we get in the markdown for refs to linked routes so the client can render it in different way.

Worth it?