[QUOTE=KmartSqrl;26494630]Capistrano uses git, they're not mutually exclusive. Capistrano is for deployment, git is for version control. Apples and Oranges.
If it's on your local machine it's not your production environment unless you're also running a web server off your machine that is serving the sites you are designing. (particularly in reference to the filemaw mention, as your explanation of that is the exact opposite of a production environment :P)[/QUOTE]
I manage to deploy just fine using Git to be honest, so I really couldn't care less for your opinions.
My car rolls across the ground just fine on these oval wheels so I don't care if you are suggesting I use round wheels instead.
[QUOTE=KmartSqrl;26500644]My car rolls across the ground just fine on these oval wheels so I don't care if you are suggesting I use round wheels instead.[/QUOTE]
Except that's a fucking terrible analogy. Firstly because Git to Capistrano is nothing like oval wheels to circular wheels, and secondly Git or Capistrano (and the use of each) is entirely personal preference. My method isn't causing any inconvenience at all to anybody at all, except maybe you because you're a pretentious prick who believes that it's 'my way or highway'.
Let me do it how I want to do it. It works, and I don't care for your methods. Got that?
You're tolerable when you're not discussing your opinion on something. Granted, your designs are great, and you know what you're doing. As soon as you get involved in a debate however, you begin to remind me very strongly of Nullsquared.
[QUOTE=Qombat;26494443]
I already answered this. My 'production environment' is basically my desktop, but with a few fictional user/file db entries in Filemaw's case.[/QUOTE]
So I'm guessing filemaw.com is your development or staging environment then?
[QUOTE=KmartSqrl;26490879]You really should[b]n't[/b] have your production environment set as the remote for your git repo though. Your repo should be separate and your production environment should be pulling from that git repo, not running directly from it.[/QUOTE]
I read this wrong and argued about it. Rate boxes, boxes everywhere.
[editline]5th December 2010[/editline]
To clarify, I read "shouldn't" as "should", assumed he meant 'development' and just used 'production' in place of it, and argued about it.
[QUOTE=Qombat;26501209]Except that's a fucking terrible analogy. Firstly because Git to Capistrano is nothing like oval wheels to circular wheels[/QUOTE]
When they're being used for deployment yes. I guess a better analogy would be "my car rolls fine with these metal wheels so why do I need tires?". Git being the metal wheels and capistrano being the tires. Yes, git can work for deployment, but capistrano builds on that and brings a lot of other benefits to the table.
[QUOTE=Qombat;26501209]and secondly Git or Capistrano (and the use of each) is entirely personal preference. My method isn't causing any inconvenience at all to anybody at all, except maybe you because you're a pretentious prick who believes that it's 'my way or highway'.[/QUOTE]
Your problem here is that you're taking it as a personal attack every time I disagree with you. I'd love for you to point out where I said it was an inconvenience to anyone. I'm simply presenting more powerful alternatives. If you were sitting around programming in assembly when you could be using C++ or C# or something instead wouldn't you want someone to let you know? (Obviously this example is excluding cases where you'd actually benefit from using assembly)
Photoshop -> Code it.
1. open photoshop
2. design
3. show team
success!
[QUOTE=ifaux;26512920]1. open photoshop
2. design
3. show team
success![/QUOTE]
what if you run on Linux??
[QUOTE=smidge146;26513081]what if you run on Linux??[/QUOTE]
1. boot on your windows partition
2. open photoshop
3. design
4. show team
success!
[QUOTE=smidge146;26513081]what if you run on Linux??[/QUOTE]
Be a pimp, use GIMP.
[QUOTE=smidge146;26447190]Do you use photoshop to create a site, I find it hard to make a snazzy looking website like [URL]http://tutsplus.com/[/URL] I'm a premium member there and all they seem to talk about it using photoshop to create a nice looking site, where as I code all of my stuff and here is the shit I come up with [URL="http://www.Dareforstuff.co.uk"]www.Dareforstuff.co.uk[/URL] and [URL="http://www.Elliottcoe.com"]www.Elliottcoe.com[/URL].[/QUOTE]
To be honest, your websites look like most websites that originate in a text editor/browser do, and highlight the reasons you shouldn't leap straight into markup and CSS. Design is visual; writing markup and CSS isn't the most intuitive way to lay out a design. Design isn't easy, and its importance is often under-appreciated, and in the realms of the web, it's easily confused with other disciplines (such as front end web development - which constitutes of writing the markup/css to convert a .psd screen comp into a web page). The main thing is, design requires a different approach to development.
A lot of the time - but not always - people specialize in either design or development. For example, I specialise in design and front end development. It's important to distinguish the two, because they can be considered separate specialties, and while I believe that web designers should be at least moderately familiar with front end development (since they're designing for the web after all), there are people who design webpages in Photoshop, and pass the comp on to someone else to convert into a live web page. As such, people who are good at design, front end development and back end development are highly valuable and versatile (and I envy them :saddowns:).
Anyway, that got a bit tangential. [b]The main thing I'm trying to say is to consider markup and css (front end development) separate from design, and recognize both require different approaches[/b]. Now you seem to have a solid understanding of html and css, which means you can now focus on sharpening up your design skill set.
You don't necessarily need Photoshop to design a website; it's just a tool and there are alternative tools, and ultimately, all the prettiest (and trendiest) Photoshop layer styles and filters in the world won't save your design if you don't have any design sensibilities. Design is more than decoration; successful designs communicate efficiently, and the ability to do that isn't dependent on the image editing program you use - that's where design principles come in. While you don't need Photoshop, you'll need to find a similarly powerful image editor. I'm not particularly familiar with Linux programs, I know there's Inkscape, a vector graphics editor, and then there's the venerable Gimp, which I personally can't stand using next to Photoshop.
Unfortunately, in a lot of computer-related creative fields, Adobe reigns supreme, there's really no escaping it. Adobe Photoshop, Illustrator and Fireworks are all great programs for web design, amongst other things. Whilst its fine to use alternative programs as a freelance, if you ever go for a job at a web design agency, experience with Photoshop is probably expected.
I'd suggest two areas you need to develop skills in - the first is to learn design principles. These aren't program specific and translate not just across other programs but other mediums outside of web design. Aside from that, you should aim to get a lot of experience with a particular image editing program. Whether it's Photoshop or the Gimp, you'll need to, aside from understanding design principles, be familiar with a program enough to apply these principles as you make screen comps. You may also need to become familiar with translating a screen comp into a live web page, which is usually done manually, extracting images from a layered comp and working out how to use CSS to minimize image overhead.
Okay, sounds pretty daunting when I wrote it out like that :v: and I didn't even get into my particular design process (which is relatively similar to most other people's process).
To summarize, you'll need to become familiar with the principles of design, and an image editing program to design in. Best of luck.
I design & pass on but I have a good amount of knowledge when it comes to front-end development.
That's fine. It's often the case when you're working in a team environment. If you're a freelancer/working in a small team, the versatility to perform both comes in handy. And all things considered, learning html/css is [i]probably[/i] easier, though converting a comp to html/css isn't eactly easy either.
So many contradicting statements today :v:
Hah! Me designing that's funny.
:frown:
Look at other websites which are using the same topic, draw some doodles of layouts I like, create my own sketches from reference drawings, work it out on Photoshop and then sometimes find it looks horrible, tweak it until it looks pretty. insert info/images and code back end stuff.
(always ask friends and family what they think, and insist they must give at least one change which needs to be made. Then work on it)
I'm not very creative so I say to my fired "would you kindly design me a website in photosop?" and then at some point in the close future he will upload a design to his photovucket and I will copy it as best I can just using HTML and CSS
I can't really describe how I do it. I pick a color scheme I like. I start making logos, backgrounds, etc and just start coding. I like improvisation as opposed to planning it out. Always feels so much more free.
Does that mean I haven't planned a site before? Nah. I just usually improvise.
1. make generic div layout
2. add colors
3. add pictures
4. add text
done
Sorry, you need to Log In to post a reply to this thread.
