Great!

This was exactly what I was looking for. Thanks, Bob!

Another Great Podcast

Another great job...I'm new to Drupal and CMS based sites, so I'm reading EVERYTHING on your site...and learning a TON! Thanks for providing such helpful information!!

Also...Yes, it's OK to just do Drupal Podcasts!! That's my vote!

Would this change all pages?

Thanks! These are great and I look forward to more Drupal help.

One question: if you change the CSS, that will affect all other pages on the site, right? That is, each page you put content-top stuff into will have that same 3-column look, right?

Thanks again.

Awesome!

This is wicked! I can see your face when you perform Drupal awesomeness! Haha, nicely done, Bob!

More Drupal

I'm glad you are doing more Drupal. Of course I am a big Drupal fan and struggling to learn as much as I can about it. Thank again for all the great Drupal and CSS videos. I'm tuned in each week :)

Great Podcast

Hey, thanks for doing this podcast. I have been using Panels in D5 and just started 2 sites in 6. Been thinking about how to do it without Panels. On another note, you should check out CSSEdit from MacRabbit. It is a great CSS editor.

Bob
twitter.com/kepford

All Drupal... YEAH!

Glad you are going to focus on Drupal for this podcast.

I say keep it more on

I say keep it more on drupal. The more I learn the more I realize how much I need to know. Keep em coming pleaaaaaase.

Mo Drupal, Mo Better

Hey Bob,

Great stuff as always; Mo Drupal, Mo Better!

Question regarding Panels; in the dark caverns of my mind I thought you once mentioned on the podcast that you were, at first, pleased with Panels, but after working with them became disillusioned. I do everything in .CSS, so I've never really worked with them. Recently I was watching another screencast and apparently they can generate not only location- but context-specific blocks. .CSS can't do that!

Blessings!

-NP

Drupal YES

I'm really wanting to start building in Drupal, in fact, I plan to start building today. Thank you so much for this great content. More Drupal.

Some answers....

@Justin
Indeed...with the code I used here, it would affect ALL blocks in the content-top region. You'll noticed I mentioned quickly that you may need to target specific blocks if you don't want to affect all blocks in that region.

@Bob Kepford
I recently switched to Coda...you'll have to wrestle me to the ground to get me to look at any other editor. It's so Mac-ish...just my speed.

@NP
Yeah, panels has come a long way since I made those earlier comments. Once it comes to D6, I've vowed to use it more.

Thanks for watching everyone...tell your pals! :)

COVER ALL topics!

I dont know jack about DRUPAL, but i WANT TO KNOW! I know css i know HTML...
so how about jumping around on different topics...

front

cool... I like the idea to go all drupal. There are so many CSS and Photoshop sites out there.

One additional thing regarding the styling of the home page, is that the Zen theme you are using also has a "front" class wrapper, so by cascading down from '.front' would also get you specific styles for the home page only.

Which theme you use in these podcasts

Hay Bob,

Great podcasts, really informative and most wanted stuff you are covering.
Can you please tell me which drupal theme you have used in these tutorials.

Regards,
Shafaat Awan

Very nice

These podcasts are the tidiest, most clear ones I have ever seen about almost anything on the net. Also good and fluid pronunciation helps following the tutorial easily. In such a short time, a subject can only be explained this well.

Especially this topic cleared a lot of questions on my mind.

Congratulations...

Demo software

what software fo u use to make that demo?

Thx

This stuff is really helpfull. I am starting a project without much knowledge at all and your stuff really helps a lot.

You might consider redoing this section by using panels which is out for D6. I am strongly considering using it because I shit my pants thinking of doing a lot of css and stuff.

Going to watch the rest of your casts. Good work!

Glad it was helpful

Hey all...
glad this one was helpful...I was flattered to see it on the list of Top 5 Drupal 6 screencasts!

Very refreshing

Hey there....

I dont usually leave comments... but in this case thought I'd say thanks. Your tutorials are are at the moment exactly what Drupal needs.... I have been designing sites for 6 years and have jumped to Drupal in the last few weeks - I dont have any problem with the code structures etc and Drupal seems amazing - BUT - what amazes me is the lack of BASIC easy to understand SITE STRUCTURE ORIENTATION that Drupal covers in its documentation.... something as simple as this turorial is all that is needed to kick start an approach - i.e. I have all my content but how does it relate to the web structures and approaches we have all used for the last x number of years..... i.e. here is a news listing page here are articles.... in Drupal it doesnt exactly scream out "Create a content type, create the content and then do this to display it on one page and tie in your navigation links".

Many many thanks

clear, fast, simple!

Great resource

These video tutorials are a great resource. I've learned a lot about Drupal from them.

Hiding originally created content (node)

Firstly, your podcasts are fantastic - the best source of Drupal 6 guides on the internet.

But I've got a question: I've made some content (node), passed it through Views and made it into a Block - then made it look nice with Panels and Contemplate.

Now, I only want this content to be displayed in the Block and don't want the users to be able to see the original content I created as a node. Is there a way to hide it so they cannot access it? After all, it just contains some text and looks ugly.

I don't have any links to the original node on the site but still, I don't want any users to stumble across it or let a search engine index it.

What do you suggest?

Robots and no links

Re: the previous comment, I'd recommend that you (obviously) don't link to the node anywhere, then set it up so all your hidden urls are in a structure like example.com/hidden/my-node Then, once you do that, just use your robots.txt file to tell search engines "don't crawl anything below /hidden".

Hope that helps.

Great minds..

I was thinking of the same solution but I wanted to ask to make sure I had the right idea. I have never read any tutorials about it so I am guessing it's a) not a common Best Practise amongst most Drupal developers (maybe I don't know the right ones?) or b) overkill

Which do you think it is?

For SEO I believe this would be important because you wouldn't want Google to think you're duplicating large parts of your content and subsequently blacklisted. The other advantage, as I said above, is so that no one stumbled across the content when entering a stray URL - but this would be highly unlikely.

Learning Drupal

I am very thankful to your team for extending such a magnificient hand in learning drupal through this site.I had been told by Managing Director to develop the site using drupal,but it was new to me i was worried too much.When i got this site and after approaching it i was thrilled it is terrific site.Thanks
Yours
SHAD MD BABAR(HYDERABAD),India

hiding the container page title

Thanks for the awesome video Bob, I like the idea of using a page to contain the blocks. I was wondering how you would hide the tite of that node that you created(in this case it would be the title "home"). would that be something that you will have to code in node-tpl.php?

Can't see it

I can't see the video in either FF 3 or IE 7.

What's up?

I feel a little stupid, but

I feel a little stupid, but where exactly in my css file can I add the code?

I'm using the sky template/theme and tried inserting it into the content sub-area which didn't work, and also tried directly beneath the head in css. Directly beneath head caused some catastrophic changes (luckily I backed the css up anyway) and under content area nothing changed.

Opinions?

The best way to see how the

The best way to see how the various css documents are controlling your theme is to install Firebug for Firefox. Then use the inspect element feature.

A bar will pop-up on the bottom of your browser & any element that you scroll over will reveal its coding. The left side of bottom bar is php/ html and right side is the css. This tool is great cause it tells you according to the css hierarchy what (css) document the codes are in & what line they are located on.

D/L Firebug - https://addons.mozilla.org/en-US/firefox/addon/1843

Keep this Drupal Focused

This is just my vote to keep this site focused on Drupal. Feels like I need a lifetime to learn all there is to learn about this so this helps :).