Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Chris
    @core77
    :+1:
    Chris
    @core77
    OMG, the javascript gulp task takes 17 seconds! Definitely too much.
    Chris
    @core77
    ...when running 'npm run build' (production build)
    captaincoffee
    @captaincoffee
    Today I get an error when starting gulp. "No gulpfile found" I an pretty inexperienced and have no idea where to start. I am running from your initial commit.
    Chris
    @core77
    @captaincoffee Is the gulpfile.js in the project folder?
    captaincoffee
    @captaincoffee
    The gulpfile was there. I backed up, and went thru the install again. Bundle install seemed to do the trick. Is this the typical fix?
    captaincoffee
    @captaincoffee
    Where/how should custom .js files be added to the project so that they do not get overwritten on updates?
    Chris
    @core77
    Bundler is for Ruby gem dependencies, Gulp is Node.js based... But always a good idea to check dependencies.
    You can put custom js files into /assets/js/. Don't forget to include them in the gulpfile.js
    captaincoffee
    @captaincoffee
    I went thru the install steps as in the readme. It may have been a cache or server restart issue that made bundler seem the answer when in fact it was a previous step. Thanks.
    John Egan
    @grizfan
    Hi - First, thanks for putting this together. As someone who still as a lot to learn, this has helped a lot. But, I am having a problem with the Kitchen Sink page. for the most part, nothing is functioning. It looks like the CSS is applying, but tooltips, accordian menus, Orbit, etc… don’t actually function. Orbit in particular looks broken, with all slide states spilling on to the page at once. No errors in Chrome Dev Tools console. I’m running on OS X 10.11.4, and I just downloaded jekyll-foundation from Github yesterday. If I can provide any more information, please let me know. thanks!
    Chris
    @core77
    @grizfan go to gulp/config.yml and uncomment all the js entries for the foundation components in javascript.src. Then uncomment all the sass includes for the components in assets/scss/foundation/_foundation.scss. Rerun 'npm start'. After that all the stuff on the kitchen sink page should work. Tell me,if it doesn't!
    John Egan
    @grizfan
    @core77 - on closer inspection, this looks to be an issue specific to Chrome Canary Version 50.0.2655.0 canary (64-bit). So, something about this nightly build fails. Works like a champ in Firefox and Safari, so I’ll chalk it up to some sort of Chrome Canary bug. I submitted a defect to the Chrome team, just in case. Any way, thanks for the work you’ve done, and thanks for the support!
    Leo Merkel
    @Lego2012
    @core77: First of all tnx for the great work. Very much appreciated. Are you going to implement Foundation 6.2 soon which just came out?
    Chris
    @core77
    Hi Leo, the package is 6.2 ready since yesterday. With Babel - totally new for me!
    Leo Merkel
    @Lego2012
    Cool, that's awesome, Thomas. No experience with Babel on my side too yet. When will the Repo being updated? Regards from Germany.
    Oh, just realized that you did that already! Tnx a lot - just found the commit message...
    Leo Merkel
    @Lego2012
    Works like a charm!
    Chris
    @core77
    Nice :-)
    Leo Merkel
    @Lego2012
    I found a little mistake: The Tooltip is not showing due to "tabindex=1". Foundation Website says that the number has to be in quotes. Once you write tabindex="1" it works. Hope this helps.
    Leo Merkel
    @Lego2012
    Just opened a Pull Request on Github Repo for this issue
    captaincoffee
    @captaincoffee
    Bower should handle the 6.2 update. How do you handle things like variable name changes, additions, and deletions? New setting files?
    Chris
    @core77
    @Lego2012 Thanks for the PR!
    Chris
    @core77
    @captaincoffee What do you mean exactly? Sass variables?
    captaincoffee
    @captaincoffee
    A number of the variables have changed per https://github.com/zurb/foundation-sites/wiki/Upgrading-to-Foundation-6.2 These may not be significant on a single version update, but I feel like I'm being left behind.
    Chris
    @core77
    @captaincoffee I use the settings file as described from James Stone: If you have watched my Sass + Foundation Screencast then you will know that my preferred method is to duplicate the commented out lines, then uncomment the duplicate and change your settings. That way you can always go back to the defaults if you make a mistake and it is clear what changes you made. See https://www.jamesstone.com/blog/the-five-secrets-of-sass-foundation/
    captaincoffee
    @captaincoffee
    Thanks for the link. Learned some new things.
    Grant
    @grantmoran
    hello all, I just came across this project on jekylltalk and am very excited to begin using it. However I am running into a problem I can't seem to find a good starting point to trouble shoot. Everything seems to work correctly until I uncomment Individual Foundation components (JS) in the gulp config.yml. When uncomment any of them and restart I hit the following error "
    stream.js:74
    throw er; // Unhandled stream error in pipe.
    ^
    Error: ENOENT: no such file or directory, stat '.../_site/assets/css/app.css'
    at Error (native)"
    Any thoughts on what I should look into? Thanks :)
    Chris
    @core77
    @GrantMoran I stumbled upon this error, too. For me CMD + C and a restart with 'npm start' did the job. Perhaps you want to try running 'gulp' instead. If that doesn't fix it for you, please open an issue to track this ...
    Grant
    @grantmoran
    @core77 I have had success intermittently with restarts working, however still have it fail most of the time when running both "npm start" as well as "gulp". I've added an issue on the repo in which I've included the error and two npm debug logs from different versions of node. I have no idea what to do past my attempt to ensure node is up to date. Thanks again for your efforts, have learned a lot already from this build setup.
    Jimmy Chen
    @TechFounder
    I see that Rebekah in Jan had the same issue that I'm having now. I'm getting the same error message that it can't find the '../../vendor/foundation-sites/scss/foundation' Except, she didn't say exactly the steps to take to make it work. She mentioned something about .bowerrc but what am I suppose to change there?
    What's the proper directory?
    { "directory": "bower_components" }
    Jimmy Chen
    @TechFounder
    am I suppose to delete that .bowerrc in the bower_components/foundation-sites folder and put it in the root with { "directory": "assets/vendor" }?
    Jimmy Chen
    @TechFounder
    ok, i got it to work by deleting the bower_component folder, adding a .bowerrc in the root with { "directory": "assets/vendor" } in it. Then deleting the bower_component folder and re-running bower install.
    The question is why did it install a bower_component folder and put all the assets there to begin with?
    Is there a bug that's causing this?
    Also, I'm now getting [BABEL] Note: The code generator has deoptimised the styling of "/Users/jeykll_blog/assets/vendor/jquery/dist/jquery.js" as it exceeds the max of "100KB"
    What is that?
    Jimmy99
    @Jimmy99
    Just need a bit of guidance with jekyll-foundation: When using Jekyll I just enter jekyll new my-awesome-site.
    With jekyll-foundation what is the equivalent command? Do I have to clone the project from github every time?
    Chris
    @core77
    Yeah. Git clone repoURL mynewproject
    Chris
    @core77
    Does anyone know a better way to do that?
    Jimmy99
    @Jimmy99
    That works so well I don't think it is possible to improve on that. brilliant
    daneclarkcollins
    @daneclarkcollins

    I have a feeling I'm going to feel stupid when I figure this out. I've used Foundation on plenty of sites, but on this one, for some reason, if I change the $primary-color (or any other color) in _settings.scss, it remains the same default blue/grey/etc. If I move the settings file down the page on foundation.scss, I can get my custom css (in theme.scss) to show my edited value, but still not the links, buttons, etc.

    No errors.

    I should note that if I change other values in _settings.scss, like font sizes, those changes take effect.

    Any ideas?

    Jimmy Chen
    @TechFounder
    ok, i have a simple question. does jekyll-foundation actually work on github pages? The more I dig into your library, the more it looks like it can't do that simple thing? Is it just for deploying to your own server? If you can actually easily deploy to github pages, how do you do it?
    Chris
    @core77
    As mentioned in the Readme file, it's made to build the site on your local machine and yes, to deploy it to your own server.
    Brandon Shallenberger
    @Bshally

    After a fresh install following the docs here on the repo I have uncommented all of the foundation components and js as needed. On npm start I receive the following error :

    Error in plugin 'sass'
    Message:
        assets/scss/foundation/_settings.scss
    Error: File to import not found or unreadable: util/util
           Parent style sheet: /Users/bshallenberger/Desktop/Project-HQ/jsimp/assets/scss/foundation/_settings.scss
            on line 42 of assets/scss/foundation/_settings.scss
    >>  @import 'util/util';
       -^

    After searching the foundation issues and stack overflow I've found that I need to include the path to the bower components foundation files in the gulp sass plugin . Following zurb/foundation-sites#8293 I added changed the lines starting on line 13 in the sass.js gulp task file to:

    return gulp.src(config.src)
        .pipe($.sourcemaps.init())
        .pipe($.sass({
            includePaths: 'assets/vendor/foundation-sites/scss'
        })
          .on('error', $.sass.logError))
        .pipe(autoprefixer(config.compatibility))

    This fixes the initial error but results in the following:

    Error in plugin 'sass'
    Message:
        assets/vendor/foundation-sites/scss/util/_color.scss
    Error: Undefined variable: "$foundation-palette".
            on line 45 of assets/vendor/foundation-sites/scss/util/_color.scss
    >>   @if map-has-key($foundation-palette, primary) {
       ------------------^

    I feel if I continue to move things around I may just be duplicating the foundation files between vendor and scss, which would seem to defeat the purpose of this build process. This leads me to think I may have something else wrong here but I can't nail it down. Anybody have this problem with the current version or able to point me in the right direction?

    Brandon Shallenberger
    @Bshally
    Seems like I found the issue after looking a bit further. zurb/foundation-sites#8253