Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Paths are incorrect, when custom styleguide path is provided #191

Open
VaclovasV opened this issue Jul 26, 2016 · 3 comments
Open

Paths are incorrect, when custom styleguide path is provided #191

VaclovasV opened this issue Jul 26, 2016 · 3 comments

Comments

@VaclovasV
Copy link
Contributor

image
As we talked, when custom styleguide path is provided, paths are incorrect in this case.
We should make same paths for styleguide web and back-end parts, now they are interpreted differently.
styleguide index.html should be considered as a root.

@shainanigans
Copy link

Glad to see that I'm not the only one having this problem. Anyone found a fix for this?

@AshleyJBartlett
Copy link

AshleyJBartlett commented Aug 19, 2016

Is anyone having issues where you haven't included your styleguide folder in the root of the project? I have included mine as project/wwwRoot/styleguide and I'm having issues with styleguide finding the files it needs when the server is using wwwRoot as the root folder. Actually, I think I'm having the same issue as #145 so I'll post in there.

@0xs
Copy link

0xs commented Oct 15, 2016

I'm a bit late to the party but you can probably get around the problem by editing your gulpfile.js like this:

var styleguide = require('devbridge-styleguide');

gulp.task('start-styleguide', function () {
    styleguide.startServer({
        styleguidePath: 'public/styleguide'
    });
});

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

No branches or pull requests

4 participants