After things fell apart with the Drupal project that I was into, I had a week of distraction followed by starting back up on a Wordpress Template project.
While I know many Wordpress Template creators that base their template off of someone's pre-existing one, I wanted to start from scratch since I only need a very simple template anyway. Besides, I never know how to gauge how original your template is from complex one you based yours off of. After a while all Wordpress templates probably can start looking alike from one artist to another's.
Almost everything of mine is done. Now all that remains is cleaning up the CSS before getting it transfered to a live website. CSS cleanup can be like cleaning your room. You have to clean out the code you dont need as well as get some of the like objects to be placed together. I have found some useful links that discuss this very thing:
5 Steps to a More Organized Style Sheet
11 Useful Tools to Check, Clean and Optimize your CSS file
10 Best CSS Practices to Improve Your Code
Dropping Stones into the Path
Been on vacation for close to a week and a half. Motivation to do much work has been hard with the concept of play is in a new context than what I am accustomed to in SoCal as of late. No worries. I did take my work with me and I got a few other unrelated projects out of the way.
So, as you know, the live site is up and so Im trying to go through processes all over again, learning them a second time and further drilling important keynotes into my repretoire. Also am keeping the few modules updated on the live site (about 9 less modules than on my localhost version). Admittedly part of my procrastination has been just the diverse learning experience that Drupal can afford since, well, Drupal can make all sorts of website types out there.
Im also going to use this "second time round" to get a good idea of how my workflow adapts to the Drupal environment. There are common methods and sequences no matter if Im doing an html/css site or doing something such as wordpress. Still, depending on your framework, it may differ. This might be the first time that I fully write down my methods to madness. Maybe this is a good way of taking my own advice since I tell people to write things down all the time. Does writing something out make it more significant than being part of the trains that chug about in your head? Hmmm.....
Step one was to make a site map on paper. I did about 2 revisions, the first one just taking what sections/pages that this site had in its old incarnation and recreating them. Then the elimination came, producing Version 2 which condenses defunct pages and elaborates on the section linking hierarchy will be.
Assessing your site's needs will determine modules you might need now or in the long run. Its important to work through things step by step. You can always add, change and remove modules as needed so dont get too caught up by this. Drupal's many options are what enhance your learning experience but can also deter you by overwhelming the part of your mind which innovates.
Now comes section-specific brainstorm time! Focus on the main aspects of the site, starting with the most important one. In this case, my site's number one purpose is to display products in a catalog form. With Drupal letting one create content types with any type of field (with any kind of display type), it is probably best to brainstorm all the fields you will need.
While most would suggest some of the ecommerce modules (Ubercart is a very popular choice), simple taxonomy is the method i am using for splitting my products into categories. I need to get an idea of that category hierarchy and then create a product vocabulary. Categories and subcategories will go under that vocabulary as a term.
With the brainstorm sheet(s) in hand and taxonomy created, start adding those fields. At this point, one might want to install any further field display related modules. ImageField is one of the most popular ones for product driven content such as mine. For me, some fields are going to be hidden to annonymous/guest users and others might be hidden to particular roles that authenticated users could be assigned. So, for "step 5b", I'll create those roles and set up permissions accordingly, including specifying fields which only certain role types should be able to see. Another optional step will leave me defining field groups for the product content type since I want to use fieldgroup tabs.
Once content types are set up with fields and/or respective taxonomy applied, you are nearing the end of the functionality part of things (but dont quote me on this, kiddies.). Now you can get closer to the theming aspect of things. This includes determining layout aspects such as your menu's hierarchy and placement, colors, and overall placement of body content as well as dynamic blocks of content. Ill leave it up in the air as I figure that part out myself.
So, as you know, the live site is up and so Im trying to go through processes all over again, learning them a second time and further drilling important keynotes into my repretoire. Also am keeping the few modules updated on the live site (about 9 less modules than on my localhost version). Admittedly part of my procrastination has been just the diverse learning experience that Drupal can afford since, well, Drupal can make all sorts of website types out there.
Im also going to use this "second time round" to get a good idea of how my workflow adapts to the Drupal environment. There are common methods and sequences no matter if Im doing an html/css site or doing something such as wordpress. Still, depending on your framework, it may differ. This might be the first time that I fully write down my methods to madness. Maybe this is a good way of taking my own advice since I tell people to write things down all the time. Does writing something out make it more significant than being part of the trains that chug about in your head? Hmmm.....
Step one was to make a site map on paper. I did about 2 revisions, the first one just taking what sections/pages that this site had in its old incarnation and recreating them. Then the elimination came, producing Version 2 which condenses defunct pages and elaborates on the section linking hierarchy will be.
Assessing your site's needs will determine modules you might need now or in the long run. Its important to work through things step by step. You can always add, change and remove modules as needed so dont get too caught up by this. Drupal's many options are what enhance your learning experience but can also deter you by overwhelming the part of your mind which innovates.
Now comes section-specific brainstorm time! Focus on the main aspects of the site, starting with the most important one. In this case, my site's number one purpose is to display products in a catalog form. With Drupal letting one create content types with any type of field (with any kind of display type), it is probably best to brainstorm all the fields you will need.
While most would suggest some of the ecommerce modules (Ubercart is a very popular choice), simple taxonomy is the method i am using for splitting my products into categories. I need to get an idea of that category hierarchy and then create a product vocabulary. Categories and subcategories will go under that vocabulary as a term.
With the brainstorm sheet(s) in hand and taxonomy created, start adding those fields. At this point, one might want to install any further field display related modules. ImageField is one of the most popular ones for product driven content such as mine. For me, some fields are going to be hidden to annonymous/guest users and others might be hidden to particular roles that authenticated users could be assigned. So, for "step 5b", I'll create those roles and set up permissions accordingly, including specifying fields which only certain role types should be able to see. Another optional step will leave me defining field groups for the product content type since I want to use fieldgroup tabs.
Once content types are set up with fields and/or respective taxonomy applied, you are nearing the end of the functionality part of things (but dont quote me on this, kiddies.). Now you can get closer to the theming aspect of things. This includes determining layout aspects such as your menu's hierarchy and placement, colors, and overall placement of body content as well as dynamic blocks of content. Ill leave it up in the air as I figure that part out myself.
My Current Challenge
Simple and sweet, this is my goal for the individual product page. Was hoping to use fieldgroup tabs module but it baffles me on how it will be done. JQuery and JQueryUI are my next stops. I see some explanation on it but it covers Views, which is a bit foreign to me. Maybe I should look at that first.Will be doing a manual recreation of my work on a live server in the next few days before and during my vacation/excursion. Yeah, I could of imported/exported the database but it would keep me from getting what I already learned further set into my head by doing it all over again.
Wiring It Up
While not every day leaves me pouring over internet texts like a information hungry vampire, I did get a decent chunk done in a 2 or 3 day period. I can see how this project could have alot of potential but it may die before it leaves the ground. Of course, I know the value of recycling so I suppose I will find a way to make something out of it anyway. On that, we will have to see.
CCK and Views are very concrete modules. After adding them, I enabled all the sub modules as well as the main one. Honestly cannot say that I have met a Drupal user who didnt find these insanely useful. Then again, in the case of CCK, who cold be happy with just being restricted to page and story content types?
Delving into the taxonomy, I created my Product Vocabulary and created terms based on the catalog's categories and sub categories. Once done, I went into the vocabulary's settings to make sure that the content type would use taxonomy which referred to the Product vocabulary and it's terms.
As I started elaborating on what kinds of data the Product content would be concerned with, I got curious about what I might be able to do which would restrict certan fields from being viewable by guests to the website as well as certain types of authenticated user roles. I asked Nibbler, who suggested the Content_Permissions module. After installation, I went into Administer>User Management>Permissions and there it was. Thanks alot, dear.
When it comes to layout, Im still avoiding really getting too deep into it with the exception of analyzing it from a functionality point of view. For example, it is important to have an idea of what content might appear where...but I am not going to focus on where in the page it will be just yet. One thing I want to do is get a horizontal tab layout on the individual product pages. With the amount of information that people can see about any given project (plus the images), it could get really lengthy. Tabs would be neat to do.
Found a module that could help with it but it is still in development snapshot stages. Did a bit of twittersourcing and searching around to see if anyone might know what has caused it to be in this status since last October. Looks like it got put on the back burner but no real problems reported. I installed it after a bit of debate about my typical rule of thumb (which is, "If it is beta, stay clear.").
At some point, Ill get into a few other modules I installed which pertain to adding the image content for the products. Sadly the concept of Views still eludes me. I tried a few times to read up on it but got a bit lost. It was late at night and I think I had burned the last of my midnight oil. Ill tackle it later. Sure is a comfort to know that Lullabot has released 2 more DVDs, one of which that covers Views alone.
CCK and Views are very concrete modules. After adding them, I enabled all the sub modules as well as the main one. Honestly cannot say that I have met a Drupal user who didnt find these insanely useful. Then again, in the case of CCK, who cold be happy with just being restricted to page and story content types?
Delving into the taxonomy, I created my Product Vocabulary and created terms based on the catalog's categories and sub categories. Once done, I went into the vocabulary's settings to make sure that the content type would use taxonomy which referred to the Product vocabulary and it's terms.
As I started elaborating on what kinds of data the Product content would be concerned with, I got curious about what I might be able to do which would restrict certan fields from being viewable by guests to the website as well as certain types of authenticated user roles. I asked Nibbler, who suggested the Content_Permissions module. After installation, I went into Administer>User Management>Permissions and there it was. Thanks alot, dear.
When it comes to layout, Im still avoiding really getting too deep into it with the exception of analyzing it from a functionality point of view. For example, it is important to have an idea of what content might appear where...but I am not going to focus on where in the page it will be just yet. One thing I want to do is get a horizontal tab layout on the individual product pages. With the amount of information that people can see about any given project (plus the images), it could get really lengthy. Tabs would be neat to do.
Found a module that could help with it but it is still in development snapshot stages. Did a bit of twittersourcing and searching around to see if anyone might know what has caused it to be in this status since last October. Looks like it got put on the back burner but no real problems reported. I installed it after a bit of debate about my typical rule of thumb (which is, "If it is beta, stay clear.").
At some point, Ill get into a few other modules I installed which pertain to adding the image content for the products. Sadly the concept of Views still eludes me. I tried a few times to read up on it but got a bit lost. It was late at night and I think I had burned the last of my midnight oil. Ill tackle it later. Sure is a comfort to know that Lullabot has released 2 more DVDs, one of which that covers Views alone.
The Start
Greetings! I take a break now from the finicky job market to actually blog. Yes, I now have been rejected for being over qualified on web design. Thats shocking to tell you the truth. Admittedly I have also been a bit scattered among things but I allowed for a bit of creative distraction. The sun is coming out and I sure hope to get back out to the outdoor events with my friends as well as bring my "office" out onto my deck.
Amongst some revisions to 2 HTML/CSS based sites, I am slowly changing my gears back towards the Drupal front. The drupal meeting a few weeks ago was stellar. I learned alot more about how Taxonomy works which will help me with the "catalog" portion of things. Did a bit with creating an administrator role which I always have to do with a new Drupal install.
There are a few commands Im using more and more when it comes to installing modules and the subsequent need to chown them appropriately. Of course this wont always be the case for future work but it is pretty much the same whether Im doing this on my local machine or an actual hosting server
Modules Installed:
Amongst some revisions to 2 HTML/CSS based sites, I am slowly changing my gears back towards the Drupal front. The drupal meeting a few weeks ago was stellar. I learned alot more about how Taxonomy works which will help me with the "catalog" portion of things. Did a bit with creating an administrator role which I always have to do with a new Drupal install.
There are a few commands Im using more and more when it comes to installing modules and the subsequent need to chown them appropriately. Of course this wont always be the case for future work but it is pretty much the same whether Im doing this on my local machine or an actual hosting server
Modules Installed:
The House that Mary Built
While I sit in a holding pattern on getting a portfolio site up (I need to spend money to make money but I sure dont have much of it right now), I decided to create a blog seperate from my sordid and silly personal life. Maybe I am just addicted to blogging, I dont know.
One thing I do know is that I finally want to do some better documentation of skills I acquire as well as what I learn about my own methods of thinking and how I go about processes. Take last night's Drupal meeting.
We talked about alot of things. While I picked up some new things about Taxonomy, Creating Content Types and the significance of Image Cache modules, I also came home with a better understanding of how I view the overall design and development of a website.
Being a designer with at least a bit of versatility, I find myself equating a website to a house. In a traditional website, the navigation system would be like the house's blueprints. Add walls to the house with Layout. The lighting and plumbing would probably be things like functional code such as Javascript or PHP which add certain functions such as echoing a statement or conditionals. When it comes to my specialty of the look and feel, that would probably be the landscaping round the building, the house paint job and interior decorations such as wallpaper and those cute checkered kitchen floors.
For Wordpress and Drupal, its pretty much the same thing, except my design is more or less called Templates or Themes. CSS is still used but the theming/template method just a slightly different animal in the implentation of things.
Honestly I never really explained it out like that. However all the questions floating around that people at the meeting were asking me about realy brought me to put things into an analogy such as this. For that Im thankful. High Desert Drupal crew really knows alot of stuff and they arent too gunshy about dealing with someone as new to things as me.
One thing I do know is that I finally want to do some better documentation of skills I acquire as well as what I learn about my own methods of thinking and how I go about processes. Take last night's Drupal meeting.
We talked about alot of things. While I picked up some new things about Taxonomy, Creating Content Types and the significance of Image Cache modules, I also came home with a better understanding of how I view the overall design and development of a website.
Being a designer with at least a bit of versatility, I find myself equating a website to a house. In a traditional website, the navigation system would be like the house's blueprints. Add walls to the house with Layout. The lighting and plumbing would probably be things like functional code such as Javascript or PHP which add certain functions such as echoing a statement or conditionals. When it comes to my specialty of the look and feel, that would probably be the landscaping round the building, the house paint job and interior decorations such as wallpaper and those cute checkered kitchen floors.
For Wordpress and Drupal, its pretty much the same thing, except my design is more or less called Templates or Themes. CSS is still used but the theming/template method just a slightly different animal in the implentation of things.
Honestly I never really explained it out like that. However all the questions floating around that people at the meeting were asking me about realy brought me to put things into an analogy such as this. For that Im thankful. High Desert Drupal crew really knows alot of stuff and they arent too gunshy about dealing with someone as new to things as me.