About Joomla!/Mambo

http://creativecommons.org/licenses/by-sa/2.5/ About Joomla!/Mambo <a class="wikilink" href="http://swik.net/Mambo">Mambo</a> is a <a class="wikilink" href="http://swik.net/License:GPL">GPL</a> licensed Web Content Management System originally developed by Australia-based <a class="wikilink" href="http://swik.net/Miro-International">Miro International</a>, a provider of software and services for web publishing and collaboration. Since August of 2005, Mambo has been run by a non-profit Foudnation—the Mambo Foundation, who protects and promotes the Open Source project. Mambo’s architecture is based on <a class="wikilink" href="http://swik.net/PHP">PHP</a> and <a class="wikilink" href="http://swik.net/MySQL">MySQL</a>. In late 2005, <a class="wikilink" href="http://swik.net/Mambo">Mambo</a> a group of develoeprs decided to depart the main project and forked the code base to create <a class="wikilink" href="http://swik.net/Joomla">Joomla</a>. Mambo’s primary design goal is ease of use and they have accomplished this goal with a simple user interface and functionality targeted toward managing corporate web sites and customer extranets. Mambo is quick and easy to set up – especially if the customer is willing to use the presentation templates that come with the software. These templates are fairly design-neutral and have the potential to work nicely with different corporate branding elements. <h1>Content Production/Editing</h1> Content creators can create static pages and content items using the <a class="wikilink" href="http://swik.net/TinyMCE">TinyMCE</a> in-page <a class="wikilink" href="http://swik.net/WYSIWYG">WYSIWYG</a> <a class="wikilink" href="http://swik.net/HTML-editor">HTML editor</a>. The major difference between static pages and content items is that content items are slightly more structured with an introductory text field, which is useful for listing pages. Images are associated with assets through the user interface rather than <a class="wikilink" href="http://swik.net/HTML">HTML</a> references. This helps Mambo maintain these relationships and prevent broken image references. Users have a choice of editing content through the administrative interface or directly on the site. The general guideline is to reserve use of the administrative interface for trained power users to prevent inadvertent mis-configuration. In-site editing is sufficient to make textual changes and is foolproof but does not give access to metadata and advanced publishing features. <h1>Management</h1> Assets within a Mambo site can be in one of two states: published or unpublished. The absence of content versioning makes changes to published pages immediately visible upon save. However, an author is able to preview from the edit page to verify changes before saving. Mambo has a simple locking mechanism to prevent users from trying to edit the same asset simultaneously. Assets are placed on a site by tagging them for the home page, associating them with menus that drive the site’s navigation, or assigning metadata and other categories for dynamic listing pages. <h1>Presentation</h1> Mambo has a skins framework (called templates) that manages customizations to the presentation templates and allows an administrator to toggle between skins. Installing a skin is easily done through the administrative interface. Templates are written in pure <a class="wikilink" href="http://swik.net/PHP">PHP</a>, unlike the proprietary tagging languages that many other <a class="wikilink" href="http://swik.net/CMS">CMS</a> use. This is an advantage of lessening the amount of specialized skill required to customize and manage a Mambo site. The Mambo and Joomla communities have several websites that host downloadable skins and there is an active marketplace for custom skin development. Mambo has a flat URL structure and relies on query strings to request specific pages. There are some work-arounds available to create search-friendly URLs but they are not core to the product. Mambo comes with an internal search engine that can search through page-based content on the site. Other visitor-facing functionality, such as blogs, a shopping cart, and a photo gallery can be added by downloading and installing modules (called mambots) through the management user interface <h1>Community and Support</h1> While the fork between <a class="wikilink" href="http://swik.net/Joomla">Joomla</a> and <a class="wikilink" href="http://swik.net/Mambo">Mambo</a> fragmented the community, the original community was large and vibrant enough that both new communities are healthy. The Joomla project, in addition to taking a majority of core team members is also drawing a sizable portion of the user and third party developer community. Mambo has backfilled with a new core development team. There are several Mambo and Joomla related third party sites that discuss Mambo and innovative ways to use it including MamboXchange and JoomlaForge which are like SourceForge for modules. The Source is a Mambo Community and downloads site run by the Foundation. Both Mambo and Joomla have active forums and do a decent job of notification of security vulnerabilities. The Joomla user forum is excellent with over 1,000 posts per day and a well organized moderator community. Forum participants are generally very polite and helpful, a phenomenon that some attribute to the policy of using one’s own picture in the forum profile which inserts a degree of personal accountability for what is said. information Mambo Joomla oferta2 Wed, 25 Jan 2006 13:45:31 -0800 Wed, 06 Jun 2007 09:33:54 -0700