Theme development

Hi,
Well, I'm working on a project and I need some help.

Hey Guys, I would like to ask if why does my jquery not loading on none admin pages. I'm editing my tpl file in my theme folder and all my jquery codes are working fine when I'm logged in as the administrator but if i'm not, my jquery doesn't load. Please help me with my problem. Thank you.

I know this is probably a remedial request for this forum but I decided to update the tutorial by YesCT (https://drupal.org/node/138560) on how to modify Garland by utilizing a nice template for Paint Shop Pro and making a few css changes. The process has changed slightly for Drupal 7, but I have recorded everything I did and it should be relatively easy to follow for most. I have even found some areas that can potentially be customized further than they were when it was originally released years ago.

What I need help with is what used to be called "header-region" located around line 559 in style.css that produced a nice top 'bg-navigation' bar (that some people hate and some people love). The bar cannot be seen in D7 even though I have included the modified bg-navigation.png file and played around with the css. The region is now called "region-header" and I modified the code from:

this

.region-header {
  min-height: 1em;
  background: #d2e6f3 url(images/bg-navigation.png) repeat-x 50% 100%;
}

to this

.region-header {
  min-height: 37px;
  background: #d6e2dd url(images/bg-navigation.png) repeat-x 0% 100%;
}

I am using custom themed pages for my products. Each of my product pages is either a node page or a taxonomy page under my products vocabulary. I am putting instructions for ordering at the top of these pages and this code is conditional based on either the term in the products vocabulary or the node content type. I know how to add my custom conditional statement for different instructions on the node type as written below, but I do not know how to write a conditional markup routine for providing different instructions for each taxonomy term parent or the $termparent variable. I have pasted the node type routine below to demonstrate my solution for it. If someone could help with doing the same type of routine but for my taxonomy pages based on my term parent, I would be very thankful.

if($node->type == 'banner') {

• print base_path() . path_to_theme(); /images/star_small.gif"> Choose Your Material
• print base_path() . path_to_theme(); /images/star_small.gif"> Choose Your Size

Hello,

I'm not a Drupal developer. I run a design firm and have frequent need for Drupal development. Thus, anybody responding to this is someone I'm interested in talking to.

I'm looking for a bit of guidance on a Drupal workflow that will work best for my company.

My experience working with Drupal developers in the past has been great for back-end development, and chaotic for front-end development. Projects end up with multiple and inconsistent CSS styles, and doing quality control on the visual aspect is very time-consuming.

Moreover, I'm a front-end coder, and use HMTL/CSS/JS prototypes for all phases of projects. I would prefer if the front-end coding I do to was used by the developer instead of going to waste.

However, this workflow hasn't been compatible with Drupal dev partners so far. Because they use themes, and retro-fit them to the design I give them, they aren't able to use the HTML/CSS/JS work I do. Moreover, I have a responsive framework that I like (Foundation), and my developers want to work with the standard responsive Drupal theme (Omega). I don't like Omega because it isn't fluid.

Then there's things like my developer telling me they can't do a carrousel that uses CSS (background-image), because the available Drupal carrousel modules are all based on using the HTML img tag. Does everything have to be based on modules?

I'm working with some freelance developers who have been long term Drupal coders. My background is in front end web design and when i look through the presented code I'm astounded at how almost every element has a long string of classes. Looking at whats been don't you could have written the CSS directly in as a style= without affecting code bloat.

I ask why this is and they explained its down to Drupal's framework however i cant believe the open source community would let this happen.