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
    @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
    Needed to add the $foundation-palette variable into assets/scss/foundation/_settings.scss at the end of global section but before the @include add-foundation-colors mixin.
    I'm not sure if this is something that happens on a fresh install for everyone or if I just messed something up in the process but if anybody else experiences this I'd be happy to put a PR in to put my fix in.
    Chris
    @core77
    @daneclarkcollins Did you find a solution? I just opened an issue for that.
    Chris
    @core77
    Is someone using the jekyll-foundation package with docker-compose and could provide the docker-compose.yml file?
    Erik Brommers
    @eb1
    @core77 Came across your excellent jekyll-foundation repo the other day. Thanks so much for adding it! I do have a question about deployment, though -- how does one deploy the _site folder to GitHub Pages? I'm not finding rsync info there (maybe I'm not looking in the right location)
    Chris
    @core77
    @eb1 Hi. Im made this to build a site locally on my machine, not on GitHub pages. Though take a look at this fork: https://github.com/kculmback/kculmback.github.io Seems the guy changed some things to use the repo on GitHub pages :-)
    Erik Brommers
    @eb1
    @core77 Awesome -- Thanks! I'll take a look. I was able to manually do it with a couple tweaks to the _config.yml and Gemfile. Hopefully this guy has done a little better job than I had!
    captaincoffee
    @captaincoffee
    Has anyone looked at the upcoming Foundation 6.4 and how it would work with the Flexbox defaults? I assume new templates would be needed.
    kırdinli
    @semih
    hi