Difference between revisions of "Summer of Code 2008 Project Ideas"
From Joomla! Documentation
(New page: This page contains a list of project proposal ideas from the Joomla! project (community members). The mentoring organization has written down a non exhaustive list of project ideas to guid...) |
|||
| Line 5: | Line 5: | ||
We would kindly ask you not to add new projects her unless you are one of the project mentors, please discuss these on the list/forum mentioned above. | We would kindly ask you not to add new projects her unless you are one of the project mentors, please discuss these on the list/forum mentioned above. | ||
| − | |||
| − | + | == Unit Tests == | |
| − | |||
| − | + | == Article Versioning] == | |
| − | + | == Whiteboard component == | |
| + | |||
| + | == Multi-site implemententation == | ||
| + | Ability to use one install base for multiple sites.]] | ||
| + | |||
| + | == Image Manager improvements == | ||
Thumbnails and image resizing, watermarking, caching, batch uploading, flood protection, enhanced security checking on file contents, per user galleries | Thumbnails and image resizing, watermarking, caching, batch uploading, flood protection, enhanced security checking on file contents, per user galleries | ||
| − | + | == Searching Improvements == | |
Aadvanced search capabilities including specific content types including third party extensions, section and category, weighted searches, Ajax support, multiple tabbed results sorted differently include most recent, relevance, external API's like Google and Yahoo | Aadvanced search capabilities including specific content types including third party extensions, section and category, weighted searches, Ajax support, multiple tabbed results sorted differently include most recent, relevance, external API's like Google and Yahoo | ||
| − | + | == Multi-lingual support == | |
Create environment where articles can be translated and stored using same menu structure, configured SEF URLs to have translated PLUGs and language in URL | Create environment where articles can be translated and stored using same menu structure, configured SEF URLs to have translated PLUGs and language in URL | ||
| − | + | == SEF URL Plugins == | |
Various options like category/article-name.html, blog/CCYY-MM-DD/Article, etc. | Various options like category/article-name.html, blog/CCYY-MM-DD/Article, etc. | ||
| − | + | == MultiDB support == | |
Create database abstraction layer and support for MySQL and PostGres | Create database abstraction layer and support for MySQL and PostGres | ||
| − | + | == Forms == | |
Create component that makes it easy for end users to create forms, consider Ajax support | Create component that makes it easy for end users to create forms, consider Ajax support | ||
| − | + | == Export and Import Tools == | |
Create tools that make it easier for end users to migrate content into and out of Joomla! | Create tools that make it easier for end users to migrate content into and out of Joomla! | ||
| − | + | == Comments == | |
Threaded and not threaded, support for various content-types, not just articles | Threaded and not threaded, support for various content-types, not just articles | ||
| − | + | == Tags == | |
Tagging for various content-types | Tagging for various content-types | ||
| − | + | == TinyMCE == | |
Create a plugin for TinyMCE that makes it easy for end users to choose which add-ons they want without hacking the core | Create a plugin for TinyMCE that makes it easy for end users to choose which add-ons they want without hacking the core | ||
| − | + | == Mootools == | |
Create an PHP API for using mootools. | Create an PHP API for using mootools. | ||
| − | + | == Error Page Handling == | |
Create a component that will handle standard errors (ex. 404) so that headers are sent for the error code, but the error is trapped and redirected from the error.php file back to Joomla! where it can be handled on a normal webpage. | Create a component that will handle standard errors (ex. 404) so that headers are sent for the error code, but the error is trapped and redirected from the error.php file back to Joomla! where it can be handled on a normal webpage. | ||
| − | + | == Data Portability == | |
Implement recommendations for Site Developers for Data Portability http://groups.google.com/group/dataport ... developers including creating an OAuth plugin that can be used with data services http://oauth.net/core/1.0 | Implement recommendations for Site Developers for Data Portability http://groups.google.com/group/dataport ... developers including creating an OAuth plugin that can be used with data services http://oauth.net/core/1.0 | ||
| − | + | == Semantic Web == | |
Deploy Triplify for Joomla! v 1.5, mapping to existing vocabularies and exposing publicly available content http://triplify.org/ and also deploy xmlgrddl, http://code.google.com/p/xmlgrddl/ producing RDF from the xHTML content. Compare and contrast methods; evaluate which method is better or if there are situations where one is better than the other. Create extension for use by community with instructions for both. | Deploy Triplify for Joomla! v 1.5, mapping to existing vocabularies and exposing publicly available content http://triplify.org/ and also deploy xmlgrddl, http://code.google.com/p/xmlgrddl/ producing RDF from the xHTML content. Compare and contrast methods; evaluate which method is better or if there are situations where one is better than the other. Create extension for use by community with instructions for both. | ||
Semantic Web - Create RDF output for standard Joomla! website using various vocabularies http://www.w3.org/TR/rdf-primer/ ; create a set of template overrides that can be used by community to produce the semantic output | Semantic Web - Create RDF output for standard Joomla! website using various vocabularies http://www.w3.org/TR/rdf-primer/ ; create a set of template overrides that can be used by community to produce the semantic output | ||
| − | + | == Facebook Integration == | |
| − | + | == Open Social Integration == | |
Revision as of 12:01, 18 March 2008
This page has been archived. This page contains information for an unsupported Joomla! version or is no longer relevant. It exists only as a historical reference, it will not be improved and its content may be incomplete and/or contain broken links.
This page contains a list of project proposal ideas from the Joomla! project (community members). The mentoring organization has written down a non exhaustive list of project ideas to guide the students into selecting a proper idea.
This list will be updated on a regular base, feel free to drop any other idea into into the Google Summer of Code 2008 Forum Area or use the Google Summer of Code mail list (don't forget to register to the forum and list before you can post).
We would kindly ask you not to add new projects her unless you are one of the project mentors, please discuss these on the list/forum mentioned above.
Unit Tests[edit]
Article Versioning][edit]
Whiteboard component[edit]
Multi-site implemententation[edit]
Ability to use one install base for multiple sites.]]
Image Manager improvements[edit]
Thumbnails and image resizing, watermarking, caching, batch uploading, flood protection, enhanced security checking on file contents, per user galleries
Searching Improvements[edit]
Aadvanced search capabilities including specific content types including third party extensions, section and category, weighted searches, Ajax support, multiple tabbed results sorted differently include most recent, relevance, external API's like Google and Yahoo
Multi-lingual support[edit]
Create environment where articles can be translated and stored using same menu structure, configured SEF URLs to have translated PLUGs and language in URL
SEF URL Plugins[edit]
Various options like category/article-name.html, blog/CCYY-MM-DD/Article, etc.
MultiDB support[edit]
Create database abstraction layer and support for MySQL and PostGres
Forms[edit]
Create component that makes it easy for end users to create forms, consider Ajax support
Export and Import Tools[edit]
Create tools that make it easier for end users to migrate content into and out of Joomla!
Comments[edit]
Threaded and not threaded, support for various content-types, not just articles
Tags[edit]
Tagging for various content-types
TinyMCE[edit]
Create a plugin for TinyMCE that makes it easy for end users to choose which add-ons they want without hacking the core
Mootools[edit]
Create an PHP API for using mootools.
Error Page Handling[edit]
Create a component that will handle standard errors (ex. 404) so that headers are sent for the error code, but the error is trapped and redirected from the error.php file back to Joomla! where it can be handled on a normal webpage.
Data Portability[edit]
Implement recommendations for Site Developers for Data Portability http://groups.google.com/group/dataport ... developers including creating an OAuth plugin that can be used with data services http://oauth.net/core/1.0
Semantic Web[edit]
Deploy Triplify for Joomla! v 1.5, mapping to existing vocabularies and exposing publicly available content http://triplify.org/ and also deploy xmlgrddl, http://code.google.com/p/xmlgrddl/ producing RDF from the xHTML content. Compare and contrast methods; evaluate which method is better or if there are situations where one is better than the other. Create extension for use by community with instructions for both.
Semantic Web - Create RDF output for standard Joomla! website using various vocabularies http://www.w3.org/TR/rdf-primer/ ; create a set of template overrides that can be used by community to produce the semantic output