Before you start

As a long-time lurker on the forums and Drupal enthusiast, I thought others might find this primer for new Drupal users very useful.

http://broadcast.oreilly.com/2008/11/getting-started-with-drupal.html

New users may wish to view Kurt Cagle's recent blog post at O'Reilly -- it's an in depth overview of:

Prepping a Basic Drupal Site
Configuring a Drupal Site
Creating Content
Enabling Modules
and a look at Theming

my client has sent one pdf file, in that file they asking me to include one image tag in administration console(/5/?pageName= " "alt="" width="5" height="5" />), or any other way to integrate omniture. please provide me some information.

Hi, I am a graphic print designer that has been asked by my company to start building websites. I am MAC based and totally new to web design. I have done some research and want to give Drupal a try. I have a feeling I am in way over my head but am willing to learn. Are there any pieces of advice you can give a totally green newbie?? We will need to build clean, not-too-fancy websites, possibly with shopping carts, news content management that clients can update, etc. Any words of wisdom and direction would be appreciated.

I am new to any CMS software but after consideration decided that Drupal would do everything that I want.

But two questions before I start and I apologise if they are very obvious to some.

I assume that I need to install PHP and MYSQL on my PC before I can install Drupal, correct ?

Secondly, does the service provider that will be hosting my website need to support PHP and MYSQL ?

Thanks

Hi there,

I've been looking at the beginner's guide to Drupal and there's something I can't really determine, so hopefully someone here will be able to shed some light.

I'm putting together a site for a client and they require some form of basic CMS. I will put together the site and lay it out as per the design with CSS - and they just want the ability to change aspects of the text and pictures over time. The client is a building firm, so they will have a couple of overview portfolio pages with 6 overviews per page, then 12 more detailed pages linking off those two.

They'll need to be able to change the wording and images (but retain my CSS layout) over time for certain pages, as new projects get completed and they want to showcase them instead.

They also want a few kind of scratchpad pages where they can almost add anything they like, such as news, etc etc. For them I will just give them some blank pages with some CSS formatting pre-applied for a blank div or something.

I'd like to do all of this in a fairly lightweight fashion - i.e. I really don't want a username and password field permanently on the site, maybe just an 'admin' link that will enable them to log in. When they do log in, ideally I don't want 10000000000 options to appear as the client may be overwhelmed. I just want an intuitive way for them to edit areas I choose.

Hello everyone,

I'm reviewing Drupal after last looking at it two years ago.
I'm impressed with how far Drupal has come since then!

However, I'm disappointed in trying to figure out how well it scales in a n-tier architecture and how it might support a development > staging > production methodology as separate instances for updates as well as publishing. Let me elaborate:

First, after reviewing the FAQ, I see that http://drupal.org/node/202799#serverhw points to a non-existent page that might give me some insight into how drupal.org infrastructure is set up as well as what kind of demand/traffic it supports.

What I'd like to see is that you've got a classic three tier architecture which allows scalability/failover on all tiers, e.g.:

[Internet] -> [Firewall] -> [Caching proxy or web server 1..n] -> [Firewall for DMZ] -> [Drupal App Server 1..n] -> [Firewall] -> [MySQL Database cluster, node 1..n]

where 1..n represents 1+ servers, up to a count of n. Such as: server 1, server 2, server 3, ... up to server #n.

Can Drupal support that? Is there any evidence or technical case studies that illustrate?

Second, the development to staging to production methodology question.