Sometimes you want to add menu items that can only be accessed if the user is logged in. With Drupal 6, the menu_per_role module is the way to go. That module, however, is not available for D7, at the time of this writing. So, what to do?
I actually started this review of Visual Quickstart Guide Drupal 7 by Tom Geller (Peachpit Press) with some trepidation. You see, it has been quite some time (epochs) since I was a noob, not that there's anything wrong with being a noob! It's just that I felt to do justice to those reading a review, I need to review it from the standpoint of a reader who is depending on the material, and yet, to do so, I need to understand what someone with little Drupal experience will find useful, so really, I needed to be of two minds while digesting Geller's writing.
Considering I haven't contributed a line of code (yet) to core, I hate to say anything critical, but I noticed that Drupal 7 is displaying a "read-more" link for every teaser, even those in which all the content is being displayed. Having someone click a link to read more, when clicking the link provides no additional content is...deceptive, at the least, and probably aggravating too.
I was starting to lose hope when Alpha 5 came out, and was despondent by the time Alpha 7 did. I'm plugging along with the book, half way through the first draft, but at least 25% will need to be revisited to complete examples that hit brick walls because of things just not working as they should, yet, such as custom fields not appearing in the Views sort criteria field list.
If you're a Drupal developer, you're aware, no doubt, of the coming of D7. One of the exciting changes in D7 is that CCK has been brought into core...somewhat. The changes provide opportunities to do things that were much more difficult to do before, but also, might create a black hole of challenges in the migration space between D6 and D7.