Comments on: Why You Should Build a Front End Package

By: ブランクプロジェクトフォルダで効率アップ | CSS Radar

ブランクプロジェクトフォルダで効率アップ | CSS Radar — Sun, 24 Oct 2010 04:51:33 +0000

[...] Why You Should Build a Front End Package | Design Shack [...]

By: elmalak

elmalak — Sat, 12 Jun 2010 12:58:48 +0000

the idea seems cool to me especially as I am used to the same concept in creating WordPress themes.
I prefer to use blank starter themes instead of creating all files from scratch.

I agree it does save time and effort and provide consistency in work.

By: Mes favoris du 20-02-10 au 21-02-10 » Gilles Toubiana

Mes favoris du 20-02-10 au 21-02-10 » Gilles Toubiana — Sun, 21 Feb 2010 14:25:08 +0000

[...] Why You Should Build a Front End Package | Design Shack [...]

By: Blendia » Blog Archive » Why You Should Build a Front End Package

Blendia » Blog Archive » Why You Should Build a Front End Package — Thu, 18 Feb 2010 21:59:03 +0000

[...] aqui. No [...]

By: James Waugh

James Waugh — Wed, 17 Feb 2010 02:32:06 +0000

I’m already working with something very similar to what you describe here – but picked up some very useful tips to add to my approach. Thanks, and Well done!

By: All Teched Up!! « Caintech.co.uk

All Teched Up!! « Caintech.co.uk — Mon, 15 Feb 2010 18:53:15 +0000

[...] Why You Should Build a Front End Package Design Shack [...]

By: Bjarne // Mums Studio

Bjarne // Mums Studio — Mon, 15 Feb 2010 18:25:41 +0000

Thought of this like 100 times. Never done enything about it! Now it’s in Things on my “Today” list. Meaning I’ll make this “starter-kit” tomorrow…

Thanks for pointing it out! :)

Cheers

By: rorschach design

rorschach design — Mon, 15 Feb 2010 16:45:20 +0000

Enjoyed the article a lot. I’m a new designer and I’ve thought about doing something like this before, but after reading the reasons as to why designers use a pre built system, I realize I HAVE to do it, if I want to focus on the important things…the job at hand.

By: Pontus Johansson

Pontus Johansson — Mon, 15 Feb 2010 13:19:05 +0000

To be honest, I thought everyone did this. At least to some extent.

By: Stephen Fairbanks

Stephen Fairbanks — Mon, 15 Feb 2010 11:59:45 +0000

This is very useful article, it’s amazing how much stress and headaches can be resolved by putting in place a simple package that keeps everyone working on a project on the same page.

By: ModeTen Designs

ModeTen Designs — Mon, 15 Feb 2010 11:10:12 +0000

The concept is solid and logical – as many above have said – been using it for a while. The main use here is for larger agencies and projects where people change frequently, or multiple team run the same job. Smaller agencies and projects will probably need a lighter set of rules!

By: Bruno Monteiro

Bruno Monteiro — Mon, 15 Feb 2010 10:58:18 +0000

Already working with my own Frontend Package. It doesnt differ from this one. Actually i’ve updated/improved my own with some elements of this one ;) Got mine in “Portuguese”. Big thx, great post!

By: Kamil Kaniuk (Merix Studio)

Kamil Kaniuk (Merix Studio) — Mon, 15 Feb 2010 10:16:40 +0000

So true! We have built our own model too to make xhtml/css coding even more cost-effective.

By: Russell Bishop

Russell Bishop — Mon, 15 Feb 2010 09:56:46 +0000

You raise some excellent points in regards to the reasoning behind such a framework. We’ve been using a similar model for a few months now, and it’s made the whole development process radically smoother.

We’re always adding and editing it, to further streamline the processes we’re carrying out during construction.

My only issue is the name you have for it! “Front End Package” is not a term I want to be using in the office, we’ve opted for “The Box” instead.

By: Federica Sibella

Federica Sibella — Mon, 15 Feb 2010 09:50:47 +0000

Very easy and really useful, everything at a glance, I do something like that (like “deliverables” and “useful stuff”), but not so standardised. I’ll give it a try, thanks!