There's a long standing debate over the content of RSS feeds. For the greatest convenience of your readers the full RSS feed is great, because they can read your articles in their feed aggregator. However as a publisher who needs to earn a living from my writing I only want to publish a teaser so that the reader will feel incentivized to visit my site. For me the feed is a lure to bring people to my site, and I cannot do justice to others' viewpiont.
The core Tracker module is a convenient way to look at recent traffic on a Drupal site. It shows a list of recently posted (or modified) nodes along with useful data items for each node. However with Views 2 there is a more flexible way to implement the same functionality, without enabling another module.
The task is really pretty simple. Just download and enable the Views module, then in the Views configuration interface enable the Tracker view. Yup, coming bundled with the Views module is a predefined view which does every task the Tracker module does.
In two prior blog posts (see the references section below) I've discussed using a website content type to create resources lists. In this post I want to discuss another use, for a kind of footnoting system. You can see it in action below.
An earlier blog post (see references below) discussed a website node type that I frequently use. One purpose for the website node type is to build "resources" web pages. The "resources" page is an old practice on the Web where a site might host a resources page listing useful sites. These resources pages can be a gold mine of information for users, but I suppose it can be a pain to maintain if the page is a static page you have to remember to edit to add a new resource link.
For several years I've used a CCK content type named 'Website'. The purpose has been to simply list links to websites for my reference and others benefit. The traffic on my sites shows that the website links (specifically the taxonomy pages listing the website nodes) are popular and in some cases the most popular part of the sites. In general "resources" pages are an old practice on the web, you'd see a "Resources" page on most sites that's a simple list of links to useful sites.
A good quality taxonomy listing page can act as a really good sitemap. Good sitemap pages are great for internal linking effects that helps visitors browse your site, and coincidentally aids in SEO. Most (?all?) nodes will have taxonomy terms attached to them. Hence it's a pretty good start to aid someone to browse your site. The problem is the core taxonomy module doesn't make good quality listing of taxonomy terms. For instance it ignores the term hierarchy, it doesn't display links to child term pages, etc.
Looking at a colleague's website (organicJar.com) and was jealous over the Feedback button on the side of the page of that website. It's an AJAX'y button at the side, themed so it stands out well over any background content, and plops up a nice form letting visitors give feedback. See the image to the right. It's of course important to get feedback from your visitors, to engage visitors, and perhaps if they have a good experience on your site they'll return again in the future.