Open okigan opened 12 years ago
So you are saying there are markdown editors that let you place image files inside the text, but they reference only the child directories of the markdown file? Can you give me an example of this product or workflow? thanks!
http://markdownpad.com/ -- great editor (IMHO)
mostly it is the {{urls.media}} that would break it, but I still propose to allow/default image files to be
in the same directory as
This allows for simple granularity of pages, particularly in projects.
another editor that I use, from visual studio, that also would benefit/affected from this issue: http://visualstudiogallery.msdn.microsoft.com/0855e23e-4c4c-4c82-8b39-24ab5c5a7f79/
bump -- i think this is most important issue
@plusjade, i got a rough draft update for the compiler (i can push that to my fork), and need some help with the previewer component
ok send it over :)
Have a look at: https://github.com/okigan/ruhoh.rb/commit/4fa719f91821e7914b98c5848a6ec79285cfbe09
Draft ! allow static media (png, jpg, zip!) files local in project pages issues:
key files:
+1 this would also be useful for music tracks or image galleries. then the folder that contains the track/gallery would be more self contained if all the associated media (audio for tracks, images for galleries, etc.) was embedded. IMHO even better would be having the ability to have a media
collection within a collection/folder, so we could still use all the cool media collection features (fingerprinting, dynamic URLs, etc.). an example would be:
album/
tracks/
track-01/
index.html
media/
cover.png
audio.ogg
track-02/
index.html
media/
cover.png
audio.ogg
track-03/
index.html
media/
cover.png
audio.ogg
references to media within that page would first refer to the local page's media folder then cascade outward as usual with ruhoh.
peace, w
To keep things simple propose to allow png files in pages subdirectory.
This simplifies editing and allows to use of the shelf markdown editors. But currently that's impossible as ruhoh forces png files to be placed in top level media directory.
It's nice to think about CDN compatibility, though it seems that should be done at compilation step, rather than forcing at content creation.