Before you start

Hi,

After some general information and suggestions.

I have a site I was asked to build. Now it has been decided that all the team riders will get their own actual website. But want to share one gallery, and link to eachother etc etc. There would be many elements on the sites the same.

The unique requirements for each is:

Header,
Footer,
Gallery,
About Page.

The rest of the sites data is to be the same. However keeping in mind that each about page is to be accessable by a different domain.

I run a large archaeological website in the UK (http://www.wessexarch.co.uk/), and it's about time I updated it to use a CMS, to help me as it grows ever larger. We're a charity, and it's just me to do the website management at the moment!

I'd like to ask a few questions about Drupal if I may (it's quite a long list!).

We produce 'project homepages' for our archaeological projects. Each project homepage has its own menu, and sometimes submenus, depending on the complexity of the project. At the moment, there are about 50 projects, but this will hopefully grow into potentially hundreds.

1) Finding a project of interest - listing our projects

Visitors who go to our main index page click on "Projects" and they see a list of counties and time periods, as well as a few featured projects. clicking on the county or period dynamically lists projects that match those criteria. It's done with a quick and nasty ASP/Access approach. Each time a project is uploaded I manually alter a database with the relevant info to create the project name and link on the period/county pages.

As I understand it, could this be done in Drupal by tagging content with county and period, and then getting some PHP code to produce a unique list of counties and/or periods on the project page?

2) The Project Homepages - contextual menus

Each of our projects have their own 'homepage' and customised menus. For example, our discovery of a rich burial near Stonehenge (http://www.wessexarch.co.uk/projects/amesbury/archer.html) has a custom menu. How easy is it in Drupal to create ad-hoc menus that only appear on certain pages?

What's the difference between these two modules? Both seem to do the same thing.

Hello, (and thanks in advance)

I'm planning on using drupal 4.7.2 to develop a collaborative audio website. The front end would be public (multiple pages), but we don't want the public to know anything about what's behind this. I've been reading up on all of the modules, and I think I'm getting the hang of how these work.

I'd like to know if it's possible (either through building this into the template or through a module) to have multiple front pages which are public, and then the rest of the site be private. The functionality as I see it would run something like this:

Public:
1. home page with news
2. releases
3. images
***no login for public users

Private:
1. file repository for trusted users
2. forums for development of audio
3. posts for discussion of techniques
***these pages should not be able to be viewed at all by the public

It seems like the Frontpage module would at least take care of one page (but looks like it's used more for splash pages), could it be used for multiple pages? OR (another way I'm thinking about this...) If I combine Index module with say Taxonomy Access, could I say have the public pages be generated and then use the Pass Access module to keep users out of any other part of the site? It looks also like the Secure Site module might be what I'm looking for, in that it would use browser base authentication for certain portions of the site and hide them from crawlers and robots (which is definately something we need).

Hello ...

I am looking to develop a 'family' site, with the following criteria:

- have blogs, forums, galleries, news, etc.
- a select handful of pple can actually post things (the 'main family')
- their friends can sign up to view content
- anonymous people can view certain content.

So, what I require is essentially 3 levels of users:
- family
- friends
- anonymous

This is on a per content basis ... for example: if I have a "kids story" section, then only family can see this.
However, I also want a per item/node restriction ... so if a family members posts something, they can choose whether only 'family' can see it, 'friends' , or everyone ('anonymous') ... naturally if you chose 'friends', then 'family' could see it ... so this would work on a per category, or per specific item.

Also, I understand that Drupal can categorize/taxonimze things in many different ways (which can get quite confusing) ... what I need is something basic: organize by content type (blogs, photo gallery), and/or by poster ...

So Family Member #1 would have a section with all their posts & photos, and it's separate from Family Member #2 ....
However, it's all possible to see an 'overall family' layout ... where I can go into blogs, and see all of the family members' blogs .... or a conglomerate photo gallery, with everyone's pics ...

can Drupal do this?? if so .. how??

It seems to me (a newbie), that Drupal is so extensible, that it's almost confusing ...

Setting up a new VPS server and am ready to go ahead and install MySQL. However, after reading this presentation;

http://www.mysqlperformanceblog.com/files/presentations/UC2006-MySQL-5.0...