Jump to content

louisstephens

Members
  • Posts

    512
  • Joined

  • Last visited

Posts posted by louisstephens

  1. I have been avoiding developing this section of our website for a day now as it looks horrendous in my opinion. The general layout of the section is to have our 4 main services with their titles on the left hand side. When you click on one, an entire blocks swings in from the top (animate.css) with the title, brief snippet, cta, and a youtube video "explaining" the service with plenty of buzz words. The entire section is quite tall and the video sticks out like a sore thumb.  I have been racking my brain on perhaps a "better solution", but I am all out of ideas. I was tasked to revamp the site (was on processwire, now in gridsome/graphcms just to try out something new), but the mockup is a bit out of date (just feels old tech for a marketing agency). Thankfully, I have a bit of wiggle room to make changes, as long as I can show something interesting.

    I was just wanting to hear some of your feedback/ideas on how you would go about tackling this section to make it feel a bit more interesting/clean. I have included a very basic "mockup" of the section in question (left = service titles | right = content regarding service => title, snippet, cta, video). The section is also the full width of the browser, so in my dev enviornment atm it is 1825px x 850px.

    section.png

  2. Sure thing! Here you go:

    var gulp = require("gulp");
    var sass = require("gulp-sass");
    var browserSync = require("browser-sync").create();
    var autoprefixer = require("autoprefixer");
    var rename = require("gulp-rename");
    var cssnano = require("cssnano");
    var postcss = require("gulp-postcss");
    var minify = require("gulp-minify");
    //var bourbon = require("bourbon").includePaths;
    //var neat = require("bourbon-neat").includePaths;
    
    // Put this after including our dependencies
    var paths = {
    styles: {
        // By using styles/**/*.sass we're telling gulp to check all folders for any sass file
            src: "./src/scss/*.scss",
        // Compiled files will end up in whichever folder it's found in (partials are not compiled)
            dest: "./dist/css/"
    },php: {
            src: './*.html',
    },
    scripts: {
        src: "./src/js/*.js",
        dest: "./dist/js/"
    }
    
    
    
    // Easily add additional paths
    // ,html: {
    //  src: '...',
    //  dest: '...'
    // }
    };
    
    
    
    
    function style() {
        return gulp
        .src(paths.styles.src)
            .pipe(sass({ outputStyle: "expanded" }))
        .pipe(gulp.dest(paths.styles.dest))
        .pipe(rename({ suffix: ".min" }))
            .pipe(postcss([autoprefixer({ browsers: ['> 1%', 'last 3 versions', 'Firefox >= 20', 'iOS >=7'] }), cssnano()]))
        .pipe(gulp.dest(paths.styles.dest))
        .pipe(browserSync.stream())
    
    
    }
    exports.style = style;
    
    
    function php() {
        return gulp
            .src(paths.php.src)
            .pipe(browserSync.stream())
    }
    exports.php = php;
    
    
    function script() {
        return gulp
        .src(paths.scripts.src)
        .pipe(minify({noSource: true}))
        .pipe(gulp.dest(paths.scripts.dest))
        .pipe(rename({ suffix: ".min" }))
    
    }
    
    exports.script = script;
    
    
    
    
    
    function watch() {
    
    
        browserSync.init({
          // You can tell browserSync to use this directory and serve it as a mini-server
          port: 8181,
            proxy: "http://localhost:8888/project-folder/"
          // If you are already serving your website locally using something like apache
          // You can use the proxy setting to proxy that instead
          // proxy: "yourlocal.dev"
        });
    
    
        //I usually run the compile task when the watch task starts as well
        style();
        script();
    
        gulp.watch(paths.styles.src, style);
        gulp.watch(paths.scripts.src, script);
        gulp.watch(paths.php.src, php);
    
    
    
    
    
    
    }
    exports.watch = watch
    
    

     

    • Like 2
  3. 13 hours ago, OrganizedFellow said:

    I never could get that to work reliably. Never figured out why.

     

    To be honest, it also took me a while to get it all working. Apparently I started using it with an outdated syntax of gulp (1 version behind) and when I went to add some new node modules, everything just blew up in my face. 

    If you are interested, I would be more than happy to share my gulp file with you or anyone.

  4. I use gulp with browser-sync in my current workflow. I really like it as I can specify what files extensions (php, css, etc etc) to watch for changes and once it detects a file change, it automatically reloads the page. I also will be using gulp-cache for cache busting (for changes with my scss/css). So far I have been very happy with the results.

     

    • Like 1
  5. Is the title and menu bar contained within a wrapping div? You could do this for the individual elements, but have you tried bumping up the z-index of the wrapping div or the ind. elements to bring them on top of the background image.

    • Like 1
  6. After a whiIe of not using the module I recently ran into an issue when I reinstalled the hanna code module. I tried uninstalling the module and reinstalling it, but then I run into the issue of:

    SQLSTATE[HY000]: General error: 1813 Tablespace '`revamp`.`hanna_code`' exists.

    I checked the database with adminer and searched for "hanna_code", but I am not seeing any tablespace in the database. Is there a way of clearing this out so I can do a fresh install?

    Also, I was going to use this module to allow people to define the form fields they would like to use in a setup I am currently developing (one per line). For example, they could type in [[form-firstname]] and the output would be:

    <input type="text" name="firstname" id="firstname" required>
    <label for="firstname" class="is-required">First Name</label>

    In my infinite wisdom, I thought I could explode by the line and wrap each input into a column/row. Obviously this doesnt work as the output is actually two lines (and some of my hanna codes would output up to 6 lines). Is there a good way to go about adding in rows/columns to the actual inputs?

  7. I wasn't quite sure where to put this as this not really a firm question but more of a discussion (if this needs to be moved, I do apologize). I am remaking an internal app for work and most of the users log into the admin to create pages etc etc. With the old app, I have noticed a lot of unpublished pages, duplicated pages, abuse of the system (my fault as I didn't do anything to set guidelines of maintenance etc etc) and was wondering how some of you "post" notes for the  user.

    I was going to send out an automated email once I create their user account with all of useful documentation, but I feel that they will either read it once and delete it or just skip right over it. In my mind it would be nice to have a place where this information was always available, but I have a feeling that it would just be ignored after a while. Unfortunately, I dont have the time to watch the backend like a hawk for any wrong doings, but lately the old app has become the unlawful wild wild west (the page tree is getting out of hand).

  8. Unfortunately, I do not believe the pagination has yet made it to repeater fields yet. There was a blog post made in 2016 regarding it, and I believe it is only possible with the Profields Table field atm (though the blog mentions the possibility of adding it in the future). I am sure other items were deemed more important, and pushed repeater pagination down the line. 

    I have read that AJAX loading repeaters might help, though it is the default setting. 

    • Like 1
  9. I actually was working on something similar to import/exporting using the Rest API module here at work. I have a cron job set up targeting a specific page (on the live site) with some jquery checking the api endpoint (local dev server with an external locked ip). I then post that to the targeted page and run some php to update fields on the live site with the content.. It's overkill, but I like it as it allows new content/changes to be uploaded if in case I wasnt able to get to it.

    • Like 1
  10. So I ran into a very strange issue today. I have a template with a pagetable and I went to add an item to it, when I went to select an image (for an image field) the page instantly threw up an error

    "ProcessPageSearchLive: No search specified"

    The page's content also switched to the image attached. This all worked perfectly last week (local mamp box). Has anyone experienced this before, and how did you solve it?

     

    pw-issue.png

  11. I believe the option field is set up as the following: id=name|Title. You are trying to access a Title that doesnt exist, so you would need to add to your existing set up like:

    1=north|North
    2=west|West
    3=south|South
    4=east|East

     

    I was mistaken after rereading the docs (sorry about that). It is set up by id=title by default, but you can add a separate title to the value (my apologies).

    • Like 1
  12. So I ran into a strange error this morning when trying to publish a page. I went to publish a new page under "clients", but I get an error that says "Cannot be published until errors are corrected". I thought perhaps I had missed a required field so I checked, but none of the fields are marked as required. I then checked to see if I could just add a basic page (default basic-page.php template) under the homepage, but I get the exact same error when trying to publish. When looking at the template, I don't see any error messages being displayed above any fields.

    The odd thing I found though was if I got to "settings"  and uncheck "unpublished", I can then publish the page without errors. I did upgrade earlier today to the newest version to hopefully fix an issue I had yesterday (which it did). Has anyone run into this error before? 

    **EDIT**

    Well, after a lot of staring and pulling my hair out, I found the issues. I had installed multi-language support sometime ago (and due to the project changing, had to remove it). Apparently in my haste, I did not remove all the dependencies so it was still trying to check for the multi-language title (I am guessing) even though it actually wasnt on the page. I went through the database and removed it and can now save/publish pages without issues. 

    • Like 2
  13. So I went to revisit a project that I put on hold and was met with the following error when trying to trash a page "Operator '&' is not supported for 'status' in ../wire/core/PageFinder.php: 2211

    else if(!$database->isOperator($operator)) {
       throw new PageFinderSyntaxException("Operator '$operator' is not supported for '$field'.");
    }

    I have searched through my templates just to make sure I didn't do anything screwy, but I have no clue why this error is being generated. I can individually delete an item from the trash, but I cant empty the entire trash. 

×
×
  • Create New...