Have you considered just installing a second instance of wp? Easy to do, just give the tables in the database a different prefix. Then have a whole different catagory structure for those posts, which can be linked to from the main blog.
Thanks so much for the suggestion. I had not considered going in this direction. I think this will accomplish exactly what I want.
Yes, one approach would be to have a second blog — that’d isolate what is really a completely separate set of data, and is likely the ‘best’ approach.
If for some reason you can’t go that route, you can have an extra category tag for each ‘project’ entry, and then hide them from the normal blog query (there’s instructions around of how to hide a category from the front page, which is basically what you are asking for…).
Again, WP can obviously already do this, but you have a completely secondary set of data, that isn’t even part of the normal flow of content on the blog — setting up a second ‘blog’ that is really just a CMS for the projects seems the best approach.
-d
I agree with the earlier posts – a seperate blog makes things much easier than trying to hack away at the code, which I unsuccessfully tried. I have been working on something organized pretty much the same as what you described, and I found that seperate blogs work much better; although, I would recommend using separate databses if you can. Granted, you CAN use the same database with the “as-is” WordPress installation, but I have had a few bugs once I started adding plug-ins. Another great thing about the separate blogs is you can use the RSS feed from one and still “preview” the posts in that blog if you want, so from an end-user perspective it won’t necessarily feel like a whole seperate area of the Web site. I mean, it will – but in a good way – not in that “where am I?” way …
