Articles - Page 250

Not All Heroes Wear Capes. Here's Why CMS Is Your 'Unsung Hero' in 2025

janus-boye

The latest release candidate of ImpressCMS 1.1.2 is out. This release incorporates the following changes:
Fixed
<ul>
<li> User was logged out if they double-clicked on the Administration Menu link</li>
<li> CAPTCHA was being bypassed on the registration form</li>
<li> Activation key was not in the activation emails being sent to the administrator group</li>
<li> WYSIWYG editor was being used for several text areas where it was inappropriate</li>
</ul>
Improved
<ul>
<li> SMARTY was updated to the latest version – 2.6.22</li>
<li> Password encryption method can only be changed if the site is open and allows you to access the reset password page</li>
<li> Database factory improvement by GiJoe, providing more protection against SQL injections when Protector 3.30+ is installed</li>
</ul>
Added
<ul>
<li> SimplePie RSS generator</li>
</ul>
For a complete list of changes, read the <a href="http://wiki.impresscms.org/index.php?title=Change_Log#Impresscms_1.1.2">changelog</a>.

New release candidate for ImpressCMS 1.1.2

mike-johnston

Vignette has announced that earnings were down 11.6% from the previous year and reportedly have decreased 30% since 2007.
“Despite a challenging economic environment in 2008, Vignette delivered operating profit and positive cash flow for the full year,” said Mike Aviles, president and CEO of Vignette. “In 2009, Vignette is looking to build on its position as the leading independent provider of content management solutions. We are committed to keeping our balance sheet strong while we continue to enhance our product portfolio to position the company for the long-term.”
This is a trend we expect to continue as ECM vendors struggle to maintain both market share and overall appeal for their customers. Open Source initiatives such as Alfresco and other pay as you go based companies are seeing a growth while flat fee based products are seeing a decline. Will SaaS (Software as a Service) begin to see a rise? It's too early to tell but expect some difficult times ahead for those in the industry.
More details on the Vignette reporting at <a href="http://www.vignette.com/portal/site/us/menuitem.62215d74e262b2ba32189210180141a0/?vgnextoid=be76b12f0b93f110VgnVCM1000005610140aRCRD&amp;vgnext-selected-menuitem=191626ff2f7512e8fb3d8010180141a0&amp;gbl-vcmprguid=be76b12f0b93f110VgnVCM1000005610140aRCRD" target="_blank" rel="noopener noreferrer">Vignette's website</a>.

Vignette reports 30% decrease in revenue since 2007

No we don't want you to fly south, this is for those of you who need to migrate from Postnuke to Zikula.  Zikula CMS 1.1.1 is the first bugfix release for the 1.1 series, and fixes 65 bugs found in 1.1.0.
According to the release notice:
“This will be the only published migration distribution for 1.1.1, so we strongly encourage you to use this release to migrate your PostNuke site. The 1.1 series is now very stable and few bugs have been postponed to 1.1.2. Meanwhile development on 1.2.0 and 2.0.0 continues, for those not aware 1.2.0 will be the first release including gettext and 2.0.0 will bring the latest architectural evolvements as we move towards a leaner codebase with more added features for developers and users alike.”
Read more and <a href="http://community.zikula.org/index.php?module=News&amp;func=display&amp;sid=2971&amp;title=Zikula-111-and-PostNuke-Migration-Distribution-Released" target="_blank" rel="noopener noreferrer">download </a>

Zikula 1.1.1 CMS Migration Release

<img style="max-width:150px" title="miacms" src="https://cmscritic.com/ms-content/uploads/2021/07/miacms-150x150_hbicwe.jpg" />
In this interview with Chad Auld of MiaCMS.. we cover his thoughts on the future and talk shop. You'll find an in-depth interview with never before discussed details about their departure from the Mambo Foundation and the nitty gritty behind the curtain.
Thank you Chad for taking the time to speak with us.
CC: Can you tell us about yourself and include your time on Mambo (if any).
CA: I am a front-end engineer at Yahoo by day, and an open source developer by night. These days I primarily deal with PHP, 
JavaScript, databases, MiaCMS, and other web related technologies.  I have a Master’s degree in Information Systems, a Zend PHP 
Certification, and I am a certified MySQL Professional.  I have a wonderful wife, 3 children, and a cat named JSON ?
I have been heavily involved with the CMS space for about 5 years now. I spent three years on the Mambo CMS team in various roles. These included Project Leader, Lead Core Developer, Director on the Mambo Foundation Board, and Mambo Steering Committee team leader prior to stepping down in February of 2008.
CC: What inspired the formation of MiaCMS and what makes it different from its Mambo roots?
<img title="cauld_gs" src="https://cmscritic.com/ms-content/uploads/2023/08/cauld_gs-147x150.jpg" alt="Chad Auld" />
CA: I talked about this at good length on my blog a while back in an article entitled “Mambo Forked, Meet MiaCMS”.  The team also has an official statement up on the documentation site entitled “The MiaCMS Story”.  The reasoning has not changed and rather than repeat what has already been said I’d direct people to those pages.  In summary though it basically boils down to this…
We felt that the policies, processes, and priorities of the official Mambo Foundation were having a negative impact on the code and the community. Innovation, creativity, and team spirit had all but been 
eliminated. Trolling the internal forums had become depressing to say the least.  Trying to push new code or even fixes to existing code into the core resulted in nothing except for long drawn out fights.  The 
project was at a standstill.
What make MiaCMS different from Mambo?  By design we have less formal policies and procedures, fewer teams and team leaders, and have refocused on a core open source principle… release early, release often.  These changes allow us to move quickly, be more flexible, and actually advance the state of the project.  Talking, planning, and debating are fine, but there comes a time when you have to make a decision and get down to work.
CC: What are your thoughts on the future of Mambo now that Mia has formed with some of the main Mambo developers?
CA: Much of open source software is about giving people a variety of choices and the freedom to utilize, modify, and/or extend 
what works best for them.  What’s perfect for one person or project doesn't always meet the requirements of the next.  So as an open source advocate and from one CMS project to another I welcome the healthy competition.  That being said though I think it is time the Mambo Foundation came clean about the state of their project.  Let me state this as constructively as I can.
Before MiaCMS was formed there were about seven active core developers (Note: by core developers I mean the folks that routinely 
worked on and committed changes to the platform’s PHP, JavaScript, XML, and database code).  Four of those seven core developers, including myself, left in April of 2008 to form MiaCMS.  A fifth former Mambo core developer joined us just a few months later and a sixth developer left the Mambo team around the same time, but did not follow us to MiaCMS. Mambo was left with just one core developer, which as far as we can tell is still the case today.  Yes their project page might list more names, but again I’m talking about people who routinely commit significant code changes.
Since that time they also announced a new Project Leader who has since left, had the Foundation’s President resign, and have yet to fulfill their annual general election obligation, which allows foundation members to vote on new board members. In my opinion the project currently lacks true leadership, consensus on a future vision, and developers.  Mambo was a great project. If I didn't think so I would not have spent thee years helping build it.  Perhaps it can be great again, but right now it would not be my first choice for a CMS.  On a positive note they do still have a fairly active community so not all hope is lost, but they are in need of some serious changes and soon.
Mambo has given birth to a number of very successful forks and served the open-source community well.  That being said the code is 
aging quickly, it is not keeping up with the competition, and for all intensive purposes the project has stalled.  While still on the Mambo team the current MiaCMS team members spent over a year helping to develop the next minor release of Mambo, version 4.7.  When we left to form MiaCMS in April of 2008 it was in the final stages of development and due for release in short order.  MiaCMS forked from Mambo 4.6 since the 4.7 branch had yet to be released under the GPL.  Along with the rebranding work that went into creating MiaCMS the team also re-implemented about 95% of the work we had done for Mambo 4.7.  What MiaCMS delivered as its first release was the equivalent of Mambo 4.7, as it stood at the time, and then some.  MiaCMS has gone on to have 
over 650 important commits to the code repository, several important maintenance releases, and one minor (but in reality fairly major)  release.  The latest branch, 4.8, is pretty much inline with what we had planned for Mambo 4.8 long ago.
The point I am trying to make is that much of the current MiaCMS team is the same team that brought the Mambo community the 4.5.3 through 4.6.3 releases.  We have not diverted from our goal to build a best-of-breed CMS or from our responsibility to do what is best for our users and the community at large.  In fact, we have continued down a very similar roadmap, just under a new name.
During the same time Mambo has had only two fairly minor maintenance releases and a quick look at the Subversion logs for the 4.6 branch will only show about 50 or so commits of any real important since the MiaCMS fork.  The Mambo 4.7 branch is still locked from public access so we can’t do a fair comparison there, but all I can say is it was mostly feature complete when we left and just about stable enough for production.  So one can only speculate on the amount of work that has actually been done on the 
branch since the time of the fork.
Holding elections for a new set of leadership and opening the 4.7 branch up for review are probably the two most important things the project can do at this point.  The branch will either show some real progress or the lack thereof and at least allow interested developers to offer some assistance.
The next major release of Mambo, version 5.0, has been in discussions for ages.  It is often seen as the release they will return 
Mambo to greatness.  What most people don’t know is that Mambo 5 is essentially vaporware at this point.  Several years ago, while still Project Leader, I talked about our direction for Mambo in an article entitled “Baking Mambo”.  We had selected CakePHP as our foundation for a full rewrite of the Mambo core and finally kicked off development.  I spent months focusing on the database portability layer.
I presented the team with an early prototype that had a portability layer in place and a database agnostic installer using Adodb and AXMLS.  Ultimately though, attention refocused on 4.7 and we never got back to version 5 before the fork.  Another quick look at the Subversion logs for the 5.0 branch shows not a single commit has been made since my initial check-in back in September of 2007.  That initial prototype represents perhaps 5% of the overall effort required for a rewrite which means version 5.0 is still 95% incomplete.  That’s if they even stick with the original 5%, but it was written on an early beta version of CakePHP.  CakePHP 1.2 has since had over a thousand commits, several years of development, and an official release leaving the Mambo 5 prototype sorely obsolete.
So what do I think about Mambo?  I think if you liked Mambo, you are going to love MiaCMS.  Converting a Mambo site to MiaCMS is almost as easy as a standard Mambo upgrade.  As a side note it is important to also mention that most of the available Mambo 4.6.x &amp; Joomla 1.0.x templates and extensions will actually work just fine in MiaCMS with either no changes or little changes.
CC: What are the projects main objectives?
CA: To built a state of the art content management system that enables users to create powerful web sites, applications, and 
experiences.  We aim to continue innovating and advancing the CMS by refining the existing code and adding new features as requested by the community.  Simply put, to constantly exceed our users expectations and be the open source CMS of choice.
CC: What would you like to say to naysayer’s who surmise that we do not need another Mambo/Joomla clone?
CA: I’d have to say I agree with them.  We don’t view MiaCMS as a clone.  As I mentioned in an earlier question, we have not 
diverted from our original goals.  We spent years building Mambo and so it only made sense to base MiaCMS on the platform we helped create.  Since the initial fork we have continued to build on that solid base by fixing existing bugs, implementing long standing community wishlist items and other new features, and planning for the next generation of our platform.  As I also stated before the old core is aging, it is in need of a rewrite, and we are already on the case.
Version 4.8 is a solid release and goes a long way toward stabilizing and improving the core.  It will serve the community well while the team focuses on what is next to come.  All three systems are fairly different at this point and it will continue to become more apparent over time.  To be honest we don’t spend much time looking back or looking over our shoulder.  We are MiaCMS, we are proud of the system we have built, and we are excited about the future that lay ahead.
CC: What is the least known feature that separates Mia from its competitors?
CA: We have added and/or improved a number of interesting things recently.  I’ll mention two here.  The first is content 
versioning.  It is hard to imagine that a content management system was lacking this feature, but this has been the case for Mambo since the beginning and has sat on the wishlist for years.  With the 4.8 release I’m happy to say MiaCMS now supports content versioning and it has been well received by the community thus far.  This basically means that users can store as many versions of a content item as they would like, compare old version to the current version, and restore a past version if they so desire.
Secondly, a major decision the team made after forking from Mambo was the decision to rebuilt the entire JavaScript layer of the 
platform.  We’ve done this in phases and rolled out different portions of the rewrite with each new release.  The latest release, version 4.8, completes the rewrite.  Not that it is absolutely perfect or that there will not be some changes in the future.  But we did achieve what we set out to do.  The Mambo core that we initially based MiaCMS on is 7+ years old at this point.  The JavaScript layer is outdated and was in sore need of attention.
MiaCMS’s new base JavaScript architecture is built around the Yahoo! User Interface (YUI) library. The components in this library give  MiaCMS a solid set of cross-browser methods for dealing with things like identifying and accessing parts of the DOM, processing DOM objects, doing animations, and detecting when key DOM events have fired (ex) DOM ready, load, click, etc. The main goals behind formalizing the JavaScript architecture are to provide a consistent interface throughout the system, a reduced dependency on external libraries, enhanced cross-browser support via the graded browser support model, and just more efficient code overall.
The MiaCMS team is working hard to assure that all the JavaScript within the system is properly namespaced and that it follows 
recommended object-oriented conventions. The MiaCMS JavaScript architecture makes use of public, private, and protected variables and functions through the use of object literals and closures.  We feel strongly that the CMS should not simply be a collection of a thousand JavaScript functions scattered throughout.
We strive hard to avoid polluting the browser’s global namespace and avoiding collisions with other JavaScript.  All the JavaScript in MiaCMS lives under the  “miacms” namespace and thus remains isolated from all other JavaScript loaded by extensions, 3rd party JavaScript libraries, etc. We advocate the YUI Library, but because of proper namespacing within the core, 3rd party developers are still free to utilize whatever works best for them in their custom extensions (ex) jQuery, Prototype, etc.
CC: Can you share some sites that use Mia and you feel are successful?
CA: To be honest I don’t have a great list of sites to share.  We don’t track the installations and therefore only know about 
sites we stumble upon or uncover via web searches.  We’d love to build a gallery of sites, but haven’t had the time just yet.  I would 
encourage people to let us know about their sites via the forums for possible inclusion within the official gallery when the time comes.  So while I don’t have a list of sites for you I can tell you our community is growing and our download rates are increasing at a nice rate.
MiaCMS tied for 3rd place in the 2008 Most Promising Open Source CMS category of Packet Publishing’s annual Open Source CMS competition.  We are still a young project and so it is all about getting the word out.  In general we find that once people learn about MiaCMS they are very pleased by the solution we offer.
Here are a few sites I’ve personally been involved with building: 
<a href="http://miacms.org" target="_blank">http://miacms.org</a> 
<a href="http://opensourcepenguin.net" target="_blank">http://opensourcepenguin.net</a> (my personal site)
CC: What are the future plans of the Mia team?
CA: The team keeps an updated roadmap on the documentation site.  We also recently put together a presentation on the “Past, 
Present, and Future of MiaCMS” for the 2008 Thailand Open Source Software Festival.  We have some big news in the pipeline, but we 
aren’t ready to announce anything just yet.  Stay tuned, more to come very soon.
CC: Do you feel that Mia will be impacted at all by the current state of the economy? Why?
CA: MiaCMS is virtual organization and one run 100% by volunteers.  Our overhead is very low and we are lucky enough to have 
talented developers willing to volunteer their time toward the advancement of the platform.  If MiaCMS is affected by the current 
state of the economy I’m guessing it will actually be in a positive manner.  As people look for cost effective replacements for aging, 
proprietary, and expensive systems open source (and in our case free) applications like MiaCMS are very attractive solutions.
CC: If you could change one thing about Mia what would it be and why?
CA: We are a young project.  The team is having fun and learning a lot.  We’re not perfect, but when we encounter issues or kinks in the process we correct them quickly.  The keys are teamwork and communication.  I can’t point to anything one thing that I would 
change right now.  I think the team is pretty happy with the current state of affairs.  We identified the need for a radical change in April of 2008 and we made it (i.e.) the fork.  We learned a great deal from our time with Mambo, which has definitely influenced how we manage the MiaCMS project.
CC: Can you share some future plans and / or upcoming features?
CA: The best to place to see our future plans and/or features would be the official roadmap.  Outside of that let me talk a little 
about life beyond version 4.7.  With version 4.7 behind us the team is now fully focused on the next major release.  We’ll call it version 5.0 for now, but the versioning scheme is likely to change.  Version 5 will be full rewrite of the core building on what we’ve learned from our last 4+ years of CMS development.  The rewrite will target PHP 5+ and most likely MySQL 5+ too.  Support for PHP4 will be dropped.  It’s not that we are simply dropping support for PHP 4, but rather that the rewrite will focus on object oriented techniques and other advancements made to the language in versions greater than PHP 5.
The new framework will be lighter, faster, more secure, more flexible, and easily extendable.  We will re-implement much of the functionality MiaCMS users have come to know and love, but in a way that better prepares us for extending the platform over the coming years.  Users can expect enhanced role based access controls, more flexible content organization (i.e.) removal of two-tier section/category limitation, an improved SEF engine, improvements to the template/theming system, plus much more.
CC: Final thoughts / comments?
Thank you for your interest in <a href="http://miacms.com">MiaCMS</a>.  For anyone that would like more information and/or updates on the project I would encourage them to frequent the official project site, our forums, and/or subscribe to the Twitter feed.

Interview with Chad Auld of MiaCMS

Pligg, the open source Digg clone has been released in release candidate status for version 1. Pligg is incredibly popular and used on a large number of sites to date.
This new release offers the following new features:
New Features.
<ul>
<li>New Template</li>
<li>New Admin Panel</li>
<li>More Spam Prevention Tools</li>
<li>Advanced Search</li>
<li>Category Authors</li>
<li>Admin Help Documents</li>
<li>Story Comment RSS Feeds</li>
<li>Fully Anonymous Mode Module</li>
<li>Votes by IP</li>
</ul>
One of the major issues that was plaguing Pligg based sites was the amount of spam they had to deal with. This new version claims to have address these issues somewhat:
“The first feature is a simple user email activation system. When users sign up to your site you can now require that they verify their email address. This is a rather basic form of spam control, but it does work to stop some spam. Most forum CMS software use this method in combination of CAPTCHA as their primary spam defense. Now Pligg does too.  If a user has an issue activating his account it’s a simple one-click activation from the admin panel to validate their account for them.
The second spam-stopping feature is the Submit Antispam Addon (http://forums.pligg.com/pligg-modules/13972-submit-antispam-addon-v-0-1-a.html) by AnAlienHolakres3. Alien has designed what is probably the most advanced Pligg module ever to be made, and it is a very interesting method for dealing with spam and users who don’t publish quality stories. The module works by limiting the number of submissions an author can add to a site within a given time frame. The more votes the story author receives in a time frame, the more stories he will be allowed to submit. This is probably one of the harsher methods for dealing with spam, but it doubles as a method for promoting only quality stories to your website.”
You can download or read more at <a href="http://www.pligg.com/blog/316/what-to-expect-from-pligg-10/" target="_blank" rel="noopener noreferrer">Pligg's website</a>.

Pligg 1.0.0 RC1 Release

The team over at Umbraco have released version 4 of their content management system.  If you fancy trying out a .NET system, then check it out. We're going to be reviewing it within the coming days.
From their site:
“The ultra solid release of Umbraco is raising the bar in the Web CMS industry. The stability, the clean and user friendly UI, the beautiful and simple Canvas editing, the inclusion of community work, the integration to the .NET framework and the absolutely control over markup is second to none.”
Download at <a href="http://www.umbraco.org/" target="_blank" rel="noopener noreferrer">Umbraco</a>.

Umbraco have released version 4 of their CMS

Best Video Experience

Give your audience the best video experience

#000000

Geeklog 1.5.2 is another maintenance release for the 1.5.x series. The first release candidate is now <a href="http://www.geeklog.net/filemgmt/index.php?id=934">available for download</a>.
This release fixes issues with the story preview and duplicate story ids, the trackback editor, clickable links in text postings, issues with feed updates, and some other minor problems. We've also thrown in some small improvements, e.g. the image quality when using gdlib to rescale images should now be much better than before. See the <a href="http://www.geeklog.net/docs/changes.html">list of changes</a> and the included changelog for details.
Bugfixes
<ul>
<li>Fixed a bug in the story preview where the story content was lost when previewing a story with a duplicate story ID.</li>
<li>The Trackback editor didn't work since the security token was missing from the editor template.</li>
<li>Fixed issues with clickable links in plain text postings.</li>
<li>Fixed various problems with updating feeds, e.g. when changing topic permissions.</li>
</ul>
Fixes in the bundled Plugins
<ul>
<li>Calendar: You couldn't add a new event to your personal calendar.</li>
<li>Links: Changing a link's ID to one that was already in use overwrote the other link.</li>
<li>Polls: Changing a poll's ID created a new poll. Also fixed an SQL error when the poll question contained single quotes.</li>
<li>Static Pages: Saving a static page changed the owner to the user who saved it.</li>
</ul>
Other Changes
<ul>
<li>Improved image quality when using gdlib to rescale uploaded images.</li>
<li>Theme changes are documented in the <a href="http://www.geeklog.net/docs/theme.html#changes">theme documentation</a>, as usual. There are 4 bugfixes (one of which is in the templates for the Polls plugin) that should be applied to all themes for the 1.5.x series.</li>
</ul>

Geeklog 1.5.2 Bugfix and Maintenance Release

Mollom, the comment spam blocking venture by Dries Buytaert (founder of the Drupal Content Management System) has now blocked over 25 million spam attempts since it came to be 10 months ago.
Mollom is also now available for Drupal, WordPress, Radiant and Silverstripe using plugins and is  a very nice project. We've used it in the past and continue to do so now and find it quite capable. According to Dries Buytaerts' blog.. Mollom is now protecting approximately 5000 websites and has an efficiency rating of 99%.
Not bad for something that has only been around for under a year.

Mollom has now blocked over 25 million spam attempts

We are constantly exposed to content management systems day to day and have a huge number of them (and it's growing too!) in our CMS list.
We have noticed more and more that people are having a hard time deciding how to choose the right CMS for the job.
It's not an easy task for some people, and for that reason we've created this article with the hope that it can free some of you from feeling overwhelmed.
When you first realize you need/want a CMS, there is the fear that the CMS you select will:
<ol>
<li> Suck your time and money into a spinning vortex.</li>
<li>Suck your page rank down the tube due to poor optimization.</li>
<li>Just plain suck.</li>
</ol>
How do you avoid this?
Start by Following these DO and Do NOT tips:
The DO NOT List:
<ol>
<li>Do NOT pick your CMS based on the fact that you found a pretty theme for it. Themes can be created quickly and easily.. and quite frankly, choosing based on this factor alone is bound to give you a headache.</li>
<li>Do NOT just buy something without trying it first. You wouldn't do it with a car (we hope) so don't do it with your content management system either. We can pretty much guarantee that if you approach a vendor and tell them you are curious and interested but want to demo first, they will make it happen or risk losing your business.</li>
<li>Do NOT throw tons of money (cause we all have tons of money right?) at a developer and have them make something custom just for you. It's not worth the investment.. there are plenty of well supported systems out there and it's much better to have others who know the product as support options rather than just one person.</li>
<li>Do NOT assume that because the CMS costs money, it must be better than it's Open Source alternatives. While this MAY be the case in SOME instances.. it is most certainly not always the case. There are a large number of Open Source CMS products on the market that are much better than some of the commercial offerings.. and vice versa.</li>
<li>Do NOT go to the Drupal forums and ask them if WordPress or Drupal is the best.. you will get a biased answer. This is about as intelligent as walking into a Ford dealership and asking them if they think Ford is better than Chevrolet.</li>
</ol>
The DO List:
<ol>
<li>DO take your time and explore your options. There are TONS of resources out there (this is the internet for pete's sake!) that can help you in your search. We think This Site is the best. (like how we slid that in there?).  If you have a hard time finding help, then ask and we'll direct you.</li>
<li>DO try the product first. We don't recommend demos as they are already installed. It's best to download the package, find a cheap host somewhere and try to install it and see what happens. If you get lost somewhere and need help.. hit the forums for the applicable package. You can start your hunt for the perfect product by reviewing this cms list or reading some reviews.</li>
<li>DO ask other webmasters of sites that you like. Some may or may not be willing to tell you what (if any) CMS they are using but it never hurts to ask.  Frequest webmaster forums or un-jaded sites such as ours!</li>
<li>DO remember to fully research the product you are considering.. explore some themes, plugins and see how the community treats questions from new users. This will give you a good feel for the product.</li>
</ol>
So now you know what we think you should do and shouldn't do. Let's cover some additional tips.
<ol>
<li>Make sure that you check to ensure that whichever platform you are evaluating (PHP, .NET, JAVA) your hosting provider, if applicable, supports it.</li>
<li>Check the Showcase pages (if any) for the product you are considering. This is a great help in seeing what the potential of the product is.
Here are a few of the more popular CMS' showcase pages:
<a href="http://silverstripe.org/community-showcase/">Silverstripe Community Showcase</a> <a href="http://drupalsites.net">Drupal Sites Showcase</a> <a href="http://wordpress.org/showcase/">WordPress Showcase</a></li>
</ol>
That should give you a fair start. We're sure there are plenty of other items that could be added to this list. By all means, please contribute!

How to choose a CMS that doesn't suck.

During this survey, they identified three key trends that they feel will impact Web Content Management in 2009.
In the survey of 83 U.S. web content management customers, Sitecore found the number of organizations implementing Web 2.0 functionalities increased by over 250 percent.
Enterprises are finding that it is important that they make it easier and quicker for people to share news, have discussions and get information via social networking tools. The ability of Sitecore’s Web CMS to effortlessly add applications such as wikis, forums, blogs and surveys has helped its customers meet their social computing goals. Although Web 2.0 has been a recurring topic in the press, Sitecore’s survey now indicates integration with websites is rapidly growing and expects that it will see continued strong growth in 2009.
Another growing trend is the integration of portals with public websites. The predominant type of portal being integrated with Sitecore’s public websites was Microsoft’s SharePoint, with a 100 percent growth rate in portal to public website integrations noted. While content sharing is a stated goal of many web projects, to see such a high growth rate of actual implementations indicates the trend is now established.
The final key trend was the use of web content management to integrate e-commerce tools into websites. The percent of such integrations increased 39% year to year, with the two most frequent e-commerce solutions used being Microsoft Commerce Server and InSite Commerce.
Ecommerce is becoming increasingly popular as is the need for B2B as opposed to business to customer marketing. In fact, there has been a drastic increase in the profit margins of most ventures that focus on business to business transactions.

Three Key Trends That Will Impact Web Content Management in 2009

Last week, Nicole Denil of <a href="http://www.sitemasher.com" target="_blank" rel="noopener noreferrer">Sitemasher</a> was kind enough to set aside some time to walk us through a complete demonstration of Sitemasher and its functionality. We were so impressed that we wanted to spread the word about this fine content management system.
For those of you that have never heard of Sitemasher, read<a href="http://www.sitemasher.com/the-story" target="_blank" rel="noopener noreferrer"> The Sitemasher Story</a>.
Sitemasher is unique in that it allows you to create an entire website with minimal experience and no requirement to know coding or css. This is huge for those of you that struggle to understand the intricacies and/or simply do not have the time.
Want to add youtube videos? You can literally search and add directly from their interface without ever going to youtube.
Don't just take our word for it though.. you can quite literally demo the entire system on their website and we highly recommend you <a href="http://dashboard.sitemasher.com/register.aspx" target="_blank" rel="noopener noreferrer">try it</a>.
Not convinced yet? Then watch this video:

Thanks again to Nicole for opening our eyes to the power of Sitemasher. We hope you have a chance to try it out.

Sitemasher, making it easy to get things done.

The latest release candidate of the upcoming Umbraco 4 release has been unleashed for public consumption.
According to the <a href="http://umbraco.org" target="_blank" rel="noopener noreferrer">Umbraco</a> website:
<blockquote>
The final release candidate of Umbraco 4 is out and <a href="http://www.codeplex.com/umbraco/Release/ProjectReleases.aspx?ReleaseId=22030" target="_blank" rel="noopener noreferrer">available for download at CodePlex</a>.
The focus the past week have been on stability and fixing any serious issues. The last Release Candidate added error when deleting files and macros via the context menu and we’ve made sure that all that is working again.
We’ve also polished the Membership Provider, so that it’s 100% compatible with the umbraco content and members for security trimming. Word is also 100% compatible with Umbraco Content Channels including uploading images and  charts and speaking of Content Channels, it also supports the umbraco tagging control now.
The internal search index have been upgraded to Lucene 2.0 and it’s better at auto correcting any errors and you can  now also activate internal search dialog by pressing SPACE in the search box. Apart from this we’ve made a good bunch of UI polishing and upgraded jQuery to 1.3.1.
</blockquote>
<blockquote>
We’re confident that we’ll have a release of Umbraco 4 on Friday – YAY!
</blockquote>
Be sure to help them test it out if you are a user so they can have their final release ready for the upcoming weekend!

Umbraco Content Management System 4 RC 3

Founded by Ali Fazelzadeh, Jaws is a small content management system that is capable of some pretty cool functionality. With some very interesting addons and high ease of use, it's definitely a platform worth looking at if your goal is to design something simple and fast. Today we're going to show you what makes it unique amongst the other industry players in this Jaws CMS Review.
To get started, you need to download the appropriate package from the <a href="http://www.jaws-project.com/" target="_blank">Jaws Project </a>website, extract it to your host and visit your domain, you will be presented with the following screen:
<img src="https://cmscritic.com/ms-content/uploads/2023/08/jaws11.jpg" alt="Jaws CMS Review" />
After selecting your language:
<img src="https://cmscritic.com/ms-content/uploads/2023/08/jaws2.jpg" alt="Jaws CMS Review" />
An interesting security procedure above, requires you to create a file called key.txt with the displayed code in it and upload it to your /install directory before the software will allow you to install. Once you've done this, you may proceed below:
<img src="https://cmscritic.com/ms-content/uploads/2023/08/jaws3.jpg" alt="Jaws CMS Review" />
As usual, if you see all green.. you get to continue:
<img src="https://cmscritic.com/ms-content/uploads/2023/08/jaws4.jpg" alt="Jaws CMS Review" />
Once you've got your database details configured, you move on to entering your admin details:
<img src="https://cmscritic.com/ms-content/uploads/2023/08/jaws5.jpg" alt="Jaws CMS Review" />
Then proceed to:
<img src="https://cmscritic.com/ms-content/uploads/2023/08/jaws6.jpg" alt="Jaws CMS Review" />
Jaws uses gadgets which you can place anywhere within your layout (drag and drop style).. this option gives you a chance to enable a default gadget.. I would recommend the ‘Static Page' one.
<img src="https://cmscritic.com/ms-content/uploads/2023/08/jaws7.jpg" alt="Jaws CMS Review" />
Now you have the option to view the site or enter the control panel. Since your site will be completely void of any gadgets or content at the moment.. I'd recommend you enter the control panel first:
<img src="https://cmscritic.com/ms-content/uploads/2023/08/jaws8.jpg" alt="Jaws CMS Review" />
Note the section entitled “Disabled Gadgets”, this is where you get to select which ones you wish to install. Each of these gadgets once enabled will add a new icon to the control panel with which you can administer them. You can also then add them to various blocks on your new page using the Layout icon in the control panel.
<img src="https://cmscritic.com/ms-content/uploads/2023/08/jaws9.jpg" alt="Jaws CMS Review" />
To enable, just scroll through the list above and click install. Once you've selected the ones you want to install.
Once installed, you'll see the new icons created in the control panel:
<img src="https://cmscritic.com/ms-content/uploads/2023/08/jaws111.jpg" alt="Jaws CMS Review" />
You can then move to the Layout icon which will allow you to begin placing gadgets and applying a theme to your site:
<img src="https://cmscritic.com/ms-content/uploads/2023/08/jaws10.jpg" alt="Jaws CMS Review" />
<img src="https://cmscritic.com/ms-content/uploads/2023/08/jaws12.jpg" alt="Jaws CMS Review" />
Once you have the applicable gadgets added, you will be able to check out your new site and see how it looks.
You can find a few sites running Jaws at the <a href="http://wiki.jaws-project.com/doku.php?id=jaws:showcases:important" target="_blank">Jaws Showcase</a> page.
Jaws is what it claims to be.. a user friendly CMS.
It is not something I could see myself using to build massive corporate websites.. but it is something I could see using for a personal site or to create a quick web presence. I like the gadget concept and think that as the project matures, it would be nice to see these get a bit more refined.
They have recently added a forum to their project page which was desperately needed and it's seeing a fair amount of activity.
There is a lot of potential in Jaws.. don't go to it expecting perfection because you won't find it.. but do go to it if you are willing to contribute and help enhance it into something amazing.
Overall Ratings:
Community 7/10 – With the addition of the forums, it is growing rapidly.
Expandability 7/10 -There is a ton of potential here to create new gadgets and build upon the existing functionality.
Themability 7/10-Easy to theme with a reasonable selection of themes installed by default
Useability 8.5/10 – Very easy to use, highly recommended for new users or people looking to create a simple homepage, blog or web presence.
<h2>Overall Score: 7/10</h2>

Jaws CMS Review

Power your CMS on AWS

Manage your websites & apps in the most trusted cloud.

#ffffff

Explore a wide range of informative articles, insights, and industry updates. Stay informed and ahead of the curve with our diverse collection of news and posts covering the latest trends and developments in the industry. Page - 250