LampCMS open source XSLT based content management
The first open source CMS that uses browser based XSLT transformation
Decoupling blog urls from usernames
Decouple user's blog from username
Blog is blog - it's also should be a RESOURCE and as such, have a resourceID. It can extend the RESOURCE class of cause but still, it's a basic RESOURCE.
We can still automatically create a blog for new user based on a username, but we can also ask a user to pick his own blog url - sub-domain OR full domain name.
Some users may even have more than one blog associated with one user account. This would be very helpful for developers that want to create a new blog for every one of their small software packages.
A blog can have a blog entry with download (attachment), then new items may be added as updates, user can add comments, later we may allow adding a forum to a blog, so it will be everything a developer need to maintain his software and have a community.
Some things should be worked-out like should or can we allow changing the sub-domain after the blog is already establised? If user changes sub-domain it's like a big deal because all previously indexed pages will now be unavailable - we return 404 for subdomains we don't have.
Number of blogs per user can and should be determined by the usergroup, at first every user can have just one blog.
Also should a blog that hold a software have special type of RESOURCE_TYPE or not? How can we find a list of free scripts? I guess a blog that is a home of a script must have unique RESOURCE_TYPE.id
This would require a new table to hold some blog related data and we should move BLOG OPTIONS there too, so things like per-page comments, allow comments, etc. will be defined in there.
Blog is blog - it's also should be a RESOURCE and as such, have a resourceID. It can extend the RESOURCE class of cause but still, it's a basic RESOURCE.
We can still automatically create a blog for new user based on a username, but we can also ask a user to pick his own blog url - sub-domain OR full domain name.
Some users may even have more than one blog associated with one user account. This would be very helpful for developers that want to create a new blog for every one of their small software packages.
A blog can have a blog entry with download (attachment), then new items may be added as updates, user can add comments, later we may allow adding a forum to a blog, so it will be everything a developer need to maintain his software and have a community.
Some things should be worked-out like should or can we allow changing the sub-domain after the blog is already establised? If user changes sub-domain it's like a big deal because all previously indexed pages will now be unavailable - we return 404 for subdomains we don't have.
Number of blogs per user can and should be determined by the usergroup, at first every user can have just one blog.
Also should a blog that hold a software have special type of RESOURCE_TYPE or not? How can we find a list of free scripts? I guess a blog that is a home of a script must have unique RESOURCE_TYPE.id
This would require a new table to hold some blog related data and we should move BLOG OPTIONS there too, so things like per-page comments, allow comments, etc. will be defined in there.
