I'm planning a new personal site, which will be used to host my projects and activites. I've been tinkering with Drupal for about two years, and I've already decided that it is indeed the best platform for the site.

My web provider allows Drupal installation through Softaculous, so I installed Drupal 7.30 and the site is already up and running ( http://luiz.claudio.nom.br ).

In this post, I discuss my goals and requirements, and I'd like to hear your thoughts and suggestions, both on the underlying structure and on the best way to implement it.

The content in the site is still preliminary. The intended content is information on boardgames. I've written many reviews, session reports with photos, player aids, and other material on boardgames in the last few decades.

In order to better categorize all this information, I want to have a basic games page as a parent entity. Any given game can have zero or more child entities, such as files, photos, reviews, reports and so on.

I already have some content types for testing: game page, game file, game review. Right now I'm creating the node references in each child content type to the parent types. So far so good.

I plan to create views to show the consolidated information on a given game in a single page.

But I'm worried about search results. If an anonymous user comes to my site and searches for, say, Caylus, he will find the Caylus basic page and the child pages with related information. I want to restrict the search to the consolidated pages for each game, and further to block him from seeing the underlying "work" pages.

Is this possible? If so, what modules should I use for this, and most importantly, will this influence the data structure for the content?

I don't plan on having users adding content, just comments from registered users. But I wonder --- is it possible to have a forum for each game? I haven't used the Drupal forum yet, so I don't know its limitations.

That's it for now. I don't know if I gave enough information, but feel free to ask for more details. I'm eager to hear your thoughts on this.

Comments

bander2’s picture

I want to restrict the search to the consolidated pages for each game, and further to block him from seeing the underlying "work" pages.

Does this pertain to search only? Or is this a membership site where the content is only available to registered users?

- Brendan

LClaudius’s picture

I don't want to create a membership site, no. I'll only request registration in order to post comments. All content will be created by me.

What I haven't been able to gather yet is perhaps better explained this way: I have "work" pages, with unformatted content, and I have "fancy" pages, created with Views. I don't want the users, registered or anonymous, to be able to see (or search for) the work pages, but only the fancy pages.

bander2’s picture

The Search by Page module allows you to omit certain node types from search and it indexes views pages so I think thats going to help.

Something you might want to consider is that nodes always have a url. It is a property of nodes. So a user can always type in node/100 to see the game review that you don't want him to see. Also, because Drupal expects you to be happy about having a url for your node it might pop up in other places and cause you annoyances. You might consider using entities instead of nodes. Entities make fewer assumptions about your content (nodes assume your content has a url, title, author, created date, etc). The Entity Construction Kit module make working with entities as easy as working with nodes.

- Brendan

LClaudius’s picture

Hm, very interesting suggestions. Thanks! I'll take a look at them and tinker a bit.