Content and Forum Management
| From: | Webmaster | Date: | Thu, 08 Oct 2009 05:15:23 +0000 |
| Subject: | Content and Forum Management | ||
| References: | 1 | Groups: | php.webmaster |
| Request: | Send a blank email to php-webmaster+get-6102@lists.php.net to get a copy of this message | ||
Hi, my name is Vector Thorn. I have been working on some information
management systems that i will launch my SaaS oriented (but not limited to)
company with. I have been a Linux user for a few years now, and am somewhat
evangelistic about it. I am a huge php fan, and have started developing my
own "framework" with it.
While i have been slaving away for free for the last year (when you develop
your own products, you're not making any income until they are finished) i
have been wondering what i can do to ensure quality feedback as to the
usefulness of my systems, and how i can contribute to the causes that i find
so useful. So i've been keeping my eye on large open source projects that i
feel would benefit from my systems, and would have a large number of users,
for stress testing purposes, and who could provide quality feedback about
the usefulness and quality of my systems. There would of course be a mutual
benefit to that organization or project.
The services in question, pertaining to your cause, would be my User Forum
Management System (UFMS), Website Content Management System (WCMS, which can
be thought of as a hybrid between an anonymous wiki, a standard CMS, and a
blog), and the User Accounts Management System (UAMS). Obviously, these
would come with a hosting account. There is no need to host an entire domain
on my servers just to use these systems, as you can just point a subdomain
to them to use them (for example: wiki.php.net or forums.php.net or
users.php.net).
As the system is updated with new features and enhanced features, they are
instantly in effect for all users of the systems. The systems stay pretty
much bug-free, until a new feature is made live, or an existing feature's
enhancements are put live. The systems have automated bug reporting built
in, so there is almost never a need for user input on bugs. To be quite
honest, not even once has that need arisen, as the bugs are usually fixed
faster than the user can get to the contact form. The user is also notified
when the bug is fixed.
There is NEVER any setup, or configuration by the client. The client
literally --and i DO mean literally-- points and clicks to administrate
their services and its users via a very ergonomic interface. Most abuse is
also automatically detected by my systems, and the users are automatically
banned. Unlike other forums and content systems, abusive content can be
safely and IMMEDIATELY removed, and without SEO repercussions. Most
administration is also autonomously handled by the clients delegated
maintainers (aka, Moderators, Managers, Contributors, Editors,
Administrators, etc), with no need for client intervention.
These services may not be ready for commercial use for another month, but
they are almost ready for public testing right now. Until they are ready,
you will not find any documentation about them on the Ionisis website (for
obvious reasons), but feel free to contact me in you would like more
information. If you would like to test drive the services, i would more than
welcome it; the only stipulation being that your testers would provide
quality feedback about their experiences with the systems. If you would
really like to "try it on", you could also point a temporary subdomain, like
"tester.php.net" or "temp.php.net" to the servers, and i can integrate the
systems into a page with your existing site's design. If you later decide
that you like the services, you can just update your subdomain records to
the name you want to permanently use.
Thank you for your time, and let me know if you are interested.
--
http://eInformationOrganizer.com *
http://TheReformProject.com *
http://LinuxIntro.com *
http://Ionisis.com *
* Denotes that the website is being completely rebuilt, and is in testing...