|
It seems your focus is not on productivity (e.g. build a good website, quickly) but rather working hard, from the basics in order to build a strong foundation for the future. Learning from the "ground up" is no easy task, so I would suggest a divide and conquer strategy rather than trying to attack all the problem at the same time. For that reason I'll split the learning in a few different buckets, that you can choose to attack whenever you feel ready for it. I think the methodology below works best if you have a simple project in mind to work through (But remain stay realistic/minimalistic for now). 1. Front-end layout: html/css Here, think about the website layout you would like to have. Feel free to wander the web and get inspired by other design you like, and try to recreate them. At this point, you might need to brush up your Photoshop skills (for minor things). Look at css frameworks in terms of what they have to offer, and recreate it. (You can even look at their code to understand better). I would highly recommend using Firebug at this stage, to inspect page elements and css properties for websites you visit. As far as html is concerned, learn about good practices, and standards (quickly, don't become a fanatic). Use w3c validator at the end and try to make it down to zero errors/warnings. 2. Front-end UX: javascript While html/css focus on presentation, and creating a layout. Client-side Javascript will give life to it. Here I would suggest doing basic things like onclick events, DOM manipulation (e.g. create tabs, when you click on a link a div appears, the other one becomes hidden), changing css properties based on events and so on. You have a big important choice to make here however: To use jquery, or not. jQuery will make things much much easier, because the truth is client side javascript is a big mess. Every browser handles events, dom, etc... differently. If you were to use pure javascript from scratch, you would need handle all those differences yourself in order for the site to work on all browsers. If you use jQuery, it's all taken care of. So it's your call how much time you want to spend here. Honestly, I think it's safe to use jQuery directly. Also, I would suggest reading the following book at this point: "Javascript, the good parts". Don't worry, it's a small, quick, and easy book to read. NOTE: The following two steps above can be done on your computer locally, without the need of a server etc. But we are at a fork now, as you'll want to get your stuff online. If you want to learn about server now, read on. If you want to focus on back-end first, skip this step and come back to it afterwards. 3. Server stuff The easiest way would be to get a hosting, and drop your files using ftp. But you asked for a harder way which teaches you the fundamentals. I would therefore suggest getting a VPS (Virtual Private Server), which is a machine somewhere online which belongs to you. On this 24/7 connected machine, you can install anything you want based on your needs. These are not free, but if you look at http://chunkhost.com/ you can get one free month. Having a domain is useful as well, which is not free. But you can always reach your server using its IP if you prefer. You are familiar with php already, so go ahead and install apache/mysql on that server, along with an ftp for you to connect to it. How to learn about it? Slicehost has amazing documentation http://articles.slicehost.com/sitemap. I realize there are 'hotter' things out there than apache/mysql, but stick to the basics for now. After all, this will not teach you how to install "apache and mysql" on a machine, but really teach you how to get/setup/install anything on a VPS (nodejs, nginx, any other db). A word of warning here, this will involve very little programming, and might seem pretty tedious -- but it's good learning. 4. Backend: MVC You already know php, and I suppose how to use mysql with it. So it's time to use the MVC pattern. There are many frameworks out there, but if you really want the core understanding of how it works, create your own MVC framework. There are a few tutorials that will walk you through it, and give you great understanding of model, view, controller, routing, etc... At some point, you might realize you're duplicating a lot of mysql code and queries are all over the place. You might want to create a simple abstraction layer that makes it easier to create your queries in php (rather than in SQL). Once you get those running and working, it should be an Eureka moment. You'll understand a world of opportunities opened up for creating more complex websites, in a simpler way. You'll also realise that there are so many cool things you could add to make the system "better". That's where Frameworks come in: Teams of strong people have spent time to precisely create that. If you want to stick with php, look into "CodeIgniter" which is a lightweight php mvc framework. It is so lightweight, that it might feel in many ways similar to what you created. Also read about ORM (Object Relational Mapping), by using "Doctrine" along with code igniter. 5. Next steps... If you make it this far, congratulations :) The road won't be easy, and you'll have to dig all over the web to find answers. But it's through this search that you'll progress, so don't let it stop you (think of it as a sign you're doing things right). Now once you make it this far, there will be a lot more interesting topics to look into. But remember this lao tse quote: "A journey of a thousand miles begins with a single step" -- take your time, be patient, and learn one step at the time. Good luck, and I hope this post will be useful to you. |
That was incredibly be helpful. I will work my way through this stuff for sure and hopefully all works well. I'm sure I'll stumble and fall a bit... but that's part of the learning process. I'm in between a rock and a hard place. I want to focus on productivity (build a good website, quickly), but don't want to skimp on fundamentals and get lost in all either. I'll to try my best to find the balance, but knowing me I'll likely take the slower route and learn all I can... hopefully it ends up being the better choice.
Anyway, I guess it's time to dive into the front-end a bit more. In regards to photoshop, is splicing the accepted way to design html/css? Or do designers ever go straight to the code?
And I think going the jQuery route will be more effective. I'm sure you'd learn javascript by default when learning the jQuery framework anyhow.
And then there is the back-end. Which I will tackle after the above. Although, one question on that... as I only know limited PHP (and mySQL), I'm open to learning something different (Python/Django, Ruby/Rails), what are the reasons to choose one over another?
Anyway, I'll take this all one step at a time.
Thanks again!