I changed the way I work. In the design phase of a website now use a new tool that has revolutionized my usual tasks: Hammer.
I know I always advocate that we adopt tools that are well adapted to our processes but in this case worth making small adjustments to benefit from this application.
What does hammer?
Hammer helps you write HTML more efficiently by allowing you to include parts of code that can be reused. Bring functionality include PHP to HTML.
You can make a file containing the code for the header, for example, and include it in the pages of the site you are designing.
If you have multiple pages created and you have to make any changes in the header you only have to change the file that contains that piece of code and updated throughout.
Photoshop comes up short when it comes to showing responsive designs with the need to show how responsive design responsive to different screen sizes graphics editors such as Photoshop become obsolete. The static image of the sketch no longer serves the client see how it will look your site. This is where it becomes vital resource use that allows you to quickly generate a model living project and Hammer can be your best ally.
This allows you to create your own initial file structure, your own framework and reuse it in each new place that you started.
I have my index file and a series of folders and files with distinct parts of code that help me get everything better structured. Each time you save a file Hammer gathers them, compile and generate all the files ready for upload to production in a folder Build within the project.
Keep your project organized is simple and can create your own templates so that when you launch a new web Hammer believes your file structure.
What tasks have had to modify
Using Sass and love is not that I have been forced to change my way of working with CSS but I’ve been completely and Sass. Not quite convince me that writing pseudo-CSS which had subsequently compile applications but now that Hammer put it so easy I have been stepping up and have to say I’m delighted.
I have all the separate style files in a folder: reset, clear fix, overall layout, typography, forms, styles … Everything sections in place. Every time I keep some change Hammer gathers them and generates a single CSS file for use in production. And it optimizes and minimizes it!
And much more
If you have not yet gone off to buy it, you must know that makes a lot more:
- Gives you the ability to use variables. You can assign the title of the site to a variable and change the variable file for each project
- updates the browser every time you save a change, it is as if he had reached the AVE to the world of web design Adelaide, you will go much faster with this little detail
- has smart routes , i.e., magic: write the name of the file you want to include and what looks Hammer and generates the correct path
What about Codekit
I arrived at Hammer after trying Codekit. Codekit another application is quite similar to Hammer. Besides Sass compiles less, which Hammer does as SASS use this point I do not care.
Codekit another advantage is that it has more options file optimization.
With Codekit you can import your frameworks so that if you do an include of a file it will look first to the specific project you’re working and, if not found, will cross your frameworks to include it.
I tried both applications almost simultaneously and at first I liked Codekit. I did not relish that Hammer generate all files in a folder within the project Build, Codekit compiles each file in the path you indicate you. Finally I’ve used and it seems neater to have all generated files in one place. In fact has been the most solid structure Hammer that has convinced me to use this application. Both cost almost the same and have trial versions. It is best that you take a look yourself and you choose.