- Maintain a list of weblogs that are strongly place-centered. This should be inclusive rather than trying highlight favorites. We probably would want to store the list in a database from the outset. What would be the right choice of PlaceBlogDatabaseFields?
- Use a BlogAggregator mechanism to highlight recent posts on place on people's own weblogs. The idea would be to highlight particularly interesting or general posts.
- Adapt the [Carnival of the Vanities] idea so that we would have regular submissions of best posts about place to a site or set of sites.
- A blog-ring (from LisaThompson?): "Or we could do a blog-ring, where each of our posts appears, or where there are links to each of our sites, and we take turns maintaining the stationary portal. By this I don't mean the random "click for the next blog" type ring. I guess I mean a portal site with a focus on 'blogs of place' and links to our sites, perhaps teasers from our daily posts on the home page with links off to our own domains for the rest of the post, and maybe some unique content that we contribute to the portal site."
I've moved the discussion of categories of blogs about place to PlaceBlogCategories
Here's a list of questions I raised in an email to Fred the other day. --Allan
- How important will be the directory of place blogs with respect to the rest of all the other elements?
- What mechanisms do we use to update the directory? (Can anyone add and update their own directory information? Should entries be filtered through one of the 'inner circle'?)
- What will be the relationship between posts on our own individual sites versus centralized posts?
- Where will the wiki fit in all this?
- How do we come up with a graphic design, look, and feel for the site?
Where should the directory of place blogs go? Right now I'm inclined to leave these inside the wiki, and maintain these in wiki-manner (open for anybody to edit, revise, or add). Rather than a single list as we have now, each blog should have its own page, e.g. FeathersOfHope. We can then maintain lists of blogs by attributes e.g. geographic region. And if we developed a standard template for these pages, lists of these blogs could be sorted in any manner, and displayed in a read-only manner outside the wiki.
An opposite alternative to this is to keep the directory in a separate database, and have strong rules about who can access and update the database. For instance, if it were open to additions and edits by the general public, each person would only be able to update their own entries, which likely means we'd need password-protected directory accounts for everybody who wants to make an entry. This get complicated, and I'm not sure is worth the hassle, both ours and our public.
Allan, since you seem to be the person who is managing the wiki and the one for whom the system could become the most hassle, I think you should make this decision. Why not go with the scheme you describe in the first paragraph, and if we run into horrendous problems down the road, perhaps we could restrict access. My instinct is always to trust people and keep a system as open as possible - with our own eyes open and trying to anticipate potential problems. --Beth
That's definitely the wiki spirit -- keep it open and let the community deal with problems (most of which will be unintentional, like incorrectly formatted weblog descriptions). -- Allan