search

asciidoctor / asciidoctor-extensions-lab

A lab for testing and demonstrating Asciidoctor extensions. Please do not use this code in production. If you want to use one of these extensions in your application, create a new project, import the code, and distribute it as a RubyGem. You can then request to make it a top-level project under the Asciidoctor organization.
Other
104 stars 101 forks source link

"Standard" way to overload assets path #36

Open ggrossetie opened 9 years ago

ggrossetie commented 9 years ago

When using extension(.js) in the chrome extension, assets are stored within the extension package and the URL is chrome-extension://<EXTENSION_ID>/.

I think it would be nice to have a standard way to overload assets path.

ggrossetie commented 9 years ago

Maybe stylesdir will do the trick... I will give it a try

mojavelinux commented 9 years ago

That may work for now, but we should have a more semantic way of doing this. I like assetsdir. This is fairly similar to this issue: https://github.com/asciidoctor/asciidoctor/issues/659

This complements a discussion I had with Andres at JavaLand about having a mediadir that is the root of media elements and then having specific types, like images, use a relative path from there. That would allow images, videos and audio to be in different folders, same as icons are now (except icons are assumed to be under images, which may not be what we want). Clearly, we need to design the behavior that is ideal and work to integrate it into core (maybe for 1.6.0?)