Please see: http://dev.tiki.org/Blog
Trackers
RFEsBugs
Competition and standards
The ultimate Weblogging system, outlined
CVS Doc section
none yet Discussion/participation
â¡ï¸ Marking a blog entry as private, read only to yourself.
UserPagebpfaffenberger Take a look at Moveable Type, which is used by very many active bloggers. It is popular for several reasons:
â¡ï¸ paulap has created a wiki page about criteria and feature requests, BlogIdeasPaulap. The goal is to bring the tikiwiki blog to the top of the blog systems (I hope the developers hear me ð). â¡ï¸ Take a look at a new blog product from pMachine - Expression Engine. Here is the full featurelist. â¡ï¸ blogs<->wiki connection. I think this is of the utmost importance. In fact I'm surprised this hasn't been implemented yet ( I could be blind however and not notice this at all ð. I'll explain what I mean with a use case. Suppose after I finish editing this, that I will go to my blog and make an entry referencing this wiki entry. ("I made a post to BlogDev, yay!"). Now I have a link directly to this entry in my blog. What should happen next is that everyone who hits this wiki entry should also have a way of seeing the link to my blog entry referencing this page. I made a post about it on the forums here. Please let me know what your thoughts on this are.. I believe some sites out there implement such functionality already. --dmitrym. This sounds great. It seems to me Tiki needs a "render" class that takes a bunch of text and does all the necessary linking to the various sections. You can bet once blog<->Wiki is done, people will want Blog<->articles (etc!). Obviously, any such "render" class needs to be configurable, so you could switch off Wiki linking in FAQs, but leave them on in Articles (etc). ...CooferCat â¡ï¸ Extended Text - by all means make it more swish than my quick patch ð ...CooferCat Page referenced in Doc: Blogs
â¡ï¸ While working with the PHP to actually do any of this, have a thought for SEFURLs - the URLs used in the blogs are really hard to make friendly. In general, make the URLs as short as possible, consistently order variables in the query string and always specify the same things. E.g. do specify BlogId even though PostId is actually enough to locate the post. Don't specify sort order unless the user is specifically ordering the output (and so on). I sort of wonder if the whole thing needs rethinking, but in the meantime, some (reasonably) simple tidying up will do. ...CooferCat |