Sometimes it's easier to replace text from the command line rather than you favourite editor, especially if you want to blanket change configuration settings live on the server.
find /path_to_files -name "*.js" -print | xargs sed -i 's/replacethis/replacewith/g'
Dont forget that forward slashes
/ must be escaped with backslashes
\ in search and replace strings.
One of the best things about Git is the ability to retrieve and view a full history of every commit you’ve made to a project. It’s very powerful as regardless of the direction you take or any future commits you make you’ve always got access to a chronological history of commits.
Sometimes however when presenting, delivering or cloning a project for simplicity and cleanliness you may not want a history of development branches or commits to be visible, showing only the latest version of code.
Whenever you make a http request, you send a request header to the server containing details on what the browser wants and will accept from the server. The server in turn responds with a response header. Apache servers share more information than you may like in your http response headers.
While it's not sensitive information it does by default share your Apache version. This applies to PHP as well.
Grunt is an automation tool powered by NodeJS. It works with plugins and allows you to automate the execution of development tasks such as minification, Sass/LESS to CSS, merging of files and those other repetitive tasks you perform during development.
Earlier versions of grunt came with built in functionality however with recent versions such as the one used here (0.4.1) you will have to install plugins for each individual function you wish to perform.
You may visit websites from time to time where part of the page loads but it doesn’t look quite right or is not styled properly. Then in a split second after more of it has loaded it snaps into the expected form with full styling and looks fine.
Most developers get this right and avoid the problem without knowing why when building a site, then pull hairs out when they can’t figure out why that one page they are building keeps popping when it’s loading.
One of the questions I get asked frequently by developers who visit Yellloh is about how we achieve the beautiful fade-in effect on our images. With design and ease of use being a central focus I wanted to make sure that images fade in gracefully and in a reliable manner with cross browser support. In developing a solution I didn’t want to use external scripts and wanted to keep the solution as small and efficient as possible.
With any page load I wanted each image to fade in as soon as it had finished loading, independent of any other event occurring on the page. This produces the beautiful effect where images fade in independent of each other. The solution I was looking for also had to be compatible with dynamic elements as we are using infinite scroll to add new elements to the DOM and have cross-browser compatibility.