Joomla! Documentation - User contributions [en]

GSOC 2014 Project Ideas

2014-03-13T15:49:22Z

Buddhima:

[[Image:GSOC_2014.png|300px|left]]

Welcome to the Joomla! Google Summer of Code (GSoC) 2014 project ideas page. As we move forward with the 2014 version of the Joomla! GSoC, we will use this page to develop possible project ideas. Please note that anyone who is interested can participate in this process. You do not have to be a GSoC student or mentor to suggest possible project ideas. Please keep in mind that projects need to be realistically something that is able to be functionally completed by a student working full time for about eight weeks. Thanks!

For students who want a general overview of Joomla's GSoC, project plans, proposals, and timelines, please [http://docs.joomla.org/GSOC_2014 refer to the GSoC 2014 page].

Discussion of ideas and other GSoC related items is welcome on our Google Group: https://groups.google.com/d/forum/joomla-gsoc-2014

If you are interested in participating as a student please review the materials on applying that are available at [http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2013/help_page Google]. We strongly encourage you to ask questions about process and ideas on the mailing list.

If you are interested in serving as a mentor, please fill out the [https://docs.google.com/a/community.joomla.org/spreadsheet/viewform?formkey=dHA2V1lJbThYQXpwMERiRG1FOTZlV3c6MA Mentor Application Form 2014].

== Ideas ==

Opportunities exist for students to work with projects from either the Joomla CMS, the Joomla Framework or in some cases a combination of both.

In addition to this ideas list, the Joomla! Community is able to voice their opinion on features they would like to see via the [http://ideas.joomla.org/ Joomla! Idea Pool]. Those wishing to add ideas to this listing are encouraged to review the Idea Pool and base their idea on the input received there. You can also view the past lists for [[GSOC_2012_Project_Ideas|2013]], [[GSOC_2012_Project_Ideas|2012]], [[Summer_of_Code_2010_Project_Ideas|2010]] and [[Summer_of_Code_2009_Project_Ideas|2009]], which may be useful for reference. We ask that you keep ideas realistic for the time frame that students will have to complete their projects.

Unless a mentor has proposed a specific project, mentors from the mentor pool will be matched with student projects. However members of the mentor pool are available to answer questions on the Joomla GSoC mailing list.

== Important Guidelines on Submitting Ideas ==

There are some important guidelines to submit ideas, please read these carefully before adding your ideas:
* Ensure your idea is able to be completed in a fixed period of time. GSoC runs officially between May 19th 2014 and August 18th 2014. This is a very short period of actual coding time. Ideas should respect the time that students have available for the program.
* Keep ideas realistic. The ideas on this list should maintain a realistic amount of work for a single student, junior level-developer, who is working with a compressed timeline and a fixed completion ('pencils down') date.
* Keep ideas core. The purpose of GSoC is to improve Joomla itself. This is not the time to add ideas for new extensions or features that may not be included by the PLT. If the idea is related to the framework, please consult the framework team directly about new ideas to ensure there is interest in having the package included as an official Joomla Framework package.
* Respect Joomla's Release Cycle. Joomla's release cycle currently states that with Joomla 3.5, we will not add new features to the CMS. This means that most of the GSoC projects this year should ideally improve existing code in a backwards compatible way.
* Joomla 4. Currently there is not a baseline for what Joomla 4 is and what it could be. Ideas centered around Joomla 4 would not fit in well with the goal of GSoC 2014.
* When in doubt, reach out. If you're unsure if your idea belongs on this list, please post to the GSoC 2014 mailing list and ask about the community's interest.
* No documentation-focused projects. Google Summer of ''Code'' is a program about code. We expect our students to document their work, but writing documentation for Joomla as a project does not align with the goals of GSoC.

== Joomla CMS Ideas ==

* [http://github.com/joomla/joomla-cms Source Code]
* [http://groups.google.com/d/forum/joomla-dev-cms Developer Mailing List]

{{tip|Please add your CMS project ideas below. You can use the '''[[GSOC 2014 Project Ideas/template|GSOC 2014 Project template]]'''.|title=Adding Project Ideas}}

===Project: Refactor CMS to use Dependency Injection ===

:'''Brief explanation:''' The CMS currently has many hard-coded JPATH constants and a JFactory for developers to get certain global objects from the application. This project would develop a way to depreciate the current system which is difficult to test and is tightly coupled. The project will replace the JPATH constants with the Joomla Framework Dependency Injection package, allowing for a looser coupling of the application's core components.

For more info see:
* [https://github.com/joomla/joomla-framework/tree/staging/src/Joomla/DI Joomla Framework DI Package]
* [https://github.com/joomla/joomla-cms/blob/staging/includes/defines.php Joomla CMS Constants]

:'''Expected Results:'''
* Deprecate the current JPATH constants allowing for replacement with Joomla DI
* Refactor core components and to use new DI container
* Write documentation for developers to update their extensions to use Joomla DI

:'''Knowledge Prerequisite:''' PHP, object-oriented programming, Joomla CMS (from a user point of view), Understanding of Dependency Injection and Dependency Injection Containers.

:'''Difficulty:''' Medium to Hard

===Project: Webdriver system tests for CMS===

:'''Brief explanation:''' Automated system tests allow us to test the CMS by automatically running Joomla from a browser, selecting menu options, and evaluating results. At present, several number of [https://github.com/joomla/joomla-cms/tree/staging/tests/system system tests] are currently completed using the Selenium Webdriver technology and using the Page Objects pattern to separate the page objects from the test objects. This project will build on the current base of Webdriver tests and expand the test coverage to include more of the CMS.

For more info see:
* http://docs.joomla.org/System_Testing
* http://www.youtube.com/watch?v=8Mmg32lg4nA

:'''Expected Results:'''
* finish the administrator parts not yet tested
* add front end testing:
** menu items
** modules

:'''Knowledge Prerequisite:''' PHP, object-oriented programming, Joomla CMS (from a user point of view), HTML

:'''Difficulty:''' Medium to Hard

:'''Possible mentors:''' Puneet Kala, Mark Dexter and Javier Gómez

=== Project: Collection of Mini Projects ===

:'''Brief explanation:''' The CMS currently could due with several smaller tasks and projects to help move the software forward and improve its usability and feature set. This project is a *collection* of several smaller projects and improvements. The tasks involved are discrete but they must all be accomplished to a high degree of quality in detail to be considered successful.

===== Decouple Core Extensions =====
:''' Description''' In the current version of the CMS, some extensions rely on one another for functionality. The ultimate goal is for each extension to be completely independent so that it could be removed without breaking the functionality of another.

===== Add Menu Type ACL =====
:''' Description ''' Currently in the CMS there is no way to have backend based ACL rules per menu-type. This project should add advanced ACL rules and configurability to Joomla's core menu types. Adding, deleting, and editing menus on a per-menu group basis should be available on a per-group basis.

===== JError to Exceptions =====
:''' Description ''' Currently Joomla uses the JError class to handle error management - however there is a desire to move this across to use exceptions for Joomla 4.0 and remove the JError class.

:'''Expected Results:''' This project must address and complete each of the above described mini-projects. Proposals should detail each item in detail and outline a timeline for completing them.

===== Implementing Frontend Menu Editing =====
:''' Description ''' Currently frontend menu editing icon redirects user to backend. But actually frontend menu editing should be able to done at the frontend.Implementation would be much similar to the already implemented frontend configuration & frontend template style editing.

:'''Expected Results:''' Frontend logged authorized users should be able to edit menu items via frontend. Student should have to figure-out what should be in frontend editor and relevant access control levels.

:'''Knowledge Prerequisite:''' General knowledge of Joomla 3's core feature set and functionality.

:'''Difficulty:''' Medium to Hard

=== Project: Develop dependency manager ===

:'''Brief explanation:''' Distributions are one of the next possible evolutionary steps for the CMS. One key challenge to solve is the management of dependencies that extensions/packages may have.

:'''Expected Results:''' A working proof of concept that manages the handling of dependencies as well as define requirements that extensions/packages must meet for their dependencies to be managed by this system.

:'''Knowledge Prerequisite:'''

:'''Difficulty:''' Very challenging, but highly rewarding.

=== Project: Update Core Extensions to use New MVC ===

:'''Brief explanation:''' The Joomla Framework has brought us a new MVC architecture that we would like to start using for core components. This project will chose a few core components as a conversion goal to migrate them to run on the new MVC structure.

:'''Expected Results:''' Selected core components will run on the new MVC architecture. This will involve changing the component to run the new controller based architecture, and potentially develop a standardized set of methods that are used across multiple extensions. Reducing code repeats and encouraging reuse will be an important aspect of this project.

:'''Knowledge Prerequisite:'''

:'''Difficulty:''' Challenging, high learning curve and will set precedent for other extensions. This is a opportunity for innovation, not a project to simply copy other parts code into a new feature.

:'''Potential Mentors:''' Soren Beck Jensen as he runs the http://www.Component-Creator.com and Buddhima Wijeweera as he worked on a similar project for GSoC 2013 http://magazine.joomla.org/issues/issue-nov-2013/item/1580-new-mvc-for-joomla-cms

===Project: SQL Optimization===

:'''Brief explanation:''' The goal of this project is to optimize site performances, between the potential areas where performance bottleneck resides in a conventional n-tier website architecture, we'll focus our effort on database side, optimizing slow sql queries.

:'''Expected Results:''' After analyzing and measuring the site performance (on some test case ie small, medium, big) will be taken the necessary action using the proper techniques to improve measurably the slower queries.

:'''Knowledge Prerequisite:''' SQL, DBMS

:'''Difficulty:''' Medium to Hard

:'''Potential mentors:''' Nicola Galgano

===Project: JIssues tracker===

:'''Brief explanation:''' The goal of this project is to finish the JIssues tracker so it is in a position to replace the current Joomla tracker.

:'''Expected Results:''' The JIssues tracker will be at a place where a transition can take place from Joomla Code to the issues tracker. This will involve working with the JIssues (http://issues.joomla.org/) and working through the issue list (https://github.com/joomla/jissues) as well as contributing any relevant code back into the Framework Project

:'''Knowledge Prerequisite:''' Joomla Framework, JoomlaCode, Joomla Bug Tracking Process

:'''Difficulty:''' Medium to Hard

:'''Posible mentors:''' Michael Babker




<noinclude>[[Category:Google Summer of Code 2014]]</noinclude>

===Project: Component for managing predefined emails ===

:'''Brief explanation:''' Many Joomla! extensions send confirmation mails to users. It will be great if Joomla! provides a powerful component, which will be used for creating predefined emails. The component has to provide classes, which will be used from developers for loading, parsing and sending those e-mails.

:'''Expected Results:'''
* Administration interface that will provide an easy way for creating and managing predefined emails.
* Classes that will be used for loading, parsing and sending those emails.

:'''Knowledge Prerequisite:''' PHP, object-oriented programming, Joomla CMS.

:'''Difficulty:''' Medium to Hard

:'''Possible mentors:''' Todor Iliev, Daniel Dimitrov

===Project: Inline editing directly on any page ===

:'''Brief explanation:''' The aim of this project is to add in the possibility of editing any page in Joomla using an inline editing tool. It would make articles editing easier, being able to do that without going to the admin interface. The proposed editor is Froala Editor(in inline mode) and it must interact with the media manager and use language support. The final result should be similar to [http://www.youtube.com/watch?v=5YE8ISXkLXM].

:'''Useful links:'''
* [http://editor.froala.com Froala Editor]
* [https://groups.google.com/forum/#!topic/joomla-dev-cms/giQzWj7fIj8 Discussion about it on CMS list] - please ignore the long comments about the license. It will be sorted out.

:'''Expected Results:'''
* Edit articles in Joomla CMS directly from the page without going to admin interface.
* Have an API for interacting with Froala Editor.

:'''Knowledge Prerequisite:''' PHP, object-oriented programming, Joomla CMS (from a user point of view), Javascript.

:'''Difficulty:''' Medium to Hard

:'''Mentors:''' Stefan Neculai, Diana Neculai

===Project: FrontEnd Components-Management and User-Management ===

:'''Brief explanation:''' The aim of this project is to enable frontend logged authorized uses to manage component options and users. This was a idea when redesigning Joomla! and currently is in the CMS Roadmap. During last year global configuration and template configuration got a frontend configuration. Continuing that further there are 2 possible new frontend configurations:
* Frontend management for components
* Frontend user management

Since Joomla! CMS is moving towards Unified Site Administration, this project will play a key role there.

:'''Useful links:'''
* [http://docs.joomla.org/Help32:Menus_Menu_Item_Display_Site_Configuration Site Configuration Frontend]
* [http://docs.joomla.org/Help32:Menus_Menu_Item_Display_Template_Options Template Options Frontend]
* [https://groups.google.com/forum/?fromgroups=#!topic/joomla-dev-cms/BqlSCKcGB8E Discussion in dev-mailing-list]

:'''Expected Results:'''
* Frontend logged authorize users can configure components via frontend
* Frontend logged authorize users can manage users via frontend

:'''Knowledge Prerequisite:''' PHP, Joomla CMS Components, MVC.

:'''Difficulty:''' Medium to Hard

===Project: Enhancing User Profiles===

:'''Brief explanation:''' The aim of this project is to enhance the existing user profiles by allowing to interact with social media. This will create the basic infrastructure for include social media profiles, and cms developers to profile services. Also this will use existing libraries in joomla and provide a flexible way to incorporate profile services.

:'''Expected Results:'''
* cms libraries for profile services (including a local version)
* Managing keys for profile services
* Top-level configuration (for webmasters) on which services are allowed to use
* Enable individual users to specify which Profile service desire to use (select one from allowed ones)
* Modernize frontend com_contact appearance

:'''Knowledge Prerequisite:''' PHP, Joomla! Extensions Development, Understanding on Joomla! libararies (JFacebook, JLinkedin, JGoogle etc.), OAuth, Experience as a Joomla!CMS user.

:'''Difficulty:''' Medium to Hard

===Project: Improve Media Handling In Joomla! ===

:'''Brief explanation:''' The aim of this project is to add media (video & audio) handling capabilities into Joomla, with the help of external services. At the completion of the project, any interested Joomla extension should be able to handle media related things across this libraries.
Currently it is proposed to use YouTube and Vimeo for video handling, and SoundCloud for audio. But students are encourage for a better solution.

:'''Useful links:'''
* [https://developers.google.com/youtube/getting_started YouTube API]
* [http://developer.vimeo.com/ Vimeo API]
* [http://developers.soundcloud.com/ SoundCloud API]
This could take similar approach as JFacebook, JLinkedin and JGoogle. Student expected to come-up with a good plan on how to incorporate new libraries with Joomla! CMS.

:'''Expected Results:'''
* Libraries for YouTube, Vimeo and SoundCloud with tests.
* Library for CMS to handle Media and access above mentioned libraries with tests.
* Libraries should provide video modification

:'''Knowledge Prerequisite:''' PHP, Understanding on existing Joomla CMS libraries, Knowledge on mentioned APIs, Joomla! development experience.

:'''Difficulty:''' Medium to Hard

:'''Potential Mentors:''' Jonathan Cameron

===Project: Extending Tags In Joomla! ===

:'''Brief explanation:''' The introduction of Tags is a key thing Joomla 3.x series. That helped a lot to easily keep track of different contents and ease the searching. But still there are drawbacks in following areas.
* Misspelled tags
* Short form of words in tags
* Abbreviations in tags
* US, UK spelling differences
Because of the above reasons, it’ll have higher chance of missing things when number of tags keep growing. Therefore, though this student is expected to introduce a new section for com_tags, which can accommodate re-tagging process.

:'''Useful links:'''
* [http://docs.joomla.org/J3.2:How_To_Use_Content_Tags_in_Joomla! Using Tags in Joomla]
* [http://stackoverflow.com/tags/synonyms Stackoverflow Tag synonyms]

:'''Expected Results:'''
# Webmaster should be able to specify connection between tags through com_tags
# Underlying re-tagging process
# Manage a system for permanently mapping tags that were merged to the preferred tag

:'''Knowledge Prerequisite:''' PHP, object-oriented programming, experience as a Joomla CMS developer and a user

:'''Difficulty:''' Medium to Hard

== Joomla Framework ==

The Joomla Framework project ideas allows for ideas that can work within the Joomla CMS, or could be completely separate applications that have no connection at all. The Joomla Framework allows for applications to be built for the command line, process daemons and the web.

References:
*[http://github.com/joomla/joomla-framework github Source Code]
*[http://developer.joomla.org/framework/roadmap.html Development Roadmap]
*[http://groups.google.com/d/forum/joomla-dev-framework Developer Mailing List]

All code contributions must follow Joomla coding standards and include full unit test coverage.

{{tip|Please add your Framework project ideas below. You can use the '''[[GSOC 2014 Project Ideas/template|GSOC 2014 Project template]]'''.|title=Adding Project Ideas}}

===Project: Framework Unit Testing===

:'''Brief explanation:''' The Joomla Framework has a good suite of automated Unit Tests, but code coverage is lacking in some areas. The goal of this project is to improve the code coverage by writing unit tests for the Joomla Framework.

:'''Expected Results:''' The student will be expected to review the current [http://developer.joomla.org/framework-coverage/ code coverage report] for the Joomla Framework and write and agreed-upon number of unit tests with particular attention to packages that are below 50% coverage. Preference should be given to non-deprecated classes but the student may choose from either the core tree (/libraries/joomla) or the legacy tree (/libraries/legacy).

:'''Knowledge Prerequisite:''' PHP, PHPUnit

:'''Difficulty:''' Medium

===Project: Improve Filesystem classes===

:'''Brief explanation:''' Replace static methods with public ones of classes File, Folder, Path. Let these things to be used as object with theirs methods and properties. Develop classes, which will be used as adapters, for some fundamental actions performed on those file system elements. The adapters should be for uploading, deleting, reading,...

:'''Expected Results:'''
* A set of well coded, fully unit tested and documented implementations for the file system classes.
* Adapters for managing files on some of the most popular cloud services - Amazon S3, Google App Engine,...
* Classes for validating files size, images,...

:'''Knowledge Prerequisite:''' GitHub, PHPUnit, PHP, OOP, Design Patterns, familiarity with web services and Joomla! Framework.

:'''Difficulty:''' Medium to Hard

===Project: Improve Date classes===

:'''Brief explanation:''' Develop classes and methods that will give more power to developers working with dates.

:'''Expected Results:'''
* Methods that calculate dates for yesterday, begin of week, end of week, begin of month, end of month, begin of year, end of year,...
* Methods that calculate time for begin of day, end of day,...

:'''Knowledge Prerequisite:''' GitHub, PHPUnit, PHP, OOP, Design Patterns, familiarity Joomla! Framework.

:'''Difficulty:''' Medium to Hard

===Project: Composer GUI installer ===

:'''Brief explanation:''' Creating an installer from the GUI with Composer. Both the Joomla Framework and the CMS are working towards extension packages that can be installed via Composer. A great advantage of Composer is that it handles all dependencies in the background. A disadvantage is, that - until now - Composer is used via the Command Line Interface. The goal of this GSOC project is to create an installer that uses Composer, but entirely from the GUI website administrator.

This project is now put under "Joomla Framework" but there is much interest for it in the Joomla CMS and also in other PHP-projects.

For more info see:
* [https://github.com/joomla-cms/start-here/issues/11]
* [https://groups.google.com/forum/#!topic/joomla-dev-cms/nqdyyMKoDcE]
* [https://github.com/joomla-cms/start-here/issues/14]
* [https://github.com/joomlatools/joomla-composer]
* [https://www.youtube.com/watch?v=hinv__2spBc]
* [http://magazine.joomla.org/issues/issue-aug-2013/item/1450-getting-started-with-composer-and-joomla]

:'''Expected Results:'''
* A Composer based extension-installer in the Joomla CMS GUI, that can also be used on shared hosts with limited permissions to use a CLI.
* The basis for this installer as a package in the Joomla Framework, that can be used by other PHP projects.

:'''Knowledge Prerequisite:''' PHP, understanding of the use of Composer, understanding of Joomla's extension installer and "Install from Web" (formerly known as the " Joomla App Store"), knowledge of plans to split up Joomla in (composable) subprojects.

:'''Difficulty:''' Medium to Hard

[[Category:Google Summer of Code 2014]]

GSOC 2014 Project Ideas

2014-03-11T19:36:35Z

Buddhima:

[[Image:GSOC_2014.png|300px|left]]

Welcome to the Joomla! Google Summer of Code (GSoC) 2014 project ideas page. As we move forward with the 2014 version of the Joomla! GSoC, we will use this page to develop possible project ideas. Please note that anyone who is interested can participate in this process. You do not have to be a GSoC student or mentor to suggest possible project ideas. Please keep in mind that projects need to be realistically something that is able to be functionally completed by a student working full time for about eight weeks. Thanks!

For students who want a general overview of Joomla's GSoC, project plans, proposals, and timelines, please [http://docs.joomla.org/GSOC_2014 refer to the GSoC 2014 page].

Discussion of ideas and other GSoC related items is welcome on our Google Group: https://groups.google.com/d/forum/joomla-gsoc-2014

If you are interested in participating as a student please review the materials on applying that are available at [http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2013/help_page Google]. We strongly encourage you to ask questions about process and ideas on the mailing list.

If you are interested in serving as a mentor, please fill out the [https://docs.google.com/a/community.joomla.org/spreadsheet/viewform?formkey=dHA2V1lJbThYQXpwMERiRG1FOTZlV3c6MA Mentor Application Form 2014].

== Ideas ==

Opportunities exist for students to work with projects from either the Joomla CMS, the Joomla Framework or in some cases a combination of both.

In addition to this ideas list, the Joomla! Community is able to voice their opinion on features they would like to see via the [http://ideas.joomla.org/ Joomla! Idea Pool]. Those wishing to add ideas to this listing are encouraged to review the Idea Pool and base their idea on the input received there. You can also view the past lists for [[GSOC_2012_Project_Ideas|2013]], [[GSOC_2012_Project_Ideas|2012]], [[Summer_of_Code_2010_Project_Ideas|2010]] and [[Summer_of_Code_2009_Project_Ideas|2009]], which may be useful for reference. We ask that you keep ideas realistic for the time frame that students will have to complete their projects.

Unless a mentor has proposed a specific project, mentors from the mentor pool will be matched with student projects. However members of the mentor pool are available to answer questions on the Joomla GSoC mailing list.

== Important Guidelines on Submitting Ideas ==

There are some important guidelines to submit ideas, please read these carefully before adding your ideas:
* Ensure your idea is able to be completed in a fixed period of time. GSoC runs officially between May 19th 2014 and August 18th 2014. This is a very short period of actual coding time. Ideas should respect the time that students have available for the program.
* Keep ideas realistic. The ideas on this list should maintain a realistic amount of work for a single student, junior level-developer, who is working with a compressed timeline and a fixed completion ('pencils down') date.
* Keep ideas core. The purpose of GSoC is to improve Joomla itself. This is not the time to add ideas for new extensions or features that may not be included by the PLT. If the idea is related to the framework, please consult the framework team directly about new ideas to ensure there is interest in having the package included as an official Joomla Framework package.
* Respect Joomla's Release Cycle. Joomla's release cycle currently states that with Joomla 3.5, we will not add new features to the CMS. This means that most of the GSoC projects this year should ideally improve existing code in a backwards compatible way.
* Joomla 4. Currently there is not a baseline for what Joomla 4 is and what it could be. Ideas centered around Joomla 4 would not fit in well with the goal of GSoC 2014.
* When in doubt, reach out. If you're unsure if your idea belongs on this list, please post to the GSoC 2014 mailing list and ask about the community's interest.
* No documentation-focused projects. Google Summer of ''Code'' is a program about code. We expect our students to document their work, but writing documentation for Joomla as a project does not align with the goals of GSoC.

== Joomla CMS Ideas ==

* [http://github.com/joomla/joomla-cms Source Code]
* [http://groups.google.com/d/forum/joomla-dev-cms Developer Mailing List]

{{tip|Please add your CMS project ideas below. You can use the '''[[GSOC 2014 Project Ideas/template|GSOC 2014 Project template]]'''.|title=Adding Project Ideas}}

===Project: Refactor CMS to use Dependency Injection ===

:'''Brief explanation:''' The CMS currently has many hard-coded JPATH constants and a JFactory for developers to get certain global objects from the application. This project would develop a way to depreciate the current system which is difficult to test and is tightly coupled. The project will replace the JPATH constants with the Joomla Framework Dependency Injection package, allowing for a looser coupling of the application's core components.

For more info see:
* [https://github.com/joomla/joomla-framework/tree/staging/src/Joomla/DI Joomla Framework DI Package]
* [https://github.com/joomla/joomla-cms/blob/staging/includes/defines.php Joomla CMS Constants]

:'''Expected Results:'''
* Deprecate the current JPATH constants allowing for replacement with Joomla DI
* Refactor core components and to use new DI container
* Write documentation for developers to update their extensions to use Joomla DI

:'''Knowledge Prerequisite:''' PHP, object-oriented programming, Joomla CMS (from a user point of view), Understanding of Dependency Injection and Dependency Injection Containers.

:'''Difficulty:''' Medium to Hard

===Project: Webdriver system tests for CMS===

:'''Brief explanation:''' Automated system tests allow us to test the CMS by automatically running Joomla from a browser, selecting menu options, and evaluating results. At present, several number of [https://github.com/joomla/joomla-cms/tree/staging/tests/system system tests] are currently completed using the Selenium Webdriver technology and using the Page Objects pattern to separate the page objects from the test objects. This project will build on the current base of Webdriver tests and expand the test coverage to include more of the CMS.

For more info see:
* http://docs.joomla.org/System_Testing
* http://www.youtube.com/watch?v=8Mmg32lg4nA

:'''Expected Results:'''
* finish the administrator parts not yet tested
* add front end testing:
** menu items
** modules

:'''Knowledge Prerequisite:''' PHP, object-oriented programming, Joomla CMS (from a user point of view), HTML

:'''Difficulty:''' Medium to Hard

:'''Possible mentors:''' Puneet Kala, Mark Dexter and Javier Gómez

=== Project: Collection of Mini Projects ===

:'''Brief explanation:''' The CMS currently could due with several smaller tasks and projects to help move the software forward and improve its usability and feature set. This project is a *collection* of several smaller projects and improvements. The tasks involved are discrete but they must all be accomplished to a high degree of quality in detail to be considered successful.

===== Decouple Core Extensions =====
:''' Description''' In the current version of the CMS, some extensions rely on one another for functionality. The ultimate goal is for each extension to be completely independent so that it could be removed without breaking the functionality of another.

===== Add Menu Type ACL =====
:''' Description ''' Currently in the CMS there is no way to have backend based ACL rules per menu-type. This project should add advanced ACL rules and configurability to Joomla's core menu types. Adding, deleting, and editing menus on a per-menu group basis should be available on a per-group basis.

===== JError to Exceptions =====
:''' Description ''' Currently Joomla uses the JError class to handle error management - however there is a desire to move this across to use exceptions for Joomla 4.0 and remove the JError class.

:'''Expected Results:''' This project must address and complete each of the above described mini-projects. Proposals should detail each item in detail and outline a timeline for completing them.

===== Implementing Frontend Menu Editing =====
:''' Description ''' Currently frontend menu editing icon redirects user to backend. But actually frontend menu editing should be able to done at the frontend.Implementation would be much similar to the already implemented frontend configuration & frontend template style editing.

:'''Expected Results:''' Frontend logged authorized users should be able to edit menu items via frontend. Student should have to figure-out what should be in frontend editor and relevant access control levels.

:'''Knowledge Prerequisite:''' General knowledge of Joomla 3's core feature set and functionality.

:'''Difficulty:''' Medium to Hard

=== Project: Develop dependency manager ===

:'''Brief explanation:''' Distributions are one of the next possible evolutionary steps for the CMS. One key challenge to solve is the management of dependencies that extensions/packages may have.

:'''Expected Results:''' A working proof of concept that manages the handling of dependencies as well as define requirements that extensions/packages must meet for their dependencies to be managed by this system.

:'''Knowledge Prerequisite:'''

:'''Difficulty:''' Very challenging, but highly rewarding.

=== Project: Update Core Extensions to use New MVC ===

:'''Brief explanation:''' The Joomla Framework has brought us a new MVC architecture that we would like to start using for core components. This project will chose a few core components as a conversion goal to migrate them to run on the new MVC structure.

:'''Expected Results:''' Selected core components will run on the new MVC architecture. This will involve changing the component to run the new controller based architecture, and potentially develop a standardized set of methods that are used across multiple extensions. Reducing code repeats and encouraging reuse will be an important aspect of this project.

:'''Knowledge Prerequisite:'''

:'''Difficulty:''' Challenging, high learning curve and will set precedent for other extensions. This is a opportunity for innovation, not a project to simply copy other parts code into a new feature.

:'''Potential Mentors:''' Soren Beck Jensen as he runs the http://www.Component-Creator.com and Buddhima Wijeweera as he worked on a similar project for GSoC 2013 http://magazine.joomla.org/issues/issue-nov-2013/item/1580-new-mvc-for-joomla-cms

===Project: SQL Optimization===

:'''Brief explanation:''' The goal of this project is to optimize site performances, between the potential areas where performance bottleneck resides in a conventional n-tier website architecture, we'll focus our effort on database side, optimizing slow sql queries.

:'''Expected Results:''' After analyzing and measuring the site performance (on some test case ie small, medium, big) will be taken the necessary action using the proper techniques to improve measurably the slower queries.

:'''Knowledge Prerequisite:''' SQL, DBMS

:'''Difficulty:''' Medium to Hard

:'''Potential mentors:''' Nicola Galgano

===Project: JIssues tracker===

:'''Brief explanation:''' The goal of this project is to finish the JIssues tracker so it is in a position to replace the current Joomla tracker.

:'''Expected Results:''' The JIssues tracker will be at a place where a transition can take place from Joomla Code to the issues tracker. This will involve working with the JIssues (http://issues.joomla.org/) and working through the issue list (https://github.com/joomla/jissues) as well as contributing any relevant code back into the Framework Project

:'''Knowledge Prerequisite:''' Joomla Framework, JoomlaCode, Joomla Bug Tracking Process

:'''Difficulty:''' Medium to Hard

:'''Posible mentors:''' Michael Babker




<noinclude>[[Category:Google Summer of Code 2014]]</noinclude>

===Project: Component for managing predefined emails ===

:'''Brief explanation:''' Many Joomla! extensions send confirmation mails to users. It will be great if Joomla! provides a powerful component, which will be used for creating predefined emails. The component has to provide classes, which will be used from developers for loading, parsing and sending those e-mails.

:'''Expected Results:'''
* Administration interface that will provide an easy way for creating and managing predefined emails.
* Classes that will be used for loading, parsing and sending those emails.

:'''Knowledge Prerequisite:''' PHP, object-oriented programming, Joomla CMS.

:'''Difficulty:''' Medium to Hard

:'''Possible mentors:''' Todor Iliev, Daniel Dimitrov

===Project: Inline editing directly on any page ===

:'''Brief explanation:''' The aim of this project is to add in the possibility of editing any page in Joomla using an inline editing tool. It would make articles editing easier, being able to do that without going to the admin interface. The proposed editor is Froala Editor(in inline mode) and it must interact with the media manager and use language support. The final result should be similar to [http://www.youtube.com/watch?v=5YE8ISXkLXM].

:'''Useful links:'''
* [http://editor.froala.com Froala Editor]
* [https://groups.google.com/forum/#!topic/joomla-dev-cms/giQzWj7fIj8 Discussion about it on CMS list] - please ignore the long comments about the license. It will be sorted out.

:'''Expected Results:'''
* Edit articles in Joomla CMS directly from the page without going to admin interface.
* Have an API for interacting with Froala Editor.

:'''Knowledge Prerequisite:''' PHP, object-oriented programming, Joomla CMS (from a user point of view), Javascript.

:'''Difficulty:''' Medium to Hard

:'''Mentors:''' Stefan Neculai, Diana Neculai

===Project: FrontEnd Components-Management and User-Management ===

:'''Brief explanation:''' The aim of this project is to enable frontend logged authorized uses to manage component options and users. This was a idea when redesigning Joomla! and currently is in the CMS Roadmap. During last year global configuration and template configuration got a frontend configuration. Continuing that further there are 2 possible new frontend configurations:
* Frontend management for components
* Frontend user management

Since Joomla! CMS is moving towards Unified Site Administration, this project will play a key role there.

:'''Useful links:'''
* [http://docs.joomla.org/Help32:Menus_Menu_Item_Display_Site_Configuration Site Configuration Frontend]
* [http://docs.joomla.org/Help32:Menus_Menu_Item_Display_Template_Options Template Options Frontend]
* [https://groups.google.com/forum/?fromgroups=#!topic/joomla-dev-cms/BqlSCKcGB8E Discussion in dev-mailing-list]

:'''Expected Results:'''
* Frontend logged authorize users can configure components via frontend
* Frontend logged authorize users can manage users via frontend

:'''Knowledge Prerequisite:''' PHP, Joomla CMS Components, MVC.

:'''Difficulty:''' Medium to Hard

===Project: Enhancing User Profiles===

:'''Brief explanation:''' The aim of this project is to enhance the existing user profiles by allowing to interact with social media. This will create the basic infrastructure for include social media profiles, and cms developers to profile services. Also this will use existing libraries in joomla and provide a flexible way to incorporate profile services.

:'''Expected Results:'''
* cms libraries for profile services (including a local version)
* Managing keys for profile services
* Top-level configuration (for webmasters) on which services are allowed to use
* Enable individual users to specify which Profile service desire to use (select one from allowed ones)
* Modernize frontend com_contact appearance

:'''Knowledge Prerequisite:''' PHP, Joomla! Extensions Development, Understanding on Joomla! libararies (JFacebook, JLinkedin, JGoogle etc.), OAuth, Experience as a Joomla!CMS user.

:'''Difficulty:''' Medium to Hard

===Project: Improve Media Handling In Joomla! ===

:'''Brief explanation:''' The aim of this project is to add media (video & audio) handling capabilities into Joomla, with the help of external services. At the completion of the project, any interested Joomla extension should be able to handle media related things across this libraries.
Currently it is proposed to use YouTube and Vimeo for video handling, and SoundCloud for audio. But students are encourage for a better solution.

:'''Useful links:'''
* [https://developers.google.com/youtube/getting_started YouTube API]
* [http://developer.vimeo.com/ Vimeo API]
* [http://developers.soundcloud.com/ SoundCloud API]
This could take similar approach as JFacebook, JLinkedin and JGoogle. Student expected to come-up with a good plan on how to incorporate new libraries with Joomla! CMS.

:'''Expected Results:'''
* Libraries for YouTube, Vimeo and SoundCloud with tests.
* Library for CMS to handle Media and access above mentioned libraries with tests.
* Libraries should provide video modification

:'''Knowledge Prerequisite:''' PHP, Understanding on existing Joomla CMS libraries, Knowledge on mentioned APIs, Joomla! development experience.

:'''Difficulty:''' Medium to Hard

:'''Potential Mentors:''' Jonathan Cameron

== Joomla Framework ==

The Joomla Framework project ideas allows for ideas that can work within the Joomla CMS, or could be completely separate applications that have no connection at all. The Joomla Framework allows for applications to be built for the command line, process daemons and the web.

References:
*[http://github.com/joomla/joomla-framework github Source Code]
*[http://developer.joomla.org/framework/roadmap.html Development Roadmap]
*[http://groups.google.com/d/forum/joomla-dev-framework Developer Mailing List]

All code contributions must follow Joomla coding standards and include full unit test coverage.

{{tip|Please add your Framework project ideas below. You can use the '''[[GSOC 2014 Project Ideas/template|GSOC 2014 Project template]]'''.|title=Adding Project Ideas}}

===Project: Framework Unit Testing===

:'''Brief explanation:''' The Joomla Framework has a good suite of automated Unit Tests, but code coverage is lacking in some areas. The goal of this project is to improve the code coverage by writing unit tests for the Joomla Framework.

:'''Expected Results:''' The student will be expected to review the current [http://developer.joomla.org/framework-coverage/ code coverage report] for the Joomla Framework and write and agreed-upon number of unit tests with particular attention to packages that are below 50% coverage. Preference should be given to non-deprecated classes but the student may choose from either the core tree (/libraries/joomla) or the legacy tree (/libraries/legacy).

:'''Knowledge Prerequisite:''' PHP, PHPUnit

:'''Difficulty:''' Medium

===Project: Improve Filesystem classes===

:'''Brief explanation:''' Replace static methods with public ones of classes File, Folder, Path. Let these things to be used as object with theirs methods and properties. Develop classes, which will be used as adapters, for some fundamental actions performed on those file system elements. The adapters should be for uploading, deleting, reading,...

:'''Expected Results:'''
* A set of well coded, fully unit tested and documented implementations for the file system classes.
* Adapters for managing files on some of the most popular cloud services - Amazon S3, Google App Engine,...
* Classes for validating files size, images,...

:'''Knowledge Prerequisite:''' GitHub, PHPUnit, PHP, OOP, Design Patterns, familiarity with web services and Joomla! Framework.

:'''Difficulty:''' Medium to Hard

===Project: Improve Date classes===

:'''Brief explanation:''' Develop classes and methods that will give more power to developers working with dates.

:'''Expected Results:'''
* Methods that calculate dates for yesterday, begin of week, end of week, begin of month, end of month, begin of year, end of year,...
* Methods that calculate time for begin of day, end of day,...

:'''Knowledge Prerequisite:''' GitHub, PHPUnit, PHP, OOP, Design Patterns, familiarity Joomla! Framework.

:'''Difficulty:''' Medium to Hard

[[Category:Google Summer of Code 2014]]

GSOC 2014 Project Ideas

2014-02-28T06:53:17Z

Buddhima:

[[Image:GSOC_2014.png|300px|left]]

Welcome to the Joomla! Google Summer of Code (GSoC) 2014 project ideas page. As we move forward with the 2014 version of the Joomla! GSoC, we will use this page to develop possible project ideas. Please note that anyone who is interested can participate in this process. You do not have to be a GSoC student or mentor to suggest possible project ideas. Please keep in mind that projects need to be realistically something that is able to be functionally completed by a student working full time for about eight weeks. Thanks!

For students who want a general overview of Joomla's GSoc, project plans, proposals, and timelines, please [http://docs.joomla.org/GSOC_2014 refer to the GSoC 2014 page].

Discussion of ideas and other GSoC related items is welcome on our Google Group: https://groups.google.com/d/forum/joomla-gsoc-2014

If you are interested in participating as a student please review the materials on applying that are available at [http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2013/help_page Google]. We strongly encourage you to ask questions about process and ideas on the mailing list.

If you are interested in serving as a mentor, please fill out the [https://docs.google.com/a/community.joomla.org/spreadsheet/viewform?formkey=dHA2V1lJbThYQXpwMERiRG1FOTZlV3c6MA Mentor Application Form 2014].

== Ideas ==

Opportunities exist for students to work with projects from either the Joomla CMS, the Joomla Framework or in some cases a combination of both.

In addition to this ideas list, the Joomla! Community is able to voice their opinion on features they would like to see via the [http://ideas.joomla.org/ Joomla! Idea Pool]. Those wishing to add ideas to this listing are encouraged to review the Idea Pool and base their idea on the input received there. You can also view the past lists for [[GSOC_2012_Project_Ideas|2013]], [[GSOC_2012_Project_Ideas|2012]], [[Summer_of_Code_2010_Project_Ideas|2010]] and [[Summer_of_Code_2009_Project_Ideas|2009]], which may be useful for reference. We ask that you keep ideas realistic for the time frame that students will have to complete their projects.

Unless a mentor has proposed a specific project, mentors from the mentor pool will be matched with student projects. However members of the mentor pool are available to answer questions on the Joomla GSoC mailing list.

== Important Guidelines on Submitting Ideas ==

There are some important guidelines to submit ideas, please read these carefully before adding your ideas:
* Ensure your idea is able to be completed in a fixed period of time. GSoC runs officially between May 19th 2014 and August 18th 2014. This is a very short period of actual coding time. Ideas should respect the time that students have available for the program.
* Keep ideas realistic. The ideas on this list should maintain a realistic amount of work for a single student, junior level-developer, who is working with a compressed timeline and a fixed completion ('pencils down') date.
* Keep ideas core. The purpose of GSoC is to improve Joomla itself. This is not the time to add ideas for new extensions or features that may not be included by the PLT. If the idea is related to the framework, please consult the framework team directly about new ideas to ensure there is interest in having the package included as an official Joomla Framework package.
* Respect Joomla's Release Cycle. Joomla's release cycle currently states that with Joomla 3.5, we will not add new features to the CMS. This means that most of the GSoC projects this year should ideally improve existing code in a backwards compatible way.
* Joomla 4. Currently there is not a baseline for what Joomla 4 is and what it could be. Ideas centered around Joomla 4 would not fit in well with the goal of GSoC 2014.
* When in doubt, reach out. If you're unsure if your idea belongs on this list, please post to the GSoC 2014 mailing list and ask about the community's interest.
* No documentation-focused projects. Google Summer of ''Code'' is a program about code. We expect our students to document their work, but writing documentation for Joomla as a project does not align with the goals of GSoC.

== Joomla CMS Ideas ==

* [http://github.com/joomla/joomla-cms Source Code]
* [http://groups.google.com/d/forum/joomla-dev-cms Developer Mailing List]

{{tip|Please add your CMS project ideas below. You can use the '''[[GSOC 2014 Project Ideas/template|GSOC 2014 Project template]]'''.|title=Adding Project Ideas}}

===Project: Refactor CMS to use Dependency Injection ===

:'''Brief explanation:''' The CMS currently has many hard-coded JPATH constants and a JFactory for developers to get certain global objects from the application. This project would develop a way to depreciate the current system which is difficult to test and is tightly coupled. The project will replace the JPATH constants with the Joomla Framework Dependency Injection package, allowing for a looser coupling of the application's core components.

For more info see:
* [https://github.com/joomla/joomla-framework/tree/staging/src/Joomla/DI Joomla Framework DI Package]
* [https://github.com/joomla/joomla-cms/blob/staging/includes/defines.php Joomla CMS Constants]

:'''Expected Results:'''
* Deprecate the current JPATH constants allowing for replacement with Joomla DI
* Refactor core components and to use new DI container
* Write documentation for developers to update their extensions to use Joomla DI

:'''Knowledge Prerequisite:''' PHP, object-oriented programming, Joomla CMS (from a user point of view), Understanding of Dependency Injection and Dependency Injection Containers.

:'''Difficulty:''' Medium to Hard

===Project: Webdriver system tests for CMS===

:'''Brief explanation:''' Automated system tests allow us to test the CMS by automatically running Joomla from a browser, selecting menu options, and evaluating results. At present, several number of [https://github.com/joomla/joomla-cms/tree/staging/tests/system system tests] are currently completed using the Selenium Webdriver technology and using the Page Objects pattern to separate the page objects from the test objects. This project will build on the current base of Webdriver tests and expand the test coverage to include more of the CMS.

For more info see:
* http://docs.joomla.org/System_Testing
* http://www.youtube.com/watch?v=8Mmg32lg4nA

:'''Expected Results:'''
* finish the administrator parts not yet tested
* add front end testing:
** menu items
** modules

:'''Knowledge Prerequisite:''' PHP, object-oriented programming, Joomla CMS (from a user point of view), HTML

:'''Difficulty:''' Medium to Hard

:'''Possible mentors:''' Puneet Kala, Mark Dexter and Javier Gómez

=== Project: Collection of Mini Projects ===

:'''Brief explanation:''' The CMS currently could due with several smaller tasks and projects to help move the software forward and improve its usability and feature set. This project is a *collection* of several smaller projects and improvements. The tasks involved are discrete but they must all be accomplished to a high degree of quality in detail to be considered successful.

===== Decouple Core Extensions =====
:''' Description''' In the current version of the CMS, some extensions rely on one another for functionality. The ultimate goal is for each extension to be completely independent so that it could be removed without breaking the functionality of another.

===== Add Menu Type ACL =====
:''' Description ''' Currently in the CMS there is no way to have backend based ACL rules per menu-type. This project should add advanced ACL rules and configurability to Joomla's core menu types. Adding, deleting, and editing menus on a per-menu group basis should be available on a per-group basis.

===== JError to Exceptions =====
:''' Description ''' Currently Joomla uses the JError class to handle error management - however there is a desire to move this across to use exceptions for Joomla 4.0 and remove the JError class.

:'''Expected Results:''' This project must address and complete each of the above described mini-projects. Proposals should detail each item in detail and outline a timeline for completing them.

===== Implementing Frontend Menu Editing =====
:''' Description ''' Currently frontend menu editing icon redirects user to backend. But actually frontend menu editing should be able to done at the frontend.Implementation would be much similar to the already implemented frontend configuration & frontend template style editing.

:'''Expected Results:''' Frontend logged authorized users should be able to edit menu items via frontend. Student should have to figure-out what should be in frontend editor and relevant access control levels.

:'''Knowledge Prerequisite:''' General knowledge of Joomla 3's core feature set and functionality.

:'''Difficulty:''' Medium to Hard

=== Project: Develop dependency manager ===

:'''Brief explanation:''' Distributions are one of the next possible evolutionary steps for the CMS. One key challenge to solve is the management of dependencies that extensions/packages may have.

:'''Expected Results:''' A working proof of concept that manages the handling of dependencies as well as define requirements that extensions/packages must meet for their dependencies to be managed by this system.

:'''Knowledge Prerequisite:'''

:'''Difficulty:''' Very challenging, but highly rewarding.

=== Project: Update Core Extensions to use New MVC ===

:'''Brief explanation:''' The Joomla Framework has brought us a new MVC architecture that we would like to start using for core components. This project will chose a few core components as a conversion goal to migrate them to run on the new MVC structure.

:'''Expected Results:''' Selected core components will run on the new MVC architecture. This will involve changing the component to run the new controller based architecture, and potentially develop a standardized set of methods that are used across multiple extensions. Reducing code repeats and encouraging reuse will be an important aspect of this project.

:'''Knowledge Prerequisite:'''

:'''Difficulty:''' Challenging, high learning curve and will set precedent for other extensions. This is a opportunity for innovation, not a project to simply copy other parts code into a new feature.

:'''Potential Mentors:''' Soren Beck Jensen as he runs the http://www.Component-Creator.com and Buddhima Wijeweera as he worked on a similar project for GSoC 2013 http://magazine.joomla.org/issues/issue-nov-2013/item/1580-new-mvc-for-joomla-cms

===Project: SQL Optimization===

:'''Brief explanation:''' The goal of this project is to optimize site performances, between the potential areas where performance bottleneck resides in a conventional n-tier website architecture, we'll focus our effort on database side, optimizing slow sql queries.

:'''Expected Results:''' After analyzing and measuring the site performance (on some test case ie small, medium, big) will be taken the necessary action using the proper techniques to improve measurably the slower queries.

:'''Knowledge Prerequisite:''' SQL, DBMS

:'''Difficulty:''' Medium to Hard

:'''Potential mentors:''' Nicola Galgano

===Project: JIssues tracker===

:'''Brief explanation:''' The goal of this project is to finish the JIssues tracker so it is in a position to replace the current Joomla tracker.

:'''Expected Results:''' The JIssues tracker will be at a place where a transition can take place from Joomla Code to the issues tracker. This will involve working with the JIssues (http://issues.joomla.org/) and working through the issue list (https://github.com/joomla/jissues) as well as contributing any relevant code back into the Framework Project

:'''Knowledge Prerequisite:''' Joomla Framework, JoomlaCode, Joomla Bug Tracking Process

:'''Difficulty:''' Medium to Hard

:'''Posible mentors:''' Michael Babker




<noinclude>[[Category:Google Summer of Code 2014]]</noinclude>

===Project: Component for managing predefined emails ===

:'''Brief explanation:''' Many Joomla! extensions send confirmation mails to users. It will be great if Joomla! provides a powerful component, which will be used for creating predefined emails. The component has to provide classes, which will be used from developers for loading, parsing and sending those e-mails.

:'''Expected Results:'''
* Administration interface that will provide an easy way for creating and managing predefined emails.
* Classes that will be used for loading, parsing and sending those emails.

:'''Knowledge Prerequisite:''' PHP, object-oriented programming, Joomla CMS.

:'''Difficulty:''' Medium to Hard

:'''Possible mentors:''' Todor Iliev, Daniel Dimitrov

===Project: Inline editing directly on any page ===

:'''Brief explanation:''' The aim of this project is to add in the possibility of editing any page in Joomla using an inline editing tool. It would make articles editing easier, being able to do that without going to the admin interface. The proposed editor is Froala Editor(in inline mode) and it must interact with the media manager and use language support. The final result should be similar to [http://www.youtube.com/watch?v=5YE8ISXkLXM].

:'''Useful links:'''
* [http://editor.froala.com Froala Editor]
* [https://groups.google.com/forum/#!topic/joomla-dev-cms/giQzWj7fIj8 Discussion about it on CMS list] - please ignore the long comments about the license. It will be sorted out.

:'''Expected Results:'''
* Edit articles in Joomla CMS directly from the page without going to admin interface.
* Have an API for interacting with Froala Editor.

:'''Knowledge Prerequisite:''' PHP, object-oriented programming, Joomla CMS (from a user point of view), Javascript.

:'''Difficulty:''' Medium to Hard

:'''Mentors:''' Stefan Neculai, Diana Neculai

===Project: FrontEnd Components-Management and User-Management ===

:'''Brief explanation:''' The aim of this project is to enable frontend logged authorized uses to manage component options and users. This was a idea when redesigning Joomla! and currently is in the CMS Roadmap. During last year global configuration and template configuration got a frontend configuration. Continuing that further there are 2 possible new frontend configurations:
* Frontend management for components
* Frontend user management

Since Joomla! CMS is moving towards Unified Site Administration, this project will play a key role there.

:'''Useful links:'''
* [http://docs.joomla.org/Help32:Menus_Menu_Item_Display_Site_Configuration Site Configuration Frontend]
* [http://docs.joomla.org/Help32:Menus_Menu_Item_Display_Template_Options Template Options Frontend]
* [https://groups.google.com/forum/?fromgroups=#!topic/joomla-dev-cms/BqlSCKcGB8E Discussion in dev-mailing-list]

:'''Expected Results:'''
* Frontend logged authorize users can configure components via frontend
* Frontend logged authorize users can manage users via frontend

:'''Knowledge Prerequisite:''' PHP, Joomla CMS Components, MVC.

:'''Difficulty:''' Medium to Hard

===Project: Enhancing User Profiles===

:'''Brief explanation:''' The aim of this project is to enhance the existing user profiles by allowing to interact with social media. This will create the basic infrastructure for include social media profiles, and cms developers to profile services. Also this will use existing libraries in joomla and provide a flexible way to incorporate profile services.

:'''Expected Results:'''
* cms libraries for profile services (including a local version)
* Managing keys for profile services
* Top-level configuration (for webmasters) on which services are allowed to use
* Enable individual users to specify which Profile service desire to use (select one from allowed ones)
* Modernize frontend com_contact appearance

:'''Knowledge Prerequisite:''' PHP, Joomla! Extensions Development, Understanding on Joomla! libararies (JFacebook, JLinkedin, JGoogle etc.), OAuth, Experience as a Joomla!CMS user.

:'''Difficulty:''' Medium to Hard

== Joomla Framework ==

The Joomla Framework project ideas allows for ideas that can work within the Joomla CMS, or could be completely separate applications that have no connection at all. The Joomla Framework allows for applications to be built for the command line, process daemons and the web.

References:
*[http://github.com/joomla/joomla-framework github Source Code]
*[http://developer.joomla.org/framework/roadmap.html Development Roadmap]
*[http://groups.google.com/d/forum/joomla-dev-framework Developer Mailing List]

All code contributions must follow Joomla coding standards and include full unit test coverage.

{{tip|Please add your Framework project ideas below. You can use the '''[[GSOC 2014 Project Ideas/template|GSOC 2014 Project template]]'''.|title=Adding Project Ideas}}

===Project: Framework Unit Testing===

:'''Brief explanation:''' The Joomla Framework has a good suite of automated Unit Tests, but code coverage is lacking in some areas. The goal of this project is to improve the code coverage by writing unit tests for the Joomla Framework.

:'''Expected Results:''' The student will be expected to review the current [http://developer.joomla.org/framework-coverage/ code coverage report] for the Joomla Framework and write and agreed-upon number of unit tests with particular attention to packages that are below 50% coverage. Preference should be given to non-deprecated classes but the student may choose from either the core tree (/libraries/joomla) or the legacy tree (/libraries/legacy).

:'''Knowledge Prerequisite:''' PHP, PHPUnit

:'''Difficulty:''' Medium

===Project: Improve Filesystem classes===

:'''Brief explanation:''' Replace static methods with public ones of classes File, Folder, Path. Let these things to be used as object with theirs methods and properties. Develop classes, which will be used as adapters, for some fundamental actions performed on those file system elements. The adapters should be for uploading, deleting, reading,...

:'''Expected Results:'''
* A set of well coded, fully unit tested and documented implementations for the file system classes.
* Adapters for managing files on some of the most popular cloud services - Amazon S3, Google App Engine,...
* Classes for validating files size, images,...

:'''Knowledge Prerequisite:''' GitHub, PHPUnit, PHP, OOP, Design Patterns, familiarity with web services and Joomla! Framework.

:'''Difficulty:''' Medium to Hard

===Project: Improve Date classes===

:'''Brief explanation:''' Develop classes and methods that will give more power to developers working with dates.

:'''Expected Results:'''
* Methods that calculate dates for yesterday, begin of week, end of week, begin of month, end of month, begin of year, end of year,...
* Methods that calculate time for begin of day, end of day,...

:'''Knowledge Prerequisite:''' GitHub, PHPUnit, PHP, OOP, Design Patterns, familiarity Joomla! Framework.

:'''Difficulty:''' Medium to Hard

[[Category:Google Summer of Code 2014]]

GSOC 2014 Project Ideas

2014-02-28T04:46:30Z

Buddhima:

[[Image:GSOC_2014.png|300px|left]]

Welcome to the Joomla! Google Summer of Code (GSoC) 2014 project ideas page. As we move forward with the 2014 version of the Joomla! GSoC, we will use this page to develop possible project ideas. Please note that anyone who is interested can participate in this process. You do not have to be a GSoC student or mentor to suggest possible project ideas. Please keep in mind that projects need to be realistically something that is able to be functionally completed by a student working full time for about eight weeks. Thanks!

For students who want a general overview of Joomla's GSoc, project plans, proposals, and timelines, please [http://docs.joomla.org/GSOC_2014 refer to the GSoC 2014 page].

Discussion of ideas and other GSoC related items is welcome on our Google Group: https://groups.google.com/d/forum/joomla-gsoc-2014

If you are interested in participating as a student please review the materials on applying that are available at [http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2013/help_page Google]. We strongly encourage you to ask questions about process and ideas on the mailing list.

If you are interested in serving as a mentor, please fill out the [https://docs.google.com/a/community.joomla.org/spreadsheet/viewform?formkey=dHA2V1lJbThYQXpwMERiRG1FOTZlV3c6MA Mentor Application Form 2014].

== Ideas ==

Opportunities exist for students to work with projects from either the Joomla CMS, the Joomla Framework or in some cases a combination of both.

In addition to this ideas list, the Joomla! Community is able to voice their opinion on features they would like to see via the [http://ideas.joomla.org/ Joomla! Idea Pool]. Those wishing to add ideas to this listing are encouraged to review the Idea Pool and base their idea on the input received there. You can also view the past lists for [[GSOC_2012_Project_Ideas|2013]], [[GSOC_2012_Project_Ideas|2012]], [[Summer_of_Code_2010_Project_Ideas|2010]] and [[Summer_of_Code_2009_Project_Ideas|2009]], which may be useful for reference. We ask that you keep ideas realistic for the time frame that students will have to complete their projects.

Unless a mentor has proposed a specific project, mentors from the mentor pool will be matched with student projects. However members of the mentor pool are available to answer questions on the Joomla GSoC mailing list.

== Important Guidelines on Submitting Ideas ==

There are some important guidelines to submit ideas, please read these carefully before adding your ideas:
* Ensure your idea is able to be completed in a fixed period of time. GSoC runs officially between May 19th 2014 and August 18th 2014. This is a very short period of actual coding time. Ideas should respect the time that students have available for the program.
* Keep ideas realistic. The ideas on this list should maintain a realistic amount of work for a single student, junior level-developer, who is working with a compressed timeline and a fixed completion ('pencils down') date.
* Keep ideas core. The purpose of GSoC is to improve Joomla itself. This is not the time to add ideas for new extensions or features that may not be included by the PLT. If the idea is related to the framework, please consult the framework team directly about new ideas to ensure there is interest in having the package included as an official Joomla Framework package.
* Respect Joomla's Release Cycle. Joomla's release cycle currently states that with Joomla 3.5, we will not add new features to the CMS. This means that most of the GSoC projects this year should ideally improve existing code in a backwards compatible way.
* Joomla 4. Currently there is not a baseline for what Joomla 4 is and what it could be. Ideas centered around Joomla 4 would not fit in well with the goal of GSoC 2014.
* When in doubt, reach out. If you're unsure if your idea belongs on this list, please post to the GSoC 2014 mailing list and ask about the community's interest.
* No documentation-focused projects. Google Summer of ''Code'' is a program about code. We expect our students to document their work, but writing documentation for Joomla as a project does not align with the goals of GSoC.

== Joomla CMS Ideas ==

* [http://github.com/joomla/joomla-cms Source Code]
* [http://groups.google.com/d/forum/joomla-dev-cms Developer Mailing List]

{{tip|Please add your CMS project ideas below. You can use the '''[[GSOC 2014 Project Ideas/template|GSOC 2014 Project template]]'''.|title=Adding Project Ideas}}

===Project: Refactor CMS to use Dependency Injection ===

:'''Brief explanation:''' The CMS currently has many hard-coded JPATH constants and a JFactory for developers to get certain global objects from the application. This project would develop a way to depreciate the current system which is difficult to test and is tightly coupled. The project will replace the JPATH constants with the Joomla Framework Dependency Injection package, allowing for a looser coupling of the application's core components.

For more info see:
* [https://github.com/joomla/joomla-framework/tree/staging/src/Joomla/DI Joomla Framework DI Package]
* [https://github.com/joomla/joomla-cms/blob/staging/includes/defines.php Joomla CMS Constants]

:'''Expected Results:'''
* Deprecate the current JPATH constants allowing for replacement with Joomla DI
* Refactor core components and to use new DI container
* Write documentation for developers to update their extensions to use Joomla DI

:'''Knowledge Prerequisite:''' PHP, object-oriented programming, Joomla CMS (from a user point of view), Understanding of Dependency Injection and Dependency Injection Containers.

:'''Difficulty:''' Medium to Hard

===Project: Webdriver system tests for CMS===

:'''Brief explanation:''' Automated system tests allow us to test the CMS by automatically running Joomla from a browser, selecting menu options, and evaluating results. At present, several number of [https://github.com/joomla/joomla-cms/tree/staging/tests/system system tests] are currently completed using the Selenium Webdriver technology and using the Page Objects pattern to separate the page objects from the test objects. This project will build on the current base of Webdriver tests and expand the test coverage to include more of the CMS.

For more info see:
* http://docs.joomla.org/System_Testing
* http://www.youtube.com/watch?v=8Mmg32lg4nA

:'''Expected Results:'''
* finish the administrator parts not yet tested
* add front end testing:
** menu items
** modules

:'''Knowledge Prerequisite:''' PHP, object-oriented programming, Joomla CMS (from a user point of view), HTML

:'''Difficulty:''' Medium to Hard

:'''Possible mentors:''' Puneet Kala, Mark Dexter and Javier Gómez

=== Project: Collection of Mini Projects ===

:'''Brief explanation:''' The CMS currently could due with several smaller tasks and projects to help move the software forward and improve its usability and feature set. This project is a *collection* of several smaller projects and improvements. The tasks involved are discrete but they must all be accomplished to a high degree of quality in detail to be considered successful.

===== Decouple Core Extensions =====
:''' Description''' In the current version of the CMS, some extensions rely on one another for functionality. The ultimate goal is for each extension to be completely independent so that it could be removed without breaking the functionality of another.

===== Add Menu Type ACL =====
:''' Description ''' Currently in the CMS there is no way to have backend based ACL rules per menu-type. This project should add advanced ACL rules and configurability to Joomla's core menu types. Adding, deleting, and editing menus on a per-menu group basis should be available on a per-group basis.

===== JError to Exceptions =====
:''' Description ''' Currently Joomla uses the JError class to handle error management - however there is a desire to move this across to use exceptions for Joomla 4.0 and remove the JError class.

:'''Expected Results:''' This project must address and complete each of the above described mini-projects. Proposals should detail each item in detail and outline a timeline for completing them.

===== Implementing Frontend Menu Editing =====
:''' Description ''' Currently frontend menu editing icon redirects user to backend. But actually frontend menu editing should be able to done at the frontend.Implementation would be much similar to the already implemented frontend configuration & frontend template style editing.

:'''Expected Results:''' Frontend logged authorized users should be able to edit menu items via frontend. Student should have to figure-out what should be in frontend editor and relevant access control levels.

:'''Knowledge Prerequisite:''' General knowledge of Joomla 3's core feature set and functionality.

:'''Difficulty:''' Medium to Hard

=== Project: Develop dependency manager ===

:'''Brief explanation:''' Distributions are one of the next possible evolutionary steps for the CMS. One key challenge to solve is the management of dependencies that extensions/packages may have.

:'''Expected Results:''' A working proof of concept that manages the handling of dependencies as well as define requirements that extensions/packages must meet for their dependencies to be managed by this system.

:'''Knowledge Prerequisite:'''

:'''Difficulty:''' Very challenging, but highly rewarding.

=== Project: Update Core Extensions to use New MVC ===

:'''Brief explanation:''' The Joomla Framework has brought us a new MVC architecture that we would like to start using for core components. This project will chose a few core components as a conversion goal to migrate them to run on the new MVC structure.

:'''Expected Results:''' Selected core components will run on the new MVC architecture. This will involve changing the component to run the new controller based architecture, and potentially develop a standardized set of methods that are used across multiple extensions. Reducing code repeats and encouraging reuse will be an important aspect of this project.

:'''Knowledge Prerequisite:'''

:'''Difficulty:''' Challenging, high learning curve and will set precedent for other extensions. This is a opportunity for innovation, not a project to simply copy other parts code into a new feature.

:'''Potential Mentors:''' Soren Beck Jensen as he runs the http://www.Component-Creator.com and Buddhima Wijeweera as he worked on a similar project for GSoC 2013 http://magazine.joomla.org/issues/issue-nov-2013/item/1580-new-mvc-for-joomla-cms

===Project: SQL Optimization===

:'''Brief explanation:''' The goal of this project is to optimize site performances, between the potential areas where performance bottleneck resides in a conventional n-tier website architecture, we'll focus our effort on database side, optimizing slow sql queries.

:'''Expected Results:''' After analyzing and measuring the site performance (on some test case ie small, medium, big) will be taken the necessary action using the proper techniques to improve measurably the slower queries.

:'''Knowledge Prerequisite:''' SQL, DBMS

:'''Difficulty:''' Medium to Hard

:'''Potential mentors:''' Nicola Galgano

===Project: JIssues tracker===

:'''Brief explanation:''' The goal of this project is to finish the JIssues tracker so it is in a position to replace the current Joomla tracker.

:'''Expected Results:''' The JIssues tracker will be at a place where a transition can take place from Joomla Code to the issues tracker. This will involve working with the JIssues (http://issues.joomla.org/) and working through the issue list (https://github.com/joomla/jissues) as well as contributing any relevant code back into the Framework Project

:'''Knowledge Prerequisite:''' Joomla Framework, JoomlaCode, Joomla Bug Tracking Process

:'''Difficulty:''' Medium to Hard

:'''Posible mentors:''' Michael Babker




<noinclude>[[Category:Google Summer of Code 2014]]</noinclude>

===Project: Component for managing predefined emails ===

:'''Brief explanation:''' Many Joomla! extensions send confirmation mails to users. It will be great if Joomla! provides a powerful component, which will be used for creating predefined emails. The component has to provide classes, which will be used from developers for loading, parsing and sending those e-mails.

:'''Expected Results:'''
* Administration interface that will provide an easy way for creating and managing predefined emails.
* Classes that will be used for loading, parsing and sending those emails.

:'''Knowledge Prerequisite:''' PHP, object-oriented programming, Joomla CMS.

:'''Difficulty:''' Medium to Hard

:'''Possible mentors:''' Todor Iliev, Daniel Dimitrov

===Project: Inline editing directly on any page ===

:'''Brief explanation:''' The aim of this project is to add in the possibility of editing any page in Joomla using an inline editing tool. It would make articles editing easier, being able to do that without going to the admin interface. The proposed editor is Froala Editor(in inline mode) and it must interact with the media manager and use language support. The final result should be similar to [http://www.youtube.com/watch?v=5YE8ISXkLXM].

:'''Useful links:'''
* [http://editor.froala.com Froala Editor]
* [https://groups.google.com/forum/#!topic/joomla-dev-cms/giQzWj7fIj8 Discussion about it on CMS list] - please ignore the long comments about the license. It will be sorted out.

:'''Expected Results:'''
* Edit articles in Joomla CMS directly from the page without going to admin interface.
* Have an API for interacting with Froala Editor.

:'''Knowledge Prerequisite:''' PHP, object-oriented programming, Joomla CMS (from a user point of view), Javascript.

:'''Difficulty:''' Medium to Hard

:'''Mentors:''' Stefan Neculai, Diana Neculai

===Project: FrontEnd Components-Management and User-Management ===

:'''Brief explanation:''' The aim of this project is to enable frontend logged authorized uses to manage component options and users. This was a idea when redesigning Joomla! and currently is in the CMS Roadmap. During last year global configuration and template configuration got a frontend configuration. Continuing that further there are 2 possible new frontend configurations:
* Frontend management for components
* Frontend user management

Since Joomla! CMS is moving towards Unified Site Administration, this project will play a key role there.

:'''Useful links:'''
* [http://docs.joomla.org/Help32:Menus_Menu_Item_Display_Site_Configuration Site Configuration Frontend]
* [http://docs.joomla.org/Help32:Menus_Menu_Item_Display_Template_Options Template Options Frontend]
* [https://groups.google.com/forum/?fromgroups=#!topic/joomla-dev-cms/BqlSCKcGB8E Discussion in dev-mailing-list]

:'''Expected Results:'''
* Frontend logged authorize users can configure components via frontend
* Frontend logged authorize users can manage users via frontend

:'''Knowledge Prerequisite:''' PHP, Joomla CMS Components, MVC.

:'''Difficulty:''' Medium to Hard

== Joomla Framework ==

The Joomla Framework project ideas allows for ideas that can work within the Joomla CMS, or could be completely separate applications that have no connection at all. The Joomla Framework allows for applications to be built for the command line, process daemons and the web.

References:
*[http://github.com/joomla/joomla-framework github Source Code]
*[http://developer.joomla.org/framework/roadmap.html Development Roadmap]
*[http://groups.google.com/d/forum/joomla-dev-framework Developer Mailing List]

All code contributions must follow Joomla coding standards and include full unit test coverage.

{{tip|Please add your Framework project ideas below. You can use the '''[[GSOC 2014 Project Ideas/template|GSOC 2014 Project template]]'''.|title=Adding Project Ideas}}

===Project: Framework Unit Testing===

:'''Brief explanation:''' The Joomla Framework has a good suite of automated Unit Tests, but code coverage is lacking in some areas. The goal of this project is to improve the code coverage by writing unit tests for the Joomla Framework.

:'''Expected Results:''' The student will be expected to review the current [http://developer.joomla.org/framework-coverage/ code coverage report] for the Joomla Framework and write and agreed-upon number of unit tests with particular attention to packages that are below 50% coverage. Preference should be given to non-deprecated classes but the student may choose from either the core tree (/libraries/joomla) or the legacy tree (/libraries/legacy).

:'''Knowledge Prerequisite:''' PHP, PHPUnit

:'''Difficulty:''' Medium

===Project: Improve Filesystem classes===

:'''Brief explanation:''' Replace static methods with public ones of classes File, Folder, Path. Let these things to be used as object with theirs methods and properties. Develop classes, which will be used as adapters, for some fundamental actions performed on those file system elements. The adapters should be for uploading, deleting, reading,...

:'''Expected Results:'''
* A set of well coded, fully unit tested and documented implementations for the file system classes.
* Adapters for managing files on some of the most popular cloud services - Amazon S3, Google App Engine,...
* Classes for validating files size, images,...

:'''Knowledge Prerequisite:''' GitHub, PHPUnit, PHP, OOP, Design Patterns, familiarity with web services and Joomla! Framework.

:'''Difficulty:''' Medium to Hard

===Project: Improve Date classes===

:'''Brief explanation:''' Develop classes and methods that will give more power to developers working with dates.

:'''Expected Results:'''
* Methods that calculate dates for yesterday, begin of week, end of week, begin of month, end of month, begin of year, end of year,...
* Methods that calculate time for begin of day, end of day,...

:'''Knowledge Prerequisite:''' GitHub, PHPUnit, PHP, OOP, Design Patterns, familiarity Joomla! Framework.

:'''Difficulty:''' Medium to Hard

[[Category:Google Summer of Code 2014]]

GSOC 2014 Project Ideas

2014-02-14T18:58:30Z

Buddhima:

Help310:Menus Menu Item Display Template Options

2013-11-12T06:00:35Z

Buddhima:

{{RightTOC}}
This is a simplified version to change current template settings from front end.
== How To Access ==
To create a new Display Template Options Menu Item:
* Select {{rarr|Menus,[name of the menu]}} from the drop-down menu on the back-end of your Joomla! installation (for example, {{rarr|Menus,Main Menu}}).
* Click the New Toolbar button to create a new menu item.
* Click the Menu Item Type Select button [[File:Help30-Menu-Item-Type-Select-Button.png]] and then click the Display Template Options Menu Item link under Configuration Manager.

To edit an existing Display Template Options Menu Item, click its Title in [[Help30:Menus_Menu_Item_Manager|Menu Manager: Menu Items]].

== Description ==
This menu item can be helpful to new Joomla! super-users to easily change the template options. This will provide current template options in front end. Options to display can be customized[1] . Therefore after a change, super-user will see the results immediately.
== Screenshot ==
[[Image:Help32-Menus-Menu-Display_Template_Options-screenshot.png]]
== Details ==
=== Details Tab ===
{{Chunk30:colheader|Status}}
{{Chunk30:colheader|Menu Title}}
{{Chunk30:colheader|Alias}}
{{Chunk30:colheader|Menu Item Link}}
{{Chunk30:colheader|Menu Location}}
{{Chunk30:colheader|Parent Item}}
{{Chunk30:colheader|Menu Item Ordering}}
{{Chunk30:colheader|Access}}
{{Chunk30:colheader|Default Page}}
{{Chunk30:colheader|Target Window}}
{{Chunk30:colheader|Template Style}}
{{Chunk30:colheader|Language}}
{{Chunk30:colheader|Note}}

For more information please see Menu Item Manager: [[Help30:Menus_Menu_Item_Manager_Edit#New Menu Item Details|Details Tab]]
==== Required Settings ====
{{chunk30:colheader|Menu Title}}
{{chunk30:colheader|Menu Location}}

===Link Type Options===
{{Chunk30:Link Type Options}}

=== Page Display Tab ===
{{Chunk30:Page Display Options}}

=== Metadata Tab ===
{{Chunk30:Metadata Options}}

===Module Assignments Tab===
{{Chunk30:Module Assignment}}

== Toolbar ==
At the top left you will see the toolbar:

[[Image:Help32-Save-SaveClose-SaveNew-SaveAsCopy-Close-toolbar.png]]

The functions are:
{{Chunk30:Help_screen_toolbar_icon_Save|menu item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndClose|menu item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndNew|menu item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAsCopy|menu item}}
{{Chunk30:Help_screen_toolbar_icon_Cancel}}
{{Chunk30:Help_screen_toolbar_icon_Help}}

== Front End Screenshot ==
[[Image:Help32-Menus-Menu-Display_Template_Options-front-end-screenshot.png]]

== Other Resources ==
[1]. [[Using_com_config_for_frontend_template_style_editing]]

File:Help32-Menus-Menu-Display Template Options-screenshot-en.png

2013-11-12T05:57:00Z

Buddhima: Buddhima uploaded a new version of "File:Help32-Menus-Menu-Display Template Options-screenshot.png"

Help310:Menus Menu Item Display Template Options

2013-11-12T05:54:21Z

Buddhima: Created page with "{{RightTOC}} This is a simplified version to change current template settings from front end. == How To Access == To create a new Display Site Configuration Menu Item: * Selec..."

{{RightTOC}}
This is a simplified version to change current template settings from front end.
== How To Access ==
To create a new Display Site Configuration Menu Item:
* Select {{rarr|Menus,[name of the menu]}} from the drop-down menu on the back-end of your Joomla! installation (for example, {{rarr|Menus,Main Menu}}).
* Click the New Toolbar button to create a new menu item.
* Click the Menu Item Type Select button [[File:Help30-Menu-Item-Type-Select-Button.png]] and then click the Display Site Configuration Menu Item link under Configuration Manager.

To edit an existing Display Site Configuration Menu Item, click its Title in [[Help30:Menus_Menu_Item_Manager|Menu Manager: Menu Items]].

== Description ==
This menu item can be helpful to new Joomla! super-users to easily change the template options. This will provide current template options in front end. Options to display can be customized[1] . Therefore after a change, super-user will see the results immediately.
== Screenshot ==
[[Image:Help32-Menus-Menu-Display_Template_Options-screenshot.png]]
== Details ==
=== Details Tab ===
{{Chunk30:colheader|Status}}
{{Chunk30:colheader|Menu Title}}
{{Chunk30:colheader|Alias}}
{{Chunk30:colheader|Menu Item Link}}
{{Chunk30:colheader|Menu Location}}
{{Chunk30:colheader|Parent Item}}
{{Chunk30:colheader|Menu Item Ordering}}
{{Chunk30:colheader|Access}}
{{Chunk30:colheader|Default Page}}
{{Chunk30:colheader|Target Window}}
{{Chunk30:colheader|Template Style}}
{{Chunk30:colheader|Language}}
{{Chunk30:colheader|Note}}

For more information please see Menu Item Manager: [[Help30:Menus_Menu_Item_Manager_Edit#New Menu Item Details|Details Tab]]
==== Required Settings ====
{{chunk30:colheader|Menu Title}}
{{chunk30:colheader|Menu Location}}

===Link Type Options===
{{Chunk30:Link Type Options}}

=== Page Display Tab ===
{{Chunk30:Page Display Options}}

=== Metadata Tab ===
{{Chunk30:Metadata Options}}

===Module Assignments Tab===
{{Chunk30:Module Assignment}}

== Toolbar ==
At the top left you will see the toolbar:

[[Image:Help32-Save-SaveClose-SaveNew-SaveAsCopy-Close-toolbar.png]]

The functions are:
{{Chunk30:Help_screen_toolbar_icon_Save|menu item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndClose|menu item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndNew|menu item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAsCopy|menu item}}
{{Chunk30:Help_screen_toolbar_icon_Cancel}}
{{Chunk30:Help_screen_toolbar_icon_Help}}

== Front End Screenshot ==
[[Image:Help32-Menus-Menu-Display_Template_Options-front-end-screenshot.png]]

== Other Resources ==
[1]. [[Using_com_config_for_frontend_template_style_editing]]

File:Help32-Menus-Menu-Display Template Options-front-end-screenshot-en.png

2013-11-12T05:49:39Z

Buddhima:

File:Help32-Menus-Menu-Display Template Options-screenshot-en.png

2013-11-12T05:48:46Z

Buddhima:

Help310:Menus Menu Item Display Site Configuration

2013-11-12T05:33:38Z

Buddhima:

{{RightTOC}}
This is a simplified version of [http://docs.joomla.org/Help32:Site_Global_Configuration Site Global Configuration], which can change site settings from front end.
== How To Access ==
To create a new Display Site Configuration Menu Item:
* Select {{rarr|Menus,[name of the menu]}} from the drop-down menu on the back-end of your Joomla! installation (for example, {{rarr|Menus,Main Menu}}).
* Click the New Toolbar button to create a new menu item.
* Click the Menu Item Type Select button [[File:Help30-Menu-Item-Type-Select-Button.png]] and then click the Display Site Configuration Menu Item link under Configuration Manager.

To edit an existing Display Site Configuration Menu Item, click its Title in [[Help30:Menus_Menu_Item_Manager|Menu Manager: Menu Items]].

== Description ==
This menu item can be helpful to new Joomla! super-users to easily change the site configurations. This will provide some of the important site configurations in front end. Therefore after a change, super-user will see the results immediately.
== Screenshot ==
[[Image:Help32-Menus-Menu-Display_Configuration-screenshot.png]]
== Details ==
=== Details Tab ===
{{Chunk30:colheader|Status}}
{{Chunk30:colheader|Menu Title}}
{{Chunk30:colheader|Alias}}
{{Chunk30:colheader|Menu Item Link}}
{{Chunk30:colheader|Menu Location}}
{{Chunk30:colheader|Parent Item}}
{{Chunk30:colheader|Menu Item Ordering}}
{{Chunk30:colheader|Access}}
{{Chunk30:colheader|Default Page}}
{{Chunk30:colheader|Target Window}}
{{Chunk30:colheader|Template Style}}
{{Chunk30:colheader|Language}}
{{Chunk30:colheader|Note}}

For more information please see Menu Item Manager: [[Help30:Menus_Menu_Item_Manager_Edit#New Menu Item Details|Details Tab]]
==== Required Settings ====
{{chunk30:colheader|Menu Title}}
{{chunk30:colheader|Menu Location}}

===Link Type Options===
{{Chunk30:Link Type Options}}

=== Page Display Tab ===
{{Chunk30:Page Display Options}}

=== Metadata Tab ===
{{Chunk30:Metadata Options}}

===Module Assignments Tab===
{{Chunk30:Module Assignment}}

== Toolbar ==
At the top left you will see the toolbar:

[[Image:Help32-Save-SaveClose-SaveNew-SaveAsCopy-Close-toolbar.png]]

The functions are:
{{Chunk30:Help_screen_toolbar_icon_Save|menu item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndClose|menu item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndNew|menu item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAsCopy|menu item}}
{{Chunk30:Help_screen_toolbar_icon_Cancel}}
{{Chunk30:Help_screen_toolbar_icon_Help}}

== Front End Screenshot ==
[[Image:Help32-Menus-Menu-Display_Configuration-front-end-screenshot.png]]

Help310:Menus Menu Item Display Site Configuration

2013-11-12T05:31:18Z

Buddhima:

{{RightTOC}}
This is a simplified version of [http://Help32:Site_Global_Configuration Site Global Configuration], which can change site settings from front end.
== How To Access ==
To create a new Display Site Configuration Menu Item:
* Select {{rarr|Menus,[name of the menu]}} from the drop-down menu on the back-end of your Joomla! installation (for example, {{rarr|Menus,Main Menu}}).
* Click the New Toolbar button to create a new menu item.
* Click the Menu Item Type Select button [[File:Help30-Menu-Item-Type-Select-Button.png]] and then click the Display Site Configuration Menu Item link under Configuration Manager.

To edit an existing Display Site Configuration Menu Item, click its Title in [[Help30:Menus_Menu_Item_Manager|Menu Manager: Menu Items]].

== Description ==
This menu item can be helpful to new Joomla! super-users to easily change the site configurations. This will provide some of the important site configurations in front end. Therefore after a change, super-user will see the results immediately.
== Screenshot ==
[[Image:Help32-Menus-Menu-Display_Configuration-screenshot.png]]
== Details ==
=== Details Tab ===
{{Chunk30:colheader|Status}}
{{Chunk30:colheader|Menu Title}}
{{Chunk30:colheader|Alias}}
{{Chunk30:colheader|Menu Item Link}}
{{Chunk30:colheader|Menu Location}}
{{Chunk30:colheader|Parent Item}}
{{Chunk30:colheader|Menu Item Ordering}}
{{Chunk30:colheader|Access}}
{{Chunk30:colheader|Default Page}}
{{Chunk30:colheader|Target Window}}
{{Chunk30:colheader|Template Style}}
{{Chunk30:colheader|Language}}
{{Chunk30:colheader|Note}}

For more information please see Menu Item Manager: [[Help30:Menus_Menu_Item_Manager_Edit#New Menu Item Details|Details Tab]]
==== Required Settings ====
{{chunk30:colheader|Menu Title}}
{{chunk30:colheader|Menu Location}}

===Link Type Options===
{{Chunk30:Link Type Options}}

=== Page Display Tab ===
{{Chunk30:Page Display Options}}

=== Metadata Tab ===
{{Chunk30:Metadata Options}}

===Module Assignments Tab===
{{Chunk30:Module Assignment}}

== Toolbar ==
At the top left you will see the toolbar:

[[Image:Help32-Save-SaveClose-SaveNew-SaveAsCopy-Close-toolbar.png]]

The functions are:
{{Chunk30:Help_screen_toolbar_icon_Save|menu item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndClose|menu item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndNew|menu item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAsCopy|menu item}}
{{Chunk30:Help_screen_toolbar_icon_Cancel}}
{{Chunk30:Help_screen_toolbar_icon_Help}}

== Front End Screenshot ==
[[Image:Help32-Menus-Menu-Display_Configuration-front-end-screenshot.png]]

Help310:Menus Menu Item Display Site Configuration

2013-11-12T05:29:08Z

Buddhima:

{{RightTOC}}
This is a simplified version of [[http://docs.joomla.org/Help32:Site_Global_Configuration]]Site Global Configuration, which can change site settings from front end.
== How To Access ==
To create a new Display Site Configuration Menu Item:
* Select {{rarr|Menus,[name of the menu]}} from the drop-down menu on the back-end of your Joomla! installation (for example, {{rarr|Menus,Main Menu}}).
* Click the New Toolbar button to create a new menu item.
* Click the Menu Item Type Select button [[File:Help30-Menu-Item-Type-Select-Button.png]] and then click the Display Site Configuration Menu Item link under Configuration Manager.

To edit an existing Display Site Configuration Menu Item, click its Title in [[Help30:Menus_Menu_Item_Manager|Menu Manager: Menu Items]].

== Description ==
This menu item can be helpful to new Joomla! super-users to easily change the site configurations. This will provide some of the important site configurations in front end. Therefore after a change, super-user will see the results immediately.
== Screenshot ==
[[Image:Help32-Menus-Menu-Display_Configuration-screenshot.png]]
== Details ==
=== Details Tab ===
{{Chunk30:colheader|Status}}
{{Chunk30:colheader|Menu Title}}
{{Chunk30:colheader|Alias}}
{{Chunk30:colheader|Menu Item Link}}
{{Chunk30:colheader|Menu Location}}
{{Chunk30:colheader|Parent Item}}
{{Chunk30:colheader|Menu Item Ordering}}
{{Chunk30:colheader|Access}}
{{Chunk30:colheader|Default Page}}
{{Chunk30:colheader|Target Window}}
{{Chunk30:colheader|Template Style}}
{{Chunk30:colheader|Language}}
{{Chunk30:colheader|Note}}

For more information please see Menu Item Manager: [[Help30:Menus_Menu_Item_Manager_Edit#New Menu Item Details|Details Tab]]
==== Required Settings ====
{{chunk30:colheader|Menu Title}}
{{chunk30:colheader|Menu Location}}

===Link Type Options===
{{Chunk30:Link Type Options}}

=== Page Display Tab ===
{{Chunk30:Page Display Options}}

=== Metadata Tab ===
{{Chunk30:Metadata Options}}

===Module Assignments Tab===
{{Chunk30:Module Assignment}}

== Toolbar ==
At the top left you will see the toolbar:

[[Image:Help32-Save-SaveClose-SaveNew-SaveAsCopy-Close-toolbar.png]]

The functions are:
{{Chunk30:Help_screen_toolbar_icon_Save|menu item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndClose|menu item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndNew|menu item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAsCopy|menu item}}
{{Chunk30:Help_screen_toolbar_icon_Cancel}}
{{Chunk30:Help_screen_toolbar_icon_Help}}

== Front End Screenshot ==
[[Image:Help32-Menus-Menu-Display_Configuration-front-end-screenshot.png]]

Help310:Menus Menu Item Display Site Configuration

2013-11-12T05:17:09Z

Buddhima:

{{RightTOC}}
This is a simplified version of Site Global Configuration, which can change site settings from front end.
== How To Access ==
To create a new Display Site Configuration Menu Item:
* Select {{rarr|Menus,[name of the menu]}} from the drop-down menu on the back-end of your Joomla! installation (for example, {{rarr|Menus,Main Menu}}).
* Click the New Toolbar button to create a new menu item.
* Click the Menu Item Type Select button [[File:Help30-Menu-Item-Type-Select-Button.png]] and then click the Display Site Configuration Menu Item link under Configuration Manager.

To edit an existing Display Site Configuration Menu Item, click its Title in [[Help30:Menus_Menu_Item_Manager|Menu Manager: Menu Items]].

== Description ==
This menu item can be helpful to new Joomla! super-users to easily change the site configurations. This will provide some of the important site configurations in front end. Therefore after a change, super-user will see the results immediately.
== Screenshot ==
[[Image:Help32-Menus-Menu-Display_Configuration-screenshot.png]]
== Details ==
=== Details Tab ===
{{Chunk30:colheader|Status}}
{{Chunk30:colheader|Menu Title}}
{{Chunk30:colheader|Alias}}
{{Chunk30:colheader|Menu Item Link}}
{{Chunk30:colheader|Menu Location}}
{{Chunk30:colheader|Parent Item}}
{{Chunk30:colheader|Menu Item Ordering}}
{{Chunk30:colheader|Access}}
{{Chunk30:colheader|Default Page}}
{{Chunk30:colheader|Target Window}}
{{Chunk30:colheader|Template Style}}
{{Chunk30:colheader|Language}}
{{Chunk30:colheader|Note}}

For more information please see Menu Item Manager: [[Help30:Menus_Menu_Item_Manager_Edit#New Menu Item Details|Details Tab]]
==== Required Settings ====
{{chunk30:colheader|Menu Title}}
{{chunk30:colheader|Menu Location}}

===Link Type Options===
{{Chunk30:Link Type Options}}

=== Page Display Tab ===
{{Chunk30:Page Display Options}}

=== Metadata Tab ===
{{Chunk30:Metadata Options}}

===Module Assignments Tab===
{{Chunk30:Module Assignment}}

== Toolbar ==
At the top left you will see the toolbar:

[[Image:Help32-Save-SaveClose-SaveNew-SaveAsCopy-Close-toolbar.png]]

The functions are:
{{Chunk30:Help_screen_toolbar_icon_Save|menu item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndClose|menu item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndNew|menu item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAsCopy|menu item}}
{{Chunk30:Help_screen_toolbar_icon_Cancel}}
{{Chunk30:Help_screen_toolbar_icon_Help}}

== Front End Screenshot ==
[[Image:Help32-Menus-Menu-Display_Configuration-front-end-screenshot.png]]

Help310:Menus Menu Item Display Site Configuration

2013-11-12T04:53:36Z

Buddhima:

{{RightTOC}}
This is a simplified version of Site Global Configuration, which can change site settings from front end.
== How To Access ==
To create a new Display Site Configuration Menu Item:
* Select {{rarr|Menus,[name of the menu]}} from the drop-down menu on the back-end of your Joomla! installation (for example, {{rarr|Menus,Main Menu}}).
* Click the New Toolbar button to create a new menu item.
* Click the Menu Item Type Select button [[File:Help30-Menu-Item-Type-Select-Button.png]] and then click the Display Site Configuration Menu Item link under Configuration Manager.

To edit an existing Display Site Configuration Menu Item, click its Title in [[Help30:Menus_Menu_Item_Manager|Menu Manager: Menu Items]].

== Description ==

== Screenshot ==
[[Image:Help32-Menus-Menu-Display_Configuration-screenshot.png]]
== Details ==
=== Details Tab ===
{{Chunk30:colheader|Status}}
{{Chunk30:colheader|Menu Title}}
{{Chunk30:colheader|Alias}}
{{Chunk30:colheader|Menu Item Link}}
{{Chunk30:colheader|Menu Location}}
{{Chunk30:colheader|Parent Item}}
{{Chunk30:colheader|Menu Item Ordering}}
{{Chunk30:colheader|Access}}
{{Chunk30:colheader|Default Page}}
{{Chunk30:colheader|Target Window}}
{{Chunk30:colheader|Template Style}}
{{Chunk30:colheader|Language}}
{{Chunk30:colheader|Note}}

For more information please see Menu Item Manager: [[Help30:Menus_Menu_Item_Manager_Edit#New Menu Item Details|Details Tab]]
==== Required Settings ====
{{chunk30:colheader|Menu Title}}
{{chunk30:colheader|Menu Location}}

===Link Type Options===
{{Chunk30:Link Type Options}}

=== Page Display Tab ===
{{Chunk30:Page Display Options}}

=== Metadata Tab ===
{{Chunk30:Metadata Options}}

===Module Assignments Tab===
{{Chunk30:Module Assignment}}

== Toolbar ==
At the top left you will see the toolbar:

[[Image:Help32-Save-SaveClose-SaveNew-SaveAsCopy-Close-toolbar.png]]

The functions are:
{{Chunk30:Help_screen_toolbar_icon_Save|menu item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndClose|menu item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndNew|menu item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAsCopy|menu item}}
{{Chunk30:Help_screen_toolbar_icon_Cancel}}
{{Chunk30:Help_screen_toolbar_icon_Help}}

== Front End Screenshot ==
[[Image:Help32-Menus-Menu-Display_Configuration-front-end-screenshot.png]]

File:Help32-Menus-Menu-Display Configuration-front-end-screenshot-en.png

2013-11-12T04:41:41Z

Buddhima:

File:Help32-Menus-Menu-Display Configuration-screenshot-en.png

2013-11-12T04:37:34Z

Buddhima:

Help310:Menus Menu Item Display Site Configuration

2013-11-12T03:36:41Z

Buddhima:

{{RightTOC}}
This is a simplified version of Site Global Configuration, which can change site settings from front end.
== How To Access ==
To create a new Display Site Configuration Menu Item:
* Select {{rarr|Menus,[name of the menu]}} from the drop-down menu on the back-end of your Joomla! installation (for example, {{rarr|Menus,Main Menu}}).
* Click the New Toolbar button to create a new menu item.
* Click the Menu Item Type Select button [[File:Help30-Menu-Item-Type-Select-Button.png]] and then click the Display Site Configuration Menu Item link under Configuration Manager.

To edit an existing Display Site Configuration Menu Item, click its Title in [[Help30:Menus_Menu_Item_Manager|Menu Manager: Menu Items]].

== Description ==

== Screenshot ==

== Details ==
=== Details Tab ===
For more information please see Menu Item Manager: [[Help30:Menus_Menu_Item_Manager_Edit#New Menu Item Details|Details Tab]]
==== Required Settings ====
{{chunk30:colheader|Menu Title}}
{{chunk30:colheader|Menu Location}}

===Link Type Options===
See [[Help30:Menus_Menu_Item_Manager_Edit|Menu Item Manager: New Menu Item]] for help on fields in '''[[Help30:Menus_Menu_Item_Manager_Edit#Link Type Options|Link Type Options]]''' for this Menu Item.

=== Page Display Tab ===
See [[Help30:Menus_Menu_Item_Manager_Edit|Menu Item Manager: New Menu Item]] for help on fields in '''[[Help30:Menus_Menu_Item_Manager_Edit#Page Display Options|Page Display Options]]''' for this Menu Item.

=== Metadata Tab ===
See [[Help30:Menus_Menu_Item_Manager_Edit|Menu Item Manager: New Menu Item]] for help on fields in '''[[Help30:Menus_Menu_Item_Manager_Edit#Metadata Options|Metadata Options]]''' for this Menu Item.

===Module Assignments Tab===
See [[Help30:Menus_Menu_Item_Manager_Edit|Menu Item Manager: New Menu Item]] for help on fields in '''[[Help30:Menus_Menu_Item_Manager_Edit#Module Assignment Tab|Module Assignments]]''' for this Menu Item.

== Toolbar ==
At the top left you will see the toolbar:

[[Image:Help30-Save-SaveClose-SaveNew-Cancel-Help-toolbar.png]]

The functions are:
{{Chunk30:Help_screen_toolbar_icon_Save|menu item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndClose|menu item}}
{{Chunk30:Help_screen_toolbar_icon_SaveAndNew|menu item}}
{{Chunk30:Help_screen_toolbar_icon_Cancel}}
{{Chunk30:Help_screen_toolbar_icon_Help}}

== Front End Screenshot ==

Help310:Menus Menu Item Display Site Configuration

2013-11-12T03:28:29Z

Buddhima:

{{RightTOC}}
This is a simplified version of Site Global Configuration, which can change site settings from front end.
== How To Access ==

== Description ==

== Screenshot ==

== Details ==
=== Details Tab ===
For more information please see Menu Item Manager: [[Help30:Menus_Menu_Item_Manager_Edit#New Menu Item Details|Details Tab]]
==== Required Settings ====
{{chunk30:colheader|Menu Title}}
{{chunk30:colheader|Menu Location}}

===Link Type Options===
See [[Help30:Menus_Menu_Item_Manager_Edit|Menu Item Manager: New Menu Item]] for help on fields in '''[[Help30:Menus_Menu_Item_Manager_Edit#Link Type Options|Link Type Options]]''' for this Menu Item.

=== Page Display Tab ===
See [[Help30:Menus_Menu_Item_Manager_Edit|Menu Item Manager: New Menu Item]] for help on fields in '''[[Help30:Menus_Menu_Item_Manager_Edit#Page Display Options|Page Display Options]]''' for this Menu Item.

=== Metadata Tab ===
See [[Help30:Menus_Menu_Item_Manager_Edit|Menu Item Manager: New Menu Item]] for help on fields in '''[[Help30:Menus_Menu_Item_Manager_Edit#Metadata Options|Metadata Options]]''' for this Menu Item.

===Module Assignments Tab===
See [[Help30:Menus_Menu_Item_Manager_Edit|Menu Item Manager: New Menu Item]] for help on fields in '''[[Help30:Menus_Menu_Item_Manager_Edit#Module Assignment Tab|Module Assignments]]''' for this Menu Item.

== Toolbar ==

== Front End Screenshot ==

Help310:Menus Menu Item Display Site Configuration

2013-11-12T03:19:29Z

Buddhima:

Help310:Menus Menu Item Display Site Configuration

2013-11-12T03:05:47Z

Buddhima:

This is a simplified version of Site Global Configuration, which can change site settings from front end.
How To Access

Description

Screenshot

Details

Toolbar

Front End Screenshot

Help310:Menus Menu Item Display Site Configuration

2013-11-12T03:04:10Z

Buddhima: This is a simplified version of Global Configuration which can change site settings from front end.

How To Access

Description

Screenshot

Details

Toolbar

Front End Screenshot

Using com config for frontend template style editing

2013-10-15T10:22:29Z

Buddhima:

{{version/tutor|3.2}}
{{RightTOC}}
== Introduction ==
In early versions, it was a bit difficult thing for users to figure out how to change basic settings after installing Joomla! for the first time. To reduce that difficulty front-end component com_config make it possible to do some of those settings through front-end. Through this template view of com_config, super users can easily change current template style parameters and view the changes soon after clicking Save!

== Access to Templates View ==
For beginners, we encourage you to install Joomla! With sample data '''Blog English (GB) Sample Data''' or '''Brochure English (GB) Sample Data'''. If you installed with one of two data sets, you can access it by clicking “Template Settings” on Main Menu (login as super-user will be required).

In other cases you can simply add it to the any menu. Following steps are for adding it to Main menu (super-user privileges are required).

1. Login to back-end (administrator view)

2. Go to ''{{rarr|Menus,Main Menu,Add New Item}}''

[[File:Screencapture-Add-Main-Menu-Menu-Item.png]]

3. Set “'''Menu Item Type'''” to ''{{rarr|ConfigurationManager,Display Template Options}}''

[[File:Screencapture-Add-Display-Template-Options-For-Menu-Item.png]]

4. Set '''“Menu Title”''' to '''“Template Settings”'''

5. Finally click '''“Save & Close”'''

6. Now login front front-end as the super-user

7. Click on menu item '''“Template Settings”''' on Main Menu

[[File:Screencapture-FrontEnd-Main-Menu-Template-Settings.png]]

8. You will get Template Settings which is allowed by the current front-end template

[[File:Screencapture-FrontEnd-Template-Settings.png]]

You can do settings and view those changes very quickly. Hope you feel that this is pretty much easier than changing template settings from administrator view.

== For Template Developers ==
This has the flexibility for template developers to specify the parameters which to be shown on the front-end. It is just to adding com_config.xml file with relevant fields to the template folder as shown below.

[[File:Screencapture-Com_Config-XML-For-Templates.png]]

Note: If no such file included in template folder, this component will take all the config fields mentioned in the templateDetails.xml

== Example ==
For this case, Protostar template is used (which is the default template after Joomla! 3.0).

1. Open the folder ''{{rarr|PATH_TO_JOOMLA_DIR,templates,protostar}}''

2. Create a file named '''com_config.xml'''

3. Add the following code

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>

<config>
<fields name="params">
<fieldset name="basics">
<field name="templateColor" class="" type="color" default="#08C"
label="TPL_PROTOSTAR_COLOR_LABEL"
description="TPL_PROTOSTAR_COLOR_DESC" />

<field name="templateBackgroundColor" class="" type="color" default="#F4F6F7"
label="TPL_PROTOSTAR_BACKGROUND_COLOR_LABEL"
description="TPL_PROTOSTAR_BACKGROUND_COLOR_DESC" />

<field name="logoFile" class="" type="media" default=""
label="TPL_PROTOSTAR_LOGO_LABEL"
description="TPL_PROTOSTAR_LOGO_DESC" />

</fieldset>
</fields>
</config>
</source>

4. Above code segment says only to show Template Colour, Background Colour and Logo fields only for the front-end.

5. Thereafter you clicking '''Template Settings''' you will only see the previously mentioned fields are there.

[[File:Screencapture-FrontEnd-Main-Menu-Template-Options-Reduced-Parameters.png]]

Similarly for any template this can be used, but special inspection of the template designer may be required.

== Conclusion ==
From this feature, it is believed that Joomla! super-users will get more efficient way of customizing their web sites and also template developers will use this for their beneficial to serve the clients.

Important: Some templates will not directly support this by adding a com_config.xml. Templates also should support viewing fields added to com_config.xml. Therefore it is highly recommended to consult the template developer for concerns arising when enabling this feature for a particular template.

--[[User:Buddhima|Buddhima]] ([[User talk:Buddhima|talk]]) 04:53, 13 October 2013 (CDT)

Using com config for frontend template style editing

2013-10-15T10:21:23Z

Buddhima:

{{version/tutor|3.2}}
{{RightTOC}}
== Introduction ==
In early versions, it was a bit difficult thing for users to figure out how to change basic settings after installing Joomla! for the first time. To reduce that difficulty front-end component com_config make it possible to do some of those settings through front-end. Through this template view of com_config, super users can easily change current template style parameters and view the changes soon after clicking Save!

== Access to Templates View ==
For beginners, we encourage you to install Joomla! With sample data '''Blog English (GB) Sample Data''' or '''Brochure English (GB) Sample Data'''. If you installed with one of two data sets, you can access it by clicking “Template Settings” on Main Menu (login as super-user will be required).

In other cases you can simply add it to the any menu. Following steps are for adding it to Main menu (super-user privileges are required).

1. Login to back-end (administrator view)

2. Go to '''{{rarr|Menus,Main Menu,Add New Item}}'''

[[File:Screencapture-Add-Main-Menu-Menu-Item.png]]

3. Set “'''Menu Item Type'''” to '''{{rarr|ConfigurationManager,Display Template Options}}'''

[[File:Screencapture-Add-Display-Template-Options-For-Menu-Item.png]]

4. Set '''“Menu Title”''' to '''“Template Settings”'''

5. Finally click '''“Save & Close”'''

6. Now login front front-end as the super-user

7. Click on menu item '''“Template Settings”''' on Main Menu

[[File:Screencapture-FrontEnd-Main-Menu-Template-Settings.png]]

8. You will get Template Settings which is allowed by the current front-end template

[[File:Screencapture-FrontEnd-Template-Settings.png]]

You can do settings and view those changes very quickly. Hope you feel that this is pretty much easier than changing template settings from administrator view.

== For Template Developers ==
This has the flexibility for template developers to specify the parameters which to be shown on the front-end. It is just to adding com_config.xml file with relevant fields to the template folder as shown below.

[[File:Screencapture-Com_Config-XML-For-Templates.png]]

Note: If no such file included in template folder, this component will take all the config fields mentioned in the templateDetails.xml

== Example ==
For this case, Protostar template is used (which is the default template after Joomla! 3.0).

1. Open the folder '''{{rarr|PATH_TO_JOOMLA_DIR,templates,protostar}}'''

2. Create a file named '''com_config.xml'''

3. Add the following code

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>

<config>
<fields name="params">
<fieldset name="basics">
<field name="templateColor" class="" type="color" default="#08C"
label="TPL_PROTOSTAR_COLOR_LABEL"
description="TPL_PROTOSTAR_COLOR_DESC" />

<field name="templateBackgroundColor" class="" type="color" default="#F4F6F7"
label="TPL_PROTOSTAR_BACKGROUND_COLOR_LABEL"
description="TPL_PROTOSTAR_BACKGROUND_COLOR_DESC" />

<field name="logoFile" class="" type="media" default=""
label="TPL_PROTOSTAR_LOGO_LABEL"
description="TPL_PROTOSTAR_LOGO_DESC" />

</fieldset>
</fields>
</config>
</source>

4. Above code segment says only to show Template Colour, Background Colour and Logo fields only for the front-end.

5. Thereafter you clicking '''Template Settings''' you will only see the previously mentioned fields are there.

[[File:Screencapture-FrontEnd-Main-Menu-Template-Options-Reduced-Parameters.png]]

Similarly for any template this can be used, but special inspection of the template designer may be required.

== Conclusion ==
From this feature, it is believed that Joomla! super-users will get more efficient way of customizing their web sites and also template developers will use this for their beneficial to serve the clients.

Important: Some templates will not directly support this by adding a com_config.xml. Templates also should support viewing fields added to com_config.xml. Therefore it is highly recommended to consult the template developer for concerns arising when enabling this feature for a particular template.

--[[User:Buddhima|Buddhima]] ([[User talk:Buddhima|talk]]) 04:53, 13 October 2013 (CDT)

File:Screencapture-FrontEnd-Main-Menu-Template-Settings.png

2013-10-13T15:08:29Z

Buddhima: Buddhima uploaded a new version of "File:Screencapture-FrontEnd-Main-Menu-Template-Settings.png"

Using com config for frontend template style editing

2013-10-13T15:07:11Z

Buddhima: Using com_config frontend template styling, super-users can easily change template styles and experience it easily!

{{version/tutor|3.2}}
{{RightTOC}}
== Introduction ==
In early versions, it was a bit difficult thing for users to figure out how to change basic settings after installing Joomla! for the first time. To reduce that difficulty front-end component com_config make it possible to do some of those settings through front-end. Through this template view of com_config, super users can easily change current template style parameters and view the changes soon after clicking Save!

== Access to Templates View ==
For beginners, we encourage you to install Joomla! With sample data '''Blog English (GB) Sample Data''' or '''Brochure English (GB) Sample Data'''. If you installed with one of two data sets, you can access it by clicking “Template Settings” on Main Menu (login as super-user will be required).

In other cases you can simply add it to the any menu. Following steps are for adding it to Main menu (super-user privileges are required).

1. Login to back-end (administrator view)

2. Go to '''Menus -> Main Menu -> Add New Item'''

[[File:Screencapture-Add-Main-Menu-Menu-Item.png]]

3. Set “'''Menu Item Type'''” to '''ConfigurationManager -> Display Template Options'''

[[File:Screencapture-Add-Display-Template-Options-For-Menu-Item.png]]

4. Set '''“Menu Title”''' to '''“Template Settings”'''

5. Finally click '''“Save & Close”'''

6. Now login front front-end as the super-user

7. Click on menu item '''“Template Settings”''' on Main Menu

[[File:Screencapture-FrontEnd-Main-Menu-Template-Settings.png]]

8. You will get Template Settings which is allowed by the current front-end template

[[File:Screencapture-FrontEnd-Template-Settings.png]]

You can do settings and view those changes very quickly. Hope you feel that this is pretty much easier than changing template settings from administrator view.

== For Template Developers ==
This has the flexibility for template developers to specify the parameters which to be shown on the front-end. It is just to adding com_config.xml file with relevant fields to the template folder as shown below.

[[File:Screencapture-Com_Config-XML-For-Templates.png]]

Note: If no such file included in template folder, this component will take all the config fields mentioned in the templateDetails.xml

== Example ==
For this case, Protostar template is used (which is the default template after Joomla! 3.0).

1. Open the folder '''PATH_TO_JOOMLA_DIR -> templates -> protostar'''

2. Create a file named '''com_config.xml'''

3. Add the following code

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>

<config>
<fields name="params">
<fieldset name="basics">
<field name="templateColor" class="" type="color" default="#08C"
label="TPL_PROTOSTAR_COLOR_LABEL"
description="TPL_PROTOSTAR_COLOR_DESC" />

<field name="templateBackgroundColor" class="" type="color" default="#F4F6F7"
label="TPL_PROTOSTAR_BACKGROUND_COLOR_LABEL"
description="TPL_PROTOSTAR_BACKGROUND_COLOR_DESC" />

<field name="logoFile" class="" type="media" default=""
label="TPL_PROTOSTAR_LOGO_LABEL"
description="TPL_PROTOSTAR_LOGO_DESC" />

</fieldset>
</fields>
</config>
</source>

4. Above code segment says only to show Template Colour, Background Colour and Logo fields only for the front-end.

5. Thereafter you clicking '''Template Settings''' you will only see the previously mentioned fields are there.

[[File:Screencapture-FrontEnd-Main-Menu-Template-Options-Reduced-Parameters.png]]

Similarly for any template this can be used, but special inspection of the template designer may be required.

== Conclusion ==
From this feature, it is believed that Joomla! super-users will get more efficient way of customizing their web sites and also template developers will use this for their beneficial to serve the clients.

Important: Some templates will not directly support this by adding a com_config.xml. Templates also should support viewing fields added to com_config.xml. Therefore it is highly recommended to consult the template developer for concerns arising when enabling this feature for a particular template.

--[[User:Buddhima|Buddhima]] ([[User talk:Buddhima|talk]]) 04:53, 13 October 2013 (CDT)

Using com config for frontend template style editing

2013-10-13T14:57:33Z

Buddhima:

{{version/tutor|3.2}}
{{RightTOC}}
== Introduction ==
In early versions, it was a bit difficult thing for users to figure out how to change basic settings after installing Joomla! for the first time. To reduce that difficulty front-end component com_config make it possible to do some of those settings through front-end. Through this template view of com_config, super users can easily change current template style parameters and view the changes soon after clicking Save!

== Access to Templates View ==
For beginners, we encourage you to install Joomla! With sample data Blog English (GB) Sample Data or Brochure English (GB) Sample Data. If you installed with one of two data sets, you can access it by clicking “Template Settings” on Main Menu (login as super-user will be required).

In other cases you can simply add it to the any menu. Following steps are for adding it to Main menu (super-user privileges are required).

1. Login to back-end (administrator view)

2. Go to Menus -> Main Menu -> Add New Item

[[File:Screencapture-Add-Main-Menu-Menu-Item.png]]

3. Set “Menu Item Type” to ConfigurationManager -> Display Template Options

[[File:Screencapture-Add-Display-Template-Options-For-Menu-Item.png]]

4. Set “Menu Title” to “Template Settings”

5. Finally click “Save & Close”

6. Now login front front-end as the super-user

7. Click on menu item “Template Settings” on Main Menu

[[File:Screencapture-FrontEnd-Main-Menu-Template-Settings.png]]

8. You will get Template Settings which is allowed by the current front-end template

[[File:Screencapture-FrontEnd-Template-Settings.png]]

You can do settings and view those changes very quickly. Hope you feel that this is pretty much easier than changing template settings from administrator view.

== For Template Developers ==
This has the flexibility for template developers to specify the parameters which to be shown on the front-end. It is just to adding com_config.xml file with relevant fields to the template folder as shown below.

[[File:Screencapture-Com_Config-XML-For-Templates.png]]

Note: If no such file included in template folder, this component will take all the config fields mentioned in the templateDetails.xml

== Example ==
For this case, Protostar template is used (which is the default template after Joomla! 3.0).

1. Open the folder PATH_TO_JOOMLA_DIR -> templates -> protostar

2. Create a file named com_config.xml

3. Add the following code

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>

<config>
<fields name="params">
<fieldset name="basics">
<field name="templateColor" class="" type="color" default="#08C"
label="TPL_PROTOSTAR_COLOR_LABEL"
description="TPL_PROTOSTAR_COLOR_DESC" />

<field name="templateBackgroundColor" class="" type="color" default="#F4F6F7"
label="TPL_PROTOSTAR_BACKGROUND_COLOR_LABEL"
description="TPL_PROTOSTAR_BACKGROUND_COLOR_DESC" />

<field name="logoFile" class="" type="media" default=""
label="TPL_PROTOSTAR_LOGO_LABEL"
description="TPL_PROTOSTAR_LOGO_DESC" />

</fieldset>
</fields>
</config>
</source>

4. Above code segment says only to show Template Colour, Background Colour and Logo fields only for the front-end.

5. Thereafter you clicking Template Settings you will only see the previously mentioned fields are there.

[[File:Screencapture-FrontEnd-Main-Menu-Template-Options-Reduced-Parameters.png]]

Similarly for any template this can be used, but special inspection of the template designer may be required.

== Conclusion ==
From this feature, it is believed that Joomla! super-users will get more efficient way of customizing their web sites and also template developers will use this for their beneficial to serve the clients.

Important: Some templates will not directly support this by adding a com_config.xml. Templates also should support viewing fields added to com_config.xml. Therefore it is highly recommended to consult the template developer for concerns arising when enabling this feature for a particular template.

--[[User:Buddhima|Buddhima]] ([[User talk:Buddhima|talk]]) 04:53, 13 October 2013 (CDT)

File:Screencapture-FrontEnd-Main-Menu-Template-Options-Reduced-Parameters.png

2013-10-13T14:57:16Z

Buddhima:

File:Screencapture-Com Config-XML-For-Templates.png

2013-10-13T14:56:19Z

Buddhima:

File:Screencapture-FrontEnd-Template-Settings.png

2013-10-13T14:55:31Z

Buddhima:

File:Screencapture-FrontEnd-Main-Menu-Template-Settings.png

2013-10-13T14:54:30Z

Buddhima:

File:Screencapture-Add-Main-Menu-Menu-Item.png

2013-10-13T14:53:21Z

Buddhima:

Using com config for frontend template style editing

2013-10-13T14:51:19Z

Buddhima:

{{version/tutor|3.2}}
{{RightTOC}}
== Introduction ==
In early versions, it was a bit difficult thing for users to figure out how to change basic settings after installing Joomla! for the first time. To reduce that difficulty front-end component com_config make it possible to do some of those settings through front-end. Through this template view of com_config, super users can easily change current template style parameters and view the changes soon after clicking Save!

== Access to Templates View ==
For beginners, we encourage you to install Joomla! With sample data Blog English (GB) Sample Data or Brochure English (GB) Sample Data. If you installed with one of two data sets, you can access it by clicking “Template Settings” on Main Menu (login as super-user will be required).

In other cases you can simply add it to the any menu. Following steps are for adding it to Main menu (super-user privileges are required).

1. Login to back-end (administrator view)

2. Go to Menus -> Main Menu -> Add New Item

3. Set “Menu Item Type” to ConfigurationManager -> Display Template Options

[[File:Screencapture-Add-Display-Template-Options-For-Menu-Item.png]]

4. Set “Menu Title” to “Template Settings”

5. Finally click “Save & Close”

6. Now login front front-end as the super-user

7. Click on menu item “Template Settings” on Main Menu

8. You will get Template Settings which is allowed by the current front-end template

You can do settings and view those changes very quickly. Hope you feel that this is pretty much easier than changing template settings from administrator view.

== For Template Developers ==
This has the flexibility for template developers to specify the parameters which to be shown on the front-end. It is just to adding com_config.xml file with relevant fields to the template folder as shown below.

Note: If no such file included in template folder, this component will take all the config fields mentioned in the templateDetails.xml

== Example ==
For this case, Protostar template is used (which is the default template after Joomla! 3.0).

1. Open the folder PATH_TO_JOOMLA_DIR -> templates -> protostar

2. Create a file named com_config.xml

3. Add the following code

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>

<config>
<fields name="params">
<fieldset name="basics">
<field name="templateColor" class="" type="color" default="#08C"
label="TPL_PROTOSTAR_COLOR_LABEL"
description="TPL_PROTOSTAR_COLOR_DESC" />

<field name="templateBackgroundColor" class="" type="color" default="#F4F6F7"
label="TPL_PROTOSTAR_BACKGROUND_COLOR_LABEL"
description="TPL_PROTOSTAR_BACKGROUND_COLOR_DESC" />

<field name="logoFile" class="" type="media" default=""
label="TPL_PROTOSTAR_LOGO_LABEL"
description="TPL_PROTOSTAR_LOGO_DESC" />

</fieldset>
</fields>
</config>
</source>

4. Above code segment says only to show Template Colour, Background Colour and Logo fields only for the front-end.

5. Thereafter you clicking Template Settings you will only see the previously mentioned fields are there.

Similarly for any template this can be used, but special inspection of the template designer may be required.

== Conclusion ==
From this feature, it is believed that Joomla! super-users will get more efficient way of customizing their web sites and also template developers will use this for their beneficial to serve the clients.

Important: Some templates will not directly support this by adding a com_config.xml. Templates also should support viewing fields added to com_config.xml. Therefore it is highly recommended to consult the template developer for concerns arising when enabling this feature for a particular template.

--[[User:Buddhima|Buddhima]] ([[User talk:Buddhima|talk]]) 04:53, 13 October 2013 (CDT)

File:Screencapture-Add-Display-Template-Options-For-Menu-Item.png

2013-10-13T14:50:42Z

Buddhima: Buddhima uploaded a new version of "File:Screencapture-Add-Display-Template-Options-For-Menu-Item.png"

File:Screencapture-Add-Display-Template-Options-For-Menu-Item.png

2013-10-13T14:35:33Z

Buddhima:

Using com config for frontend template style editing

2013-10-13T10:52:11Z

Buddhima:

{{version/tutor|3.2}}
{{RightTOC}}
== Introduction ==
In early versions, it was a bit difficult thing for users to figure out how to change basic settings after installing Joomla! for the first time. To reduce that difficulty front-end component com_config make it possible to do some of those settings through front-end. Through this template view of com_config, super users can easily change current template style parameters and view the changes soon after clicking Save!

== Access to Templates View ==
For beginners, we encourage you to install Joomla! With sample data Blog English (GB) Sample Data or Brochure English (GB) Sample Data. If you installed with one of two data sets, you can access it by clicking “Template Settings” on Main Menu (login as super-user will be required).

In other cases you can simply add it to the any menu. Following steps are for adding it to Main menu (super-user privileges are required).

1. Login to back-end (administrator view)

2. Go to Menus -> Main Menu -> Add New Item

3. Set “Menu Item Type” to ConfigurationManager -> Display Template Options

4. Set “Menu Title” to “Template Settings”

5. Finally click “Save & Close”

6. Now login front front-end as the super-user

7. Click on menu item “Template Settings” on Main Menu

8. You will get Template Settings which is allowed by the current front-end template

You can do settings and view those changes very quickly. Hope you feel that this is pretty much easier than changing template settings from administrator view.

== For Template Developers ==
This has the flexibility for template developers to specify the parameters which to be shown on the front-end. It is just to adding com_config.xml file with relevant fields to the template folder as shown below.

Note: If no such file included in template folder, this component will take all the config fields mentioned in the templateDetails.xml

== Example ==
For this case, Protostar template is used (which is the default template after Joomla! 3.0).

1. Open the folder PATH_TO_JOOMLA_DIR -> templates -> protostar

2. Create a file named com_config.xml

3. Add the following code

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>

<config>
<fields name="params">
<fieldset name="basics">
<field name="templateColor" class="" type="color" default="#08C"
label="TPL_PROTOSTAR_COLOR_LABEL"
description="TPL_PROTOSTAR_COLOR_DESC" />

<field name="templateBackgroundColor" class="" type="color" default="#F4F6F7"
label="TPL_PROTOSTAR_BACKGROUND_COLOR_LABEL"
description="TPL_PROTOSTAR_BACKGROUND_COLOR_DESC" />

<field name="logoFile" class="" type="media" default=""
label="TPL_PROTOSTAR_LOGO_LABEL"
description="TPL_PROTOSTAR_LOGO_DESC" />

</fieldset>
</fields>
</config>
</source>

4. Above code segment says only to show Template Colour, Background Colour and Logo fields only for the front-end.

5. Thereafter you clicking Template Settings you will only see the previously mentioned fields are there.

Similarly for any template this can be used, but special inspection of the template designer may be required.

== Conclusion ==
From this feature, it is believed that Joomla! super-users will get more efficient way of customizing their web sites and also template developers will use this for their beneficial to serve the clients.

Important: Some templates will not directly support this by adding a com_config.xml. Templates also should support viewing fields added to com_config.xml. Therefore it is highly recommended to consult the template developer for concerns arising when enabling this feature for a particular template.

--[[User:Buddhima|Buddhima]] ([[User talk:Buddhima|talk]]) 04:53, 13 October 2013 (CDT)

Using com config for frontend template style editing

2013-10-13T10:06:37Z

Buddhima:

{{version/tutor|3.2}}
{{RightTOC}}
== Introduction ==
In early versions, it was a bit difficult thing for users to figure out how to change basic settings after installing Joomla! for the first time. To reduce that difficulty front-end component com_config make it possible to do some of those settings through front-end. Through this template view of com_config, super users can easily change current template style parameters and view the changes soon after clicking Save!

== Access to Templates View ==
For beginners, we encourage you to install Joomla! With sample data Blog English (GB) Sample Data or Brochure English (GB) Sample Data. If you installed with one of two data sets, you can access it by clicking “Template Settings” on Main Menu (login as super-user will be required).

In other cases you can simply add it to the any menu. Following steps are for adding it to Main menu (super-user privileges are required).

1. Login to back-end (administrator view)

2. Go to Menus -> Main Menu -> Add New Item

3. Set “Menu Item Type” to ConfigurationManager -> Display Template Options

4. Set “Menu Title” to “Template Settings”

5. Finally click “Save & Close”

6. Now login front front-end as the super-user

7. Click on menu item “Template Settings” on Main Menu

8. You will get Template Settings which is allowed by the current front-end template

You can do settings and view those changes very quickly. Hope you feel that this is pretty much easier than changing template settings from administrator view.

== For Template Developers ==
This has the flexibility for template developers to specify the parameters which to be shown on the front-end. It is just to adding com_config.xml file with relevant fields to the template folder as shown below.

Note: If no such file included in template folder, this component will take all the config fields mentioned in the templateDetails.xml

== Example ==
For this case, Protostar template is used (which is the default template after Joomla! 3.0).

1. Open the folder PATH_TO_JOOMLA_DIR -> templates -> protostar

2. Create a file named com_config.xml

3. Add the following code

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE install PUBLIC "-//Joomla! 3.2//DTD template 1.0//EN" "http://www.joomla.org/xml/dtd/2.5/template-install.dtd">

<config>
<fields name="params">
<fieldset name="basics">
<field name="templateColor" class="" type="color" default="#08C"
label="TPL_PROTOSTAR_COLOR_LABEL"
description="TPL_PROTOSTAR_COLOR_DESC" />

<field name="templateBackgroundColor" class="" type="color" default="#F4F6F7"
label="TPL_PROTOSTAR_BACKGROUND_COLOR_LABEL"
description="TPL_PROTOSTAR_BACKGROUND_COLOR_DESC" />

<field name="logoFile" class="" type="media" default=""
label="TPL_PROTOSTAR_LOGO_LABEL"
description="TPL_PROTOSTAR_LOGO_DESC" />

</fieldset>
</fields>
</config>
</source>

4. Above code segment says only to show Template Colour, Background Colour and Logo fields only for the front-end.

5. Thereafter you clicking Template Settings you will only see the previously mentioned fields are there.

Similarly for any template this can be used, but special inspection of the template designer may be required.

== Conclusion ==
From this feature, it is believed that Joomla! super-users will get more efficient way of customizing their web sites and also template developers will use this for their beneficial to serve the clients.

Important: Some templates will not directly support this by adding a com_config.xml. Templates also should support viewing fields added to com_config.xml. Therefore it is highly recommended to consult the template developer for concerns arising when enabling this feature for a particular template.

--[[User:Buddhima|Buddhima]] ([[User talk:Buddhima|talk]]) 04:53, 13 October 2013 (CDT)

Using com config for frontend template style editing

2013-10-13T09:54:32Z

Buddhima:

{{version/tutor|3.2}}
{{RightTOC}}
== Introduction ==
In early versions, it was a bit difficult thing for users to figure out how to change basic settings after installing Joomla! for the first time. To reduce that difficulty front-end component com_config make it possible to do some of those settings through front-end. Through this template view of com_config, super users can easily change current template style parameters and view the changes soon after clicking Save!

== Access to Templates View ==
For beginners, we encourage you to install Joomla! With sample data Blog English (GB) Sample Data or Brochure English (GB) Sample Data. If you installed with one of two data sets, you can access it by clicking “Template Settings” on Main Menu (login as super-user will be required).

In other cases you can simply add it to the any menu. Following steps are for adding it to Main menu (super-user privileges are required).

1. Login to back-end (administrator view)

2. Go to Menus -> Main Menu -> Add New Item

3. Set “Menu Item Type” to ConfigurationManager -> Display Template Options

4. Set “Menu Title” to “Template Settings”

5. Finally click “Save & Close”

6. Now login front front-end as the super-user

7. Click on menu item “Template Settings” on Main Menu

8. You will get Template Settings which is allowed by the current front-end template

You can do settings and view those changes very quickly. Hope you feel that this is pretty much easier than changing template settings from administrator view.

== For Template Developers ==
This has the flexibility for template developers to specify the parameters which to be shown on the front-end. It is just to adding com_config.xml file with relevant fields to the template folder as shown below.

Note: If no such file included in template folder, this component will take all the config fields mentioned in the templateDetails.xml

== Example ==
For this case, Protostar template is used (which is the default template after Joomla! 3.0).

1. Open the folder PATH_TO_JOOMLA_DIR -> templates -> protostar

2. Create a file named com_config.xml

3. Add the following code

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE install PUBLIC "-//Joomla! 2.5//DTD template 1.0//EN" "http://www.joomla.org/xml/dtd/2.5/template-install.dtd">

<config>
<fields name="params">
<fieldset name="basics">
<field name="templateColor" class="" type="color" default="#08C"
label="TPL_PROTOSTAR_COLOR_LABEL"
description="TPL_PROTOSTAR_COLOR_DESC" />

<field name="templateBackgroundColor" class="" type="color" default="#F4F6F7"
label="TPL_PROTOSTAR_BACKGROUND_COLOR_LABEL"
description="TPL_PROTOSTAR_BACKGROUND_COLOR_DESC" />

<field name="logoFile" class="" type="media" default=""
label="TPL_PROTOSTAR_LOGO_LABEL"
description="TPL_PROTOSTAR_LOGO_DESC" />

</fieldset>
</fields>
</config>
</source>

4. Above code segment says only to show Template Colour, Background Colour and Logo fields only for the front-end.

5. Thereafter you clicking Template Settings you will only see the previously mentioned fields are there.

Similarly for any template this can be used, but special inspection of the template designer may be required.

== Conclusion ==
From this feature, it is believed that Joomla! super-users will get more efficient way of customizing their web sites and also template developers will use this for their beneficial to serve the clients.

Important: Some templates will not directly support this by adding a com_config.xml. Templates also should support viewing fields added to com_config.xml. Therefore it is highly recommended to consult the template developer for concerns arising when enabling this feature for a particular template.

--[[User:Buddhima|Buddhima]] ([[User talk:Buddhima|talk]]) 04:53, 13 October 2013 (CDT)

Using com config for frontend template style editing

2013-10-13T09:53:31Z

Buddhima:

{{version/tutor|3.2}}
{{RightTOC}}
== Introduction ==
In early versions, it was a bit difficult thing for users to figure out how to change basic settings after installing Joomla! for the first time. To reduce that difficulty front-end component com_config make it possible to do some of those settings through front-end. Through this template view of com_config, super users can easily change current template style parameters and view the changes soon after clicking Save!

== Access to Templates View ==
For beginners, we encourage you to install Joomla! With sample data Blog English (GB) Sample Data or Brochure English (GB) Sample Data. If you installed with one of two data sets, you can access it by clicking “Template Settings” on Main Menu (login as super-user will be required).

In other cases you can simply add it to the any menu. Following steps are for adding it to Main menu (super-user privileges are required).

1. Login to back-end (administrator view)

2. Go to Menus -> Main Menu -> Add New Item

3. Set “Menu Item Type” to ConfigurationManager -> Display Template Options

4. Set “Menu Title” to “Template Settings”

5. Finally click “Save & Close”

6. Now login front front-end as the super-user

7. Click on menu item “Template Settings” on Main Menu

8. You will get Template Settings which is allowed by the current front-end template

You can do settings and view those changes very quickly. Hope you feel that this is pretty much easier than changing template settings from administrator view.

== For Template Developers ==
This has the flexibility for template developers to specify the parameters which to be shown on the front-end. It is just to adding com_config.xml file with relevant fields to the template folder as shown below.

Note: If no such file included in template folder, this component will take all the config fields mentioned in the templateDetails.xml

== Example ==
For this case, Protostar template is used (which is the default template after Joomla! 3.0).

1. Open the folder PATH_TO_JOOMLA_DIR -> templates -> protostar

2. Create a file named com_config.xml

3. Add the following code

4. Above code segment says only to show Template Colour, Background Colour and Logo fields only for the front-end.

5. Thereafter you clicking Template Settings you will only see the previously mentioned fields are there.

Similarly for any template this can be used, but special inspection of the template designer may be required.

== Conclusion ==
From this feature, it is believed that Joomla! super-users will get more efficient way of customizing their web sites and also template developers will use this for their beneficial to serve the clients.

Important: Some templates will not directly support this by adding a com_config.xml. Templates also should support viewing fields added to com_config.xml. Therefore it is highly recommended to consult the template developer for concerns arising when enabling this feature for a particular template.

--[[User:Buddhima|Buddhima]] ([[User talk:Buddhima|talk]]) 04:53, 13 October 2013 (CDT)

Using com config for frontend template style editing

2013-10-13T09:52:34Z

Buddhima: