ÿþHi everyone, my name is Fox.
And I am Fede, today we ll look at the Drupal core modules, part 2!
A small recap: we ve seen how to install Acquia Drupal, and how some of the basic core modules work.
Exactly, we have a nice Drupal website, a blog post, a picture of the author of the post and a link to its twitter.
It s time to make it a little bit more customised and dig into Drupal configuration.
Here we go, I took of the liberty of resizing the picture a little, back to the default. OK, looks pretty good, but it still says  My Acquia Drupal Site  and it has the Acquia logo on the top. Probably one of the first thing that you want to do is to change those two values, before going into production. We ll do that by going to  site Configuration -> site information . So, Who s afraid of Drupal? And our mission is...
Don t worry, be happy! 
Exactly. Save that... And there we have it.
What about don t worry, be happy?
No problem, it s all saved, we just need to tell the theme to show it. Just as we did for the profile picture, we ll do the same for the site slogan. Site building, theme, garland, our theme, toggle site slogan. Ta-Da!
Nice!
Let s add a custom logo, too. And boom! Now, back to the home page. Notice that we still have this page at the bottom.
I think it s a good time to explain the concept is publication.
You re right, let s go back to the studio.
See, this is how Drupal works. Whenever you save a blog post, a page, or anything else, the content is stored on the database.
Mh-mh.
A content can have three states: published, promoted to front page, or sticky at the top of the list. The first one will make sure the content is visible to normal users, such as anonymous visitors. The second will make it appear on the front page, and the last will make it stick at the top of everything else.
I see. What if we have two posts, that are both promoted to front page and have the sticky flag on?
Good question. By default the system will simply put the latest one on top of the other, and then everything else. There is of course a way to show the content differently, but that s for another lesson. Now, back to the website!
We want to get rid of this page from the home, but we don t want to delete it. The way to do it is to simply demote from the front page.
What s that  join summary ?
This is how the teaser will appear. A teaser is a short version of the post, the one that appears, for example on the front page, before opening the full content. It s useful to split some content on the teaser and some on the full body, especially for very long posts. In this case the Acquia guys wanted to make sure that all the content of this node (this page), appeared in the teaser, otherwise the default value of Drupal might have kicked in, and some of the content might have been trimmed. OK, let s depublish the page and demote from home page. Notice how the background has changed. Admins can see all posts, even those that are unpublished, but to distinguish them from normal posts, Drupal uses this CSS trick. This way we know immediately how to deal with content, without having to go to the administration menu. Back to the home page and boom! The page is gone.
Int. Studio greenback
Help with graphics.
It s getting better, but we re not quite there yet. See this, this is a menu called  Primary links . It controls how the main links of our website appear, most of the users click on those whenever they visit a site.
Precisely. It s important to place the links to all the relevant content, so that it s easily accessible. We suggest not to use too many, 3-5 is a good number, anything more just bothers and distracts people. What do you say? Shall we add a link to the blog and to the contact page.
Let s do it!
First thing to notice is that the Home link doesn t actually link to the front page, but to our blog post we put before. Let s go ahead and change that, we ll be using this special token front, between angular brackets. This will point to wherever is the front page.
What do you mean  wherever is the front page ?
Drupal has a default value, defined in the Site building, site information section
But you can change that if you want. By using this special token, Drupal will dynamically adjust the link to whatever value you used for the home page, so that you don t have to go and change it manually. Now, to site building, menu, primary links. There. Now we need the path of our blog. Click on fede s blogThis is the path we need, blog/1. 1 is the ID of the user, in this case the first user, and it s the blog specific to you. But this site may have multiple authors, by removing the 1 we ll have all the blog posts of all authors of the website. We can drag the items using AJAX, save it, boom! Now, what s missing.   
The contacts section.
Right! Let s go enable the contact module. Now in site building we have the contact form configuration. It s empty, so let s add a category, we ll call it general information, fill in a recipient, and an auto-reply message. This means that anybody using this contact form will immediately receive an email with this message inside. Selected means that this will be the default contact form for the users, yes. Here s a link to the site wide contact form, it s contact. Add it to the primary link... Now, let s try opening another browser and see what do normal normal visitors see.
Access denied, you forgot to configure the permissions! Always remember that guys, it s tricky, sometimes you forget, and don t realise that things are not working. Always test with anonymous users. Let s go to user management -> permissions, you ll see two columns on the right, these are the default user role. You can more, and we ll see how to do that in the future. We ll give access to the contact form to both user groups. Save it, and boom! Also the anonymous users can now perfectly navigate throughout the entire website.     
That s it for this Drupal Core Modules part 2, we ll be seeing you next time with something very juicy, CCK.
Stay tuned!