Joomla

Joomla (/ˈdʒuːm.lɑː/), also spelled Joomla! (with an exclamation mark) and sometimes abbreviated as J!, is a free and open-source content management system (CMS) for publishing web content on websites. Web content applications include discussion forums, photo galleries, e-Commerce and user communities and numerous other web-based applications. Joomla is developed by a community of volunteers supported with the legal, organisational and financial resources of Open Source Matters, Inc.

Joomla
Screenshot
Joomla! 3.x administration backend
Developer(s)Open Source Matters, Inc. and the Joomla community
Initial release17 August 2005 (2005-08-17)
Stable release
3.9.24 / 12 January 2021 (2021-01-12)[1]
Preview release
4.0.0 beta 6 / 7 January 2021 (2021-01-07)[2]
Repository
Written inPHP
Operating systemUnix-like, Windows, Linux
Size13.3 MB (compressed) 35.5 MB (uncompressed)
TypeContent management framework, Content management system
LicenseGPLv2
Websitewww.joomla.org

Joomla is written in PHP, uses object-oriented programming techniques and software design patterns, stores data in a MySQL database.[3] It has a software dependency on the Symfony PHP framework. Joomla includes features such as page caching, RSS feeds, blogs, search, and support for language internationalisation. It is built on a model–view–controller web application framework that can be used independently of the CMS.

Over 6,000 extensions are available from the Joomla website,[4] and more are available from other sources. As of 2020, it was estimated to be the third most used open-source CMS on the Internet, after WordPress and Shopify.[5]

Overview

Joomla has a web template system using a template processor. Its architecture is a front controller, routing all requests for non-static URIs via PHP which parses the URI and identifies the target page. This allows support for more human-readable permalinks. The controller manages both the frontend, public-facing view, and a backend (GUI-driven) administration interface. The administration interface (a) stores management and content information within a database, and (b) maintains a configuration file (configuration.php, usually located in the file system root of the Joomla installation). The configuration file provides the connection between the server, database and file system and facilitates migrating the website from one server to another.[6]

The backend interface allows website operators to manage users, menus, extensions[note 1] and web content.

Joomla is designed to be used by people who have basic website creation skills and requires an Apache–MySQL–PHP, or similar, software stack.[note 2] Commercially based web hosting services may include control panels for automatically installing Joomla for their customers. Joomla may be used to create localhosted-web applications that run on a range of AMP servers.[3]

Risk management, backup and recovery are the website operator's responsibility. Joomla does not have website backup or recovery facilities built into the core CMS; third party-written products (as installable extensions or in standalone products) exist, the most popular of these are developed by Akeeba Ltd.

Other software facilities (whether as natively installable extensions utilising the Joomla framework or via "software bridges") extend a website's range of applications to include discussion forums, photo galleries, e-Commerce, user communities, and numerous other web-based applications.

History

2005-2007

Joomla was the outcome of a fork of Mambo on 17 August 2005.[8] At that time, the Mambo name was a trademark of Miro International Pvt. Ltd, who formed a non-profit foundation with the stated purpose of funding the project and protecting it from lawsuits. The Joomla development team claimed that many of the provisions of the foundation structure violated previous agreements made by the elected Mambo Steering Committee, lacked the necessary consultation with key stakeholders and included provisions that violated core open source values.[9]

Joomla's original co-founders, Andrew Eddie, Brian Teeman, Johan Janssens, Jean-Marie Simonet et al.,[10] established Open Source Matters, Inc. (OSM) to distribute information to the software community. Project leader Eddie wrote a letter that appeared on the announcements section of the public forum at mamboserver.com.[11] Over one thousand people joined OpenSourceMatters.org within a day, most posting words of encouragement and support. Miro CEO Peter Lamont responded publicly to the development team in an article titled "The Mambo Open Source Controversy—20 Questions With Miro".[12] This event created controversy within the free software community about the definition of open source. Forums of other open-source projects were active with postings about the actions of both sides.

In the two weeks following Eddie's announcement, teams were reorganised and the community continued to grow. Eben Moglen and the Software Freedom Law Center (SFLC) assisted the Joomla core team beginning in August 2005, as indicated by Moglen's blog entry from that date and a related OSM announcement.[13][14] The SFLC continues to provide legal guidance to the Joomla Project as one of OSM's partners.[15]

On 18 August Eddie called for community input to suggest a name for the project. The core team reserved the right for the final naming decision and chose a name not suggested by the community. On 22 September the new name, Joomla!, was announced. It is the anglicised spelling of the Swahili word jumla, meaning "all together" or "as a whole" that also has a similar meaning in at least Amharic, Arabic and Urdu. On 26 September, the development team called for logo submissions from the community and invited the community to vote on the logo; the team announced the community's decision on 29 September. Beginning in October 2005 guidelines covering branding, licensing and use of the registered trademark were published.[16]

2008-2011

On 28 January 2008 the first major revision to Joomla was announced: Joomla 1.5.

Joomla 1.5 was popular but criticised for its inflexible and limited approach to access control.[17] Independently of the project, Andrew Eddie and Louis Landry created a company called JXtended[18] to continue the development of Control—an ACL component—that could integrate with Joomla 1.5. In July 2009 Eddie presented his ideas[19] to the Joomla User Group Brisbane.

In July 2009 of that year, the Joomla project announced a restructuring of its management: a new Joomla Leadership Team replacing the Core Team that had originally led the project. This redefined the role of the team leading the project and structured it more around community involvement in events, the Google Summer of Code projects and other activities; the intention of the new approach to team-building was also an effort to increase community participation in the development process instead of relying upon a small group of coders to do most of the work.

According to Google Trends, interest in Joomla peaked around the period 2009–2010.[20] In January 2011—largely as the result of the collaboration between Eddie and Landry—a second major revision of Joomla was released: Joomla 1.6.[21]

Prior to the stable release of Joomla 1.6, Eddie relinquished his roles on OSM's board and project leadership;[22] Louis Landry announced his retirement from the project the following year.[23] Following Eddie's departure, in September 2011, OSM sought feedback from the community, including the possibility of constituting the governing body under a new name, to restructure the board's membership and project leadership.[24]

Molajo

In 2010, with preparations for Joomla 1.6 nearly completed, Amy Stephen, Klas Beric, Marco Barbosa, Matt Thomas et al. started a project to refactor the Joomla code. Code-named Molajo (an anagram of Joomla), the group felt that the existing Joomla CMS hindered end-users and developers adopting Joomla because (a) the Joomla CMS did not offer a range of packages containing a themed sets of web applications—like other CMS products had been doing for some time—and (b) the traditional MVC approach decreased developers' productivity in creating new components for Joomla.

Community reaction to Molajo was mixed. Some commentators claimed that it was a fork of the Joomla CMS—a claim strongly rejected by Stephen—while others contended that its activities would undermine the future of the Joomla CMS.[25][26] Against these headwinds, Molajo made its public debut at the J and Beyond conference in The Netherlands in 2011.[27]

Lacking support from OSM, an enthusiastic following from the Joomla community and unable to progress beyond pre-Alpha status, Molajo collapsed around the middle of 2015.[28]

2012-2014

In January 2012 another major revision was announced: Joomla 2.5 (essentially bringing together the two previous minor releases in the preceding year). Joomla 2.5 brought much sought-after enhancements and a new API making it easier for novice users, additional multilanguage capability and the ability for users to update with "one-click".

Shortly after the release of Joomla 2.5, work was under way on the Joomla 3.x. Joomla 3.x was focused on mobile-friendly websites on the front-end, as well as a more intuitive back-end. With greater ease in site navigation and a more user-friendly means of editing Joomla site content, Joomla 3.x became the most popular version of the CMS eventually making all previous versions obsolete.[29]

In March 2014, after seeking community feedback and a submission from the Production Leadership Team, a newly constituted OSM board approved changing the licensing for the framework from GPLv2 to LGPL.[30][31] Although the proposal only affected the licensing of the framework and not the CMS, the decision sparked a fierce debate within the community.[32][30] In the end, the framework did not adopt LGPL and is still licensed under GPLv2.[33]

In August 2014, the Joomla CMS development team released a plan for new version releases.[34]

Towards the end of 2014—three years after calling for feedback about ways to reorganise the project[24] and with Joomla 3.x into its fourth minor revision—the community discussed the leadership structure changes.[35] Eddie, although no longer an active contributor to the project, argued that the code for Joomla 3.x was "too fat and heavy to maintain with the current level of contribution"; he recommended mothballing the current CMS series and develop a less cumbersome Joomla 4. Eddie went further to criticise OSM's vision, entrepreneurship and management of the project. Other commentators also expressed their opinion that OSM had become dysfunctional.[36]

2015-2018

Criticism mounted about the plan[34] for future development of the Joomla CMS. An opinion written in May 2015 by Nicholas Dionysopoulos (founder of Akeeba Ltd.) shared some of Eddie's earlier observations about OSM lacking vision, entrepreneurship and its ability to manage the project.[37] Dionysopoulos disagreed with Eddie about the major cause of problems with Joomla 3.x; it was Dionysopoulos' view that the cause of most problems with Joomla 3.x lay within "the processes of Joomla! the organisation".

Dionysopoulos' views gathered momentum within the community and led to the formation of the Joomla 4 working group (which later became the Joomla X working group).[38][39][40]

In March 2017 the project announced the retirement of Joomla 3 and unveiled its plans to develop Joomla 4.[41] This effectively brought an end to the work of the Joomla X working group (although it would be another two years before that Joomla X working group's activity was placed in "archived" status).[42]

In an effort to improve the relationship with the community the development team revised the 2014 plan and, in June 2018, produced a new roadmap with the expectation that Joomla 4.0 would be released in a stable form before the end of 2018.[43] During the period 2017-2018 the developers created six alpha test releases for Joomla 4.[44]

2019-2020

In January 2019 the developers released an updated plan revising previously announced estimated time frames;[45] the roadmap was revised several times during 2020.[46]

Community concerns intensified about the handling the Joomla project—two years after announcing plans to retire Joomla 3 (but having already released two minor versions with plans for a third)—and by the end of 2019 a further six alpha test releases of Joomla 4 were produced for public discussion.[47] On one hand some people questioned whether the community had lost its influence in driving the project while, from the developers' viewpoint, the other side defended the project by observing that things would be more productive if the community had been more actively engaged in testing, rather than criticising, the alpha releases. These discussions revealed a growing sense of division between developers on one side and end users on the other.

A lengthy debate, started in March 2019 and initially focused on the aesthetics and usability of the Joomla 4 backend interface, highlighted an overall sense of disappointment with management and progress of the project.[48] Although the debate was weighted heavily on criticising the backend aesthetics, people on all sides of the discussion aired their dissenting opinions about why the Joomla 4 project had become distracted by feature creep, software bloat, eventual cost overrun and lack of trust.

Against a background of unrelenting criticism from within the community and declining popular interest in Joomla at the time[20] a conference was held in January 2020 to develop a strategy for the future.[49] The conference identified several key areas for further work but basically accepted the premise that faults related mainly to the project's organisational framework rather than the quality of the product .[50]

Joomla: code, community, culture

The COVID-19 pandemic impacted Joomla planned events resulting in the cancellation of the main world-wide conferences; J and Beyond was arranged as a 24-hour live stream event in May. In his welcoming address to J and Beyond OSM President Brian Mitchell acknowledged the impact of the global crisis on Joomla. Mitchell outlined his vision to meet the challenges confronting the Joomla project. The project needed to concentrate efforts, Mitchell said, to ensure that the three essential parts of the project—the code, community and culture—worked together as a whole.[51]

Version history
Joomla versions[52]
Series Released as Release date Supported until Main feature(s) Notes
1.0 & 1.5 1.0 22 September 2005 22 July 2009 Rebranded release of Mambo 4.5.2.3 that combined other bug and moderate-level security fixes. Written for PHP 4. July 2009 was the official end-of-life of Joomla 1.0.[53]
1.5[54] 22 January 2008 31 December 2012 Overhauled GUI interface, templates, limited "legacy mode" support.[55] Written for PHP 5. First long-term support (LTS) version although not backwardly-compatible with its predecessor. Such LTS versions were to have been released every three major or minor releases and supported until three months after the next LTS version is released; this approach was not followed in practice.[56] September 2012 was the official end-of-life of Joomla 1.5.[57][58]
1.6, 1.7 & 2.5 1.6[59][60] 10 January 2011 August 2011 Added full access control list functionality plus, user-defined category hierarchy, and admin interface improvements.
1.7[61][62] 19 July 2011 February 2012 Enhanced security and improved migration tools.
2.5[63] 24 January 2012 31 December 2014 New "Smart Search" component, added support for using Microsoft SQL Server as a database backend, added user notes, additional enhancements and security improvements. Second LTS release. Originally this release was to be named 1.8.0, however the developers announced August 9 that they would rename it to fit into a new version number scheme in which every LTS release is an x.5 release.[64][65] December 2014 was the official end-of-life of Joomla 2.5.[66]
3.x 3.0[67] 27 September 2012 April 2013 New default templates based on Bootstrap, added support for using PostgreSQL as a database backend, drops support for PHP 5.2. Originally, this version was supposed to be have been released in July 2012; however, the January/July release schedule was uncomfortable for volunteers, and the schedule was changed to September/March releases.[68] On 24 December 2012 it was decided to include an unforeseen addition to the 3.x series to improve the development life cycle and extend the support of LTS versions.[69]
3.1[70] 24 April 2013 October 2013 Article tagging.[71]
3.2[72] 6 November 2013 October 2014 Content versioning for articles. Because of a PHP requirement change in Joomla 3.3, extended security support was provided for 3.2 for six months after 3.3's release.[73]
3.3[74] 30 April 2014 February 2015 Improved password hashing, microdata support, removing dependencies to MooTools. On 25 April 2014, the Joomla Production Leadership Team announced that it started following 'Semantic Versioning Scheme' for new Joomla builds. The earlier LTS (Long Term Support) and STS (Short Term Support) lifecycle policy was cancelled.[75][76] Joomla version 3.3.1 was the first version released under the new development strategy.[77]
3.4[78] 24 February 2015 March 2016 Improved security advancements, Composer integration and Google's No CAPTCHA reCAPTCHA. Extensive security revisions were rolled out in October 2015 with the release of v3.4.5.
3.5[79] 21 March 2016 July 2016 Changes to admin interface (including some ability for drag and drop images). Added PHP 7 support. Added an opt-in feature to upload anonymous server statistics about environments where Joomla is being used.
3.6[80] 12 July 2016 April 2017 Improvements to UX, software updates.
3.7[81] 25 April 2017 September 2017 Custom Fields, Improved Workflow, Multilingual Associations Manager, Backend Menu Manager, improved update system, cache systems and package/extension management and further UX improvements.
3.8[82] 19 September 2017 October 2018 Improved Routing System, Joomla 4 Compatibility Layer, optional installable sample data, code improvements and encryption support (using Sodium extension on PHP 7.2, or via sodium_compat polyfill for lower supported versions).
3.9[83][84] 20 October 2018 [note 3] ‘Privacy Tool Suite’, primarily in response to the enactment of new privacy and data retention laws and regulations, in particular, the GDPR.
3.10 To be determined [note 4] Expected to be the last scheduled minor release of the Joomla 3.x series
4.x 4.0 To be determined Support for PHP 5 and Microsoft SQL Server has been removed.
  Obsolete
  Superseded release
  Current release
  Future release

Templates

There are two types of templates used in the Joomla CMS: frontend templates and backend templates. The frontend template presents the website to the user viewing the its content. The backend template presents a panel of controls for website administration.

Templates are installed as extensions to Joomla and may be customised with source code overrides and/or CSS.[85]

Standard templates are included upon installation while other, third-party templates can be installed later. In general, templates designed for each major version of Joomla are not interoperable with other major versions of Joomla. The following table lists the standard templates installed with each major Joomla release.

Joomla templates by major release
Used in versions Frontend template Backend template
1.0
madeyourweb
rhuk_solarflare_ii
joomla_admin
1.5
beez
ja_purity
rhuk_milkyway
khepri
1.6, 1.7 & 2.5
atomic
beez_20
beez5
bluestork
hathor
3.x
beez3
protostar
hathor
isis
4.0
cassiopeia
atum

Development and support

Developers

Joomla is maintained as an open source project by a community of volunteers and licensed under the GNU General Public License on an "as is" basis, without any warranty of any kind including implied warranties of merchantability and fitness for a particular purpose.[86] The source code is maintained at GitHub. The top two most popular public forums for discussing Joomla and seeking technical advice are at https://forum.joomla.org and https://joomla.stackexchange.com.

Conferences

J and Beyond is a conference largely aimed at Joomla developers and site integrators and is hosted in Europe around May each year.

Awards
Year Award[87] Category
2005 UK Linux & Open Source Awards Best Linux / Open Source Project
2006 Packt Open Source Awards Best Open Source CMS
UK Linux & Open Source Awards Best Linux / Open Source Project
2007 Packt Open Source Awards Best PHP Open Source CMS
2008 Packt Open Source Awards
  • Open Source CMS Most Valued Person — Personal award: Johan Janssens
  • 1st Runner-up Best Open Source CMS
  • 1st Runner-up Best Overall Open Source CMS
2009 Packt Open Source Awards
  • Open Source CMS Most Valued Person — Personal award: Louis Landry
  • 1st Runner-up Packt Hall of Fame CMS
  • 2nd Runner-up Best Open Source CMS
2010 Packt Open Source Awards 2nd Runner-up Hall of Fame CMS
2011 Packt Open Source Awards Best Open Source CMS
2014 CMS Critic People's Choice Awards Best Open Source PHP CMS
2015 CMS Critic People's Choice Awards Best Free CMS
2016 CMS Critic People's Choice Awards Best Free CMS
2017 CMS Critic People's Choice Awards Best Free CMS
2018 CMS Critic People's Choice Awards Best Free CMS
2019 CMS Critic People's Choice Awards Best Free CMS

Notes
  1. extensions are sub-classed as components, plugins, modules, templates and languages; some extensions are included with the "core" CMS package while other (usually third party-developed) variations or enhancements, can be optionally installed later
  2. Joomla can be installed under the Microsoft Windows operating system using the Microsoft Web Platform Installer which automatically detects and installs dependencies such as PHP or MySQL[7]
  3. nominal "support" for version 3.9 ceases with the release of version 3.10
  4. nominal "support" for version 3.10 ceases two years after the release of version 4.0

See also

References
  1. "Joomla 3.9.24 Release". 12 January 2021. Retrieved 12 January 2021.
  2. "Joomla 4 Beta 6 and Joomla 3.10 Alpha 4 are here: test them now!". 7 January 2021. Retrieved 11 January 2021.
  3. Joomla Technical Requirements
  4. "Joomla! Extensions Directory". extensions.joomla.org. Retrieved 30 November 2020.
  5. "Market share yearly trends for content management systems". Retrieved 26 November 2020.
  6. "How to Move a Joomla Site to a New Server". hostup.org. Retrieved 28 April 2019.
  7. "The Easy Way To Install PHP on Windows". SitePoint. Retrieved 20 November 2009.
  8. Eddie, Andrew (8 April 2006). "Joomla! Developer Blog: So Really—What's the Difference". Archived from the original on 1 September 2006. Retrieved 30 November 2020.
  9. "Joomla Forum Discussion by Development Team members and Community". 7 May 2007. Retrieved 7 May 2007.
  10. Teeman, Brian (17 August 2015). "Joomla is ten years old today". Retrieved 1 December 2020.
  11. Eddie, Andrew (17 August 2005). "Mambo Open Source Development Team—Letter to the community". Retrieved 13 February 2014.
  12. Shreves, Ric (21 August 2005). "The Mambo Open Source Controversy—20 Questions With Miro". Archived from the original on 18 March 2007. Retrieved 27 April 2010. Alt URL
  13. Moglen, Eben (August 2005). "Why I like Open Source Matters (was Why I Like Mambo)". Retrieved 8 October 2008.
  14. Russell, Peter (2005). "Award-winning Development Team Welcomes New Arrival—Joomla!". Retrieved 8 October 2008.
  15. "Partners". Joomla.org. Retrieved 8 October 2008.
  16. "Logo Usage and Brand Guide". docs.joomla.org. Retrieved 8 October 2008.
  17. "Multi-Level User Access With Joomla". 7 June 2007. Retrieved 30 November 2020.
  18. "Newsletter—Welcome to JXtended". JXtended Solutions. December 2007. Archived from the original on 1 May 2008. Retrieved 30 November 2020.
  19. "Lifting the lid on Joomla 1.6" (PDF). 7 June 2009. Retrieved 30 November 2020.
  20. "Google Trends—Explore—joomla (search term)". Retrieved 2 December 2020.
  21. "The Path Forward: Migration and the Future". Joomla.org. 20 January 2011. Retrieved 30 November 2020.
  22. "Andrew Eddie resigns from the Joomla! project". Joomlablogger. 31 August 2010. Retrieved 30 November 2020.
  23. Landry, Louis (3 August 2011). "My Retirement". Retrieved 30 November 2020.
  24. "Proposed leadership structure changes & request for community feedback". community.joomla.org. Retrieved 2 December 2020.
  25. "Joomla 1.6 upgrading FAQ - Discussion". 22 January 2011. Retrieved 7 May 2007.
  26. "History repeating iself?". 1 February 2011. Retrieved 7 May 2007.
  27. Stephen, Amy, et al. (Molajo team) (6 May 2011). What is Molajo?. Kerkrade, The Netherlands. Retrieved 1 December 2020.
  28. Stephen, Amy (31 August 2015). "Molajo (GitHub)". Retrieved 30 November 2020.
  29. Severdia, Ron; Gress, Jennifer (2014). Using Joomla: Efficiently build and manage custom websites. O'Reilly Media. p. 2. ISBN 978-1-449-34539-6.
  30. "Feedback on potential Joomla! Framework LGPL license change". 21 February 2014. Retrieved 1 December 2020.
  31. "LGPL License Change Approved for the Joomla Framework". community.joomla.org. Retrieved 1 December 2020.
  32. "Joomla Framework changes to LGPL". 28 March 2014. Retrieved 1 December 2020.
  33. "What is the Joomla! Framework?". framework.joomla.org. Retrieved 1 December 2020.
  34. "Roadmap". developer.joomla.org. 9 August 2014. Archived from the original on 9 February 2015. Retrieved 2 December 2020.
  35. "Update on the proposed leadership structure changes". 7 November 2014. Retrieved 2 December 2020.
  36. Dionysopoulos, Nicholas (2 November 2014). "Refactoring Joomla!". Retrieved 1 December 2020.
  37. Dionysopoulos, Nicholas (15 May 2015). "The problem is the vision". Retrieved 1 December 2020.
  38. Dings, Marco (20 July 2015). "Joomla! 4 working group". developer.joomla.org. Retrieved 1 December 2020.
  39. Braczek, Niels (28 April 2016). "Current State of Joomla!X". volunteers.joomla.org. Retrieved 4 December 2020.
  40. Nguyen, Henry (8 December 2016). "The future of Joomla: How Joomla will evolve in the next versions?". Joomlashine. Retrieved 6 December 2020.
  41. "Joomla! 3 Retiring as Joomla! 4 Comes to Life". developer.joomla.org. 31 March 2017. Retrieved 1 December 2020.
  42. "OSM Board Meeting minutes". Open Source Matters, Inc. 4 April 2019. Retrieved 1 December 2020.
  43. "Joomla! Project Roadmap". developer.joomla.org. 7 June 2018. Archived from the original on 23 June 2018. Retrieved 3 December 2020.
  44. "Joomla 4 is on the horizon …". developer.joomla.org. 28 December 2018. Retrieved 1 December 2020.
  45. "Joomla! Project Roadmap". developer.joomla.org. 15 January 2019. Archived from the original on 28 January 2019. Retrieved 4 December 2020.
  46. "Joomla! Project Roadmap". developer.joomla.org. 24 November 2020. Retrieved 4 December 2020.
  47. "What's holding back the release of Joomla 4 Beta now?". forum.joomla.org. 14 January 2020. Retrieved 10 December 2020.
  48. "About the design of the administration?". forum.joomla.org. 17 March 2019. Retrieved 10 December 2020.
  49. "Towards a Product Led Future—Forum for the Future". community.joomla.org. Marbella, Spain. 15 January 2020. Retrieved 9 December 2020.
  50. "Forum for the Future: where are we now?". community.joomla.org. 20 October 2020. Retrieved 9 December 2020.
  51. Mitchell, Brian (30 May 2020). Essential Joomla. Joomla and Beyond 2020 conference. Cologne, Germany. Retrieved 10 December 2020.
  52. See Joomla! CMS versions for additional information about version status.
  53. Sandven, Kristoffer (20 July 2009). "Procrastinators: Joomla 1.0 End of Life is Here". CMS Critic. Retrieved 5 December 2020.
  54. Joomla! 1.5 version history
  55. "What is "legacy mode"?". docs.joomla.org. Retrieved 28 November 2020.
  56. "Development Strategy". Joomla.org. 13 August 2011.
  57. "Farewell my Joomla! friend … Adios!". Bang2Joom. 13 March 2014. Archived from the original on 15 March 2014.
  58. "Joomla! CMS versions". Joomla.org. 13 March 2014.
  59. "Joomla! 1.6 Has Arrived!". Joomla.org. 10 January 2011. Retrieved 29 November 2020.
  60. Johnston, Mike (19 January 2011). "Joomla! 1.6 Review". CMS Critic.
  61. "Joomla! 1.7 Released". Joomla.org. 19 July 2011. Retrieved 29 November 2020.
  62. Johnston, Mike (19 July 2011). "1.7 released with focus on enhanced security". CMS Critic.
  63. "Joomla 2.5.0 Released". Joomla.org. 24 January 2012. Retrieved 29 November 2020.
  64. "The Version Votes are In". Joomla.org. 24 August 2011.
  65. "Vote for the Version". Joomla.org. 24 August 2011.
  66. "Joomla 2.5 end of life". 23 October 2014. Retrieved 5 December 2020.
  67. "Joomla 3.0.0 Released". Joomla.org. 27 September 2012. Retrieved 29 November 2020.
  68. "Joomla discussion—release cycle status". groups.google.com. 18 February 2012.
  69. "It's Official—Joomla! CMS to add 3.2 release". joomla.org. 24 December 2012. Retrieved 4 December 2020.
  70. "Joomla! 3.1.0 Stable Released". Joomla.org. 24 April 2013. Retrieved 29 November 2020.
  71. "Tag—You're It". Joomla.org. 6 March 2013. Retrieved 26 November 2020.
  72. "Joomla! 3.2.0 Stable Released". Joomla.org. 6 November 2013.
  73. "Raising The Bar On Security". Joomla.org. 29 January 2014. Retrieved 29 November 2020.
  74. "Joomla! 3.3.0 Released". Joomla.org. 30 April 2014. Retrieved 29 November 2020.
  75. "Release and support cycle". Joomla.org. 8 March 2015.
  76. "Joomla Development Strategy". Joomla.org.
  77. "Past release and support cycle". Joomla.org.
  78. "Joomla! 3.4 is Here". Joomla.org. 24 February 2015. Retrieved 29 November 2020.
  79. "Joomla! 3.5 is Here". Joomla.org. 21 March 2016. Retrieved 29 November 2020.
  80. "Joomla! 3.6 is Here". Joomla.org. 12 July 2016. Retrieved 29 November 2020.
  81. "Joomla! 3.7 is Here". Joomla.org. 25 April 2017. Retrieved 29 November 2020.
  82. "Joomla! 3.8.0 Release". Joomla.org. 19 September 2017. Retrieved 29 November 2020.
  83. "Joomla! 3.9.0 Release". Joomla.org. 30 October 2018. Retrieved 29 November 2020.
  84. "Joomla! 3.9 Landing Page". Joomla.org. 30 October 2018.
  85. "Understanding Output Overrides". docs.joomla.org. Retrieved 6 December 2020.
  86. "Joomla License". docs.joomla.org. Retrieved 30 November 2020.
  87. Only verifiable citations from "Joomla! Awards" are included in this table.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.