Skip to content
This repository has been archived by the owner on Dec 20, 2017. It is now read-only.

Add support for maven site structure #130

Open
ptillemans opened this issue Dec 12, 2013 · 3 comments
Open

Add support for maven site structure #130

ptillemans opened this issue Dec 12, 2013 · 3 comments

Comments

@ptillemans
Copy link

Maven uses some gothic structure to organize the content which seems optimized to not work with anything.

it structures the files as

src - site -+- markdown
               + ...
               + resources-+- css
                           + js
                           + images

Then when doing mvn site it does it's dark voodoo and everything ends up on another location so the the images folder is now in the site root together with the
docs.

My top gripe is that the images are somewhere far away and there is no decent way
to preview them without corrupting the url's so they won't work on the generated site.

So ti would be nice that the previewer would also look starting from the resources
folder if it does not find a resource in the folder it needs. Or add the resources somewhere the previewer can find them.

I guess that JS and CSS will then automagically work too, but it are the images
which would be the biggest win.

@nicoulaj nicoulaj added Bug and removed Bug labels May 9, 2014
@nicoulaj
Copy link
Owner

nicoulaj commented May 9, 2014

I don't want to put any-Maven specific code in this plugin, otherwise I will end up supporting every framework / build tool / etc, so I'm not sure how to handle this.

@ptillemans
Copy link
Author

As far as I can tell maven is the only one with a strong (and weird)
convention for the site generation. They support the strangest markup
languages, each in a separate folder which then get processed and all
thrown together with some navigation xml.

The biggest problem is images and similar static stuff when redacting
markdown, so a configurable path for looking for static resources would
solve 95% of the use cases

On Friday, May 9, 2014, Julien Nicoulaud [email protected] wrote:

I don't want to put any-Maven specific code in this plugin, otherwise I
will end up supporting every framework / build tool / etc, so I'm not sure
how to handle this.


Reply to this email directly or view it on GitHubhttps://github.com//issues/130#issuecomment-42662954
.

Sent from Gmail Mobile

@nicoulaj
Copy link
Owner

Notice: This plugin is no more maintained and it has been removed from Jetbrains plugins repository. There is a Markdown plugin officially supported by Jetbrains.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants