Wiki : GoogleSOC
Documentation Home :: Categories :: Index :: Recent Changes :: Comments :: Search :: Help :: Login/Register
Most recent edit on 2008-03-29 11:21:53 by Guite referenced pdf specifications
Additions:
PDF Specification∞
PDF Specification∞
PDF Specification∞
PDF Specification∞
PDF Specification∞
PDF Specification∞
More about the Usability Project
Deletions:
More about the Usability Project
Edited on 2008-03-20 11:58:28 by Guite
Additions:
As the internet evolves new clients are appearing continuously. Separating form and function becomes more important than ever - also in the static content parts a website may produce. PostNuke should become able to serve appropriate content without having to adapt templates for each type of user agent. Therefore this projects is about creating a new approach of storing and managing information. An editor should only define the structural/semantical information of his article which is being stored in XML for example. In addition a few "channels" are selected (which can be web, mobile, office aso) defining how the final rendering will happen and look like. One possibillity for the technical realisation is XSL processing converting XML content to other file types as XHTML, PDF or XLS. XSL is very interesting and powerful, because for example it allows a clean and reliable PDF generation.
Deletions:
As the internet evolves new clients are appearing continuously. Separating form and function becomes more important than ever - also in the static content parts a website may produce. PostNuke should become able to serve appropriate content without having to adapt templates for each type of user agent. Therefore this projects is about creating a new approach of storing and managing information. An editor should only define the structural/semantical information of his article which is being stored in XML for example. In addition a few "channels" are selected (which can be web, mobile, office aso) defining how the final rendering will happen and look like. One possibillity for the technical realisation is XSL-FO processing converting XML content to other file types as XHTML, PDF or XLS. XSL is very interesting and powerful, because for example it allows a clean and reliable PDF generation.
Edited on 2008-03-18 00:39:53 by kaffeeringe.de
Additions:
Required experience: xHTML, CSS, PHP, Usability, Accessability
Deletions:
Required experience: xHTML, CSS, Usability, Accessability
Edited on 2008-03-18 00:21:53 by kaffeeringe.de
Additions:
Postnuke was one of the earliest adopters of webstandards. It is one of the first webapplication frameworks to remove all layout tables and support correct tagging of abbreviations aso. With the new .8 core much of these ideas have consolidated. But indeed there is much to be done in support of user interaction.
This project could include a complete evaluation of the core and some central modules, the creation of UI guidelines and the implementation of examples: templates, css classes, icons and whatever helps developers to have a consistent and easy to use user interface.
More about the Usability Project
Deletions:
Postnuke was one of the earliest adopters of webstandards. One of the first webapplication frameworks to remove all layout tables and support correct tagging of abbreviations aso. With the new .8 core much of these ideas have consolidated. But indeed there is much to be done in support of user interaction.
This project could include a complete evaluation of the core and some central modules, the creation of UI guidelines and the implementation of examples: templates, css classes, icons and whatever helps developers to have a consistent and easy to use user interface.
Edited on 2008-03-18 00:10:54 by kaffeeringe.de Added: Usability & Accessability Overhaul
Additions:
As the internet evolves new clients are appearing continuously. Separating form and function becomes more important than ever - also in the static content parts a website may produce. PostNuke should become able to serve appropriate content without having to adapt templates for each type of user agent. Therefore this projects is about creating a new approach of storing and managing information. An editor should only define the structural/semantical information of his article which is being stored in XML for example. In addition a few "channels" are selected (which can be web, mobile, office aso) defining how the final rendering will happen and look like. One possibillity for the technical realisation is XSL-FO processing converting XML content to other file types as XHTML, PDF or XLS. XSL is very interesting and powerful, because for example it allows a clean and reliable PDF generation.
Usability is one of the future hot topics. Now that we have a wide range of applications that do almost everything we can imagine it is the next task of software development to make the programmes do what we want them to do as easy as possible. There are organisations working on specifications and standards like the WAI∞ or openusability.org∞.
Postnuke was one of the earliest adopters of webstandards. One of the first webapplication frameworks to remove all layout tables and support correct tagging of abbreviations aso. With the new .8 core much of these ideas have consolidated. But indeed there is much to be done in support of user interaction.
This project could include a complete evaluation of the core and some central modules, the creation of UI guidelines and the implementation of examples: templates, css classes, icons and whatever helps developers to have a consistent and easy to use user interface.
Deletions:
As the internet evolves new clients are appearing continuously. Separating form and function becomes more important than ever - also in the static content parts a website may produce. PostNuke should become able to serve appropriate content without having to adapt templates for each type of user agent. Therefore this projects is about creating a new approach of storing and managing information. A writer should only define the structural/semantical information of his article which is being stored in XML for example. In addition a few "channels" are selected (which can be web, mobile, office aso) defining how the final rendering will happen and look like. One possibillity for the technical realisation is XSL-FO processing converting XML content to other file types as XHTML, PDF or XLS. XSL is very interesting and powerful, because for example it allows a clean and reliable PDF generation.
Edited on 2008-03-07 12:44:25 by HammerHead
Additions:
The PostNuke Team has identified a number of areas in which we think we can benefit from the Google Summer of Code programme. These are fairly large projects, all of which will contribute immensely to the PostNuke feature set and our aims of providing a solid Application Framework on which third party developers can build. This page is under development, and following acceptance into the GSoC? programme full specifications for each project will be published. In the meantime, the projects we have identified are:
Deletions:
The PostNuke Team has identified a number of areas in which we think we can benefit from the Google Summer of Code programme. These are fairly large projects, all of which will contribute immensely to the PostNuke feature set and our aims of providing a solid Application Framework on which third party developers can build. This page is under development, and following acceptance into the GSoC? programme full specifications for each project will be published. In the meantime, the projects we have identified are:
Edited on 2008-03-04 12:25:29 by HammerHead Update opening paragraph
Additions:
The PostNuke Team has identified a number of areas in which we think we can benefit from the Google Summer of Code programme. These are fairly large projects, all of which will contribute immensely to the PostNuke feature set and our aims of providing a solid Application Framework on which third party developers can build. This page is under development, and following acceptance into the GSoC? programme full specifications for each project will be published. In the meantime, the projects we have identified are:
Deletions:
The PostNuke Team has identified a number of areas in which we think we can benefit from the Google Summer of Code programme. These are fairly large projects, all of which will contribute immensely to the PostNuke feature set and our aims of providing a solid Application Framework on which third party developers can build. To this end, the projects we have identified are:
Edited on 2008-03-04 11:58:37 by Guite Added two ideas and extended general content structure
Additions:
Difficulty: medium
Required experience: PHP, MySQL
Difficulty: easy
Required experience: PHP, MySQL, Language structure
Difficulty: medium
Required experience: PHP
The current categories system uses path based categories resolution, useful for keeping semantic reasoning but not the most efficient solution. This project would involve changing the categories system to use a nested set algorithm, updating the code base as necessary. An additional requirement would be an improvement of the current categories administration interface, which currently has usability issues and could be improved with an Ajax interface (with proper fallback).
Required experience: PHP, MySQL
In order to be able to extend the search module's abilities this project aims on developing a powerful search engine. It should be possible to perform unsharp searches finding also terms being similar to the search term. Another important feature is supporting semantic queries. An easy example is finding all content of a particular person. This can be enhanced for several directions, e.g. groups, relations, and so on. The third important function is indexing office and pdf documents for providing extended search capabilities.
Required experience: PHP, XML, XSL
As the internet evolves new clients are appearing continuously. Separating form and function becomes more important than ever - also in the static content parts a website may produce. PostNuke should become able to serve appropriate content without having to adapt templates for each type of user agent. Therefore this projects is about creating a new approach of storing and managing information. A writer should only define the structural/semantical information of his article which is being stored in XML for example. In addition a few "channels" are selected (which can be web, mobile, office aso) defining how the final rendering will happen and look like. One possibillity for the technical realisation is XSL-FO processing converting XML content to other file types as XHTML, PDF or XLS. XSL is very interesting and powerful, because for example it allows a clean and reliable PDF generation.
Deletions:
The current categories system uses path based categories resolution, useful for keeping semantic reasoning but not the most efficient solution. This project would involve changing the categories system to use a nested set algorithm, updating the code base as necessary. An additional requirement would be an improvement of the current categories administration interface, which currently has usability issues and could be improved with an Ajax interface (with proper fallback).
Oldest known version of this page was edited on 2007-03-06 13:02:19 by HammerHead [ ]
Additions:
PDF Specification∞
PDF Specification∞
PDF Specification∞
PDF Specification∞
PDF Specification∞
PDF Specification∞
More about the Usability Project
Deletions:
More about the Usability Project
Edited on 2008-03-20 11:58:28 by Guite
Additions:
As the internet evolves new clients are appearing continuously. Separating form and function becomes more important than ever - also in the static content parts a website may produce. PostNuke should become able to serve appropriate content without having to adapt templates for each type of user agent. Therefore this projects is about creating a new approach of storing and managing information. An editor should only define the structural/semantical information of his article which is being stored in XML for example. In addition a few "channels" are selected (which can be web, mobile, office aso) defining how the final rendering will happen and look like. One possibillity for the technical realisation is XSL processing converting XML content to other file types as XHTML, PDF or XLS. XSL is very interesting and powerful, because for example it allows a clean and reliable PDF generation.
Deletions:
As the internet evolves new clients are appearing continuously. Separating form and function becomes more important than ever - also in the static content parts a website may produce. PostNuke should become able to serve appropriate content without having to adapt templates for each type of user agent. Therefore this projects is about creating a new approach of storing and managing information. An editor should only define the structural/semantical information of his article which is being stored in XML for example. In addition a few "channels" are selected (which can be web, mobile, office aso) defining how the final rendering will happen and look like. One possibillity for the technical realisation is XSL-FO processing converting XML content to other file types as XHTML, PDF or XLS. XSL is very interesting and powerful, because for example it allows a clean and reliable PDF generation.
Edited on 2008-03-18 00:39:53 by kaffeeringe.de
Additions:
Required experience: xHTML, CSS, PHP, Usability, Accessability
Deletions:
Required experience: xHTML, CSS, Usability, Accessability
Edited on 2008-03-18 00:21:53 by kaffeeringe.de
Additions:
Postnuke was one of the earliest adopters of webstandards. It is one of the first webapplication frameworks to remove all layout tables and support correct tagging of abbreviations aso. With the new .8 core much of these ideas have consolidated. But indeed there is much to be done in support of user interaction.
This project could include a complete evaluation of the core and some central modules, the creation of UI guidelines and the implementation of examples: templates, css classes, icons and whatever helps developers to have a consistent and easy to use user interface.
More about the Usability Project
Deletions:
Postnuke was one of the earliest adopters of webstandards. One of the first webapplication frameworks to remove all layout tables and support correct tagging of abbreviations aso. With the new .8 core much of these ideas have consolidated. But indeed there is much to be done in support of user interaction.
This project could include a complete evaluation of the core and some central modules, the creation of UI guidelines and the implementation of examples: templates, css classes, icons and whatever helps developers to have a consistent and easy to use user interface.
Edited on 2008-03-18 00:10:54 by kaffeeringe.de Added: Usability & Accessability Overhaul
Additions:
As the internet evolves new clients are appearing continuously. Separating form and function becomes more important than ever - also in the static content parts a website may produce. PostNuke should become able to serve appropriate content without having to adapt templates for each type of user agent. Therefore this projects is about creating a new approach of storing and managing information. An editor should only define the structural/semantical information of his article which is being stored in XML for example. In addition a few "channels" are selected (which can be web, mobile, office aso) defining how the final rendering will happen and look like. One possibillity for the technical realisation is XSL-FO processing converting XML content to other file types as XHTML, PDF or XLS. XSL is very interesting and powerful, because for example it allows a clean and reliable PDF generation.
Usability & Accessability Overhaul
Required experience: xHTML, CSS, Usability, AccessabilityUsability is one of the future hot topics. Now that we have a wide range of applications that do almost everything we can imagine it is the next task of software development to make the programmes do what we want them to do as easy as possible. There are organisations working on specifications and standards like the WAI∞ or openusability.org∞.
Postnuke was one of the earliest adopters of webstandards. One of the first webapplication frameworks to remove all layout tables and support correct tagging of abbreviations aso. With the new .8 core much of these ideas have consolidated. But indeed there is much to be done in support of user interaction.
This project could include a complete evaluation of the core and some central modules, the creation of UI guidelines and the implementation of examples: templates, css classes, icons and whatever helps developers to have a consistent and easy to use user interface.
Deletions:
As the internet evolves new clients are appearing continuously. Separating form and function becomes more important than ever - also in the static content parts a website may produce. PostNuke should become able to serve appropriate content without having to adapt templates for each type of user agent. Therefore this projects is about creating a new approach of storing and managing information. A writer should only define the structural/semantical information of his article which is being stored in XML for example. In addition a few "channels" are selected (which can be web, mobile, office aso) defining how the final rendering will happen and look like. One possibillity for the technical realisation is XSL-FO processing converting XML content to other file types as XHTML, PDF or XLS. XSL is very interesting and powerful, because for example it allows a clean and reliable PDF generation.
Edited on 2008-03-07 12:44:25 by HammerHead
Additions:
The PostNuke Team has identified a number of areas in which we think we can benefit from the Google Summer of Code programme. These are fairly large projects, all of which will contribute immensely to the PostNuke feature set and our aims of providing a solid Application Framework on which third party developers can build. This page is under development, and following acceptance into the GSoC? programme full specifications for each project will be published. In the meantime, the projects we have identified are:
Deletions:
The PostNuke Team has identified a number of areas in which we think we can benefit from the Google Summer of Code programme. These are fairly large projects, all of which will contribute immensely to the PostNuke feature set and our aims of providing a solid Application Framework on which third party developers can build. This page is under development, and following acceptance into the GSoC? programme full specifications for each project will be published. In the meantime, the projects we have identified are:
Edited on 2008-03-04 12:25:29 by HammerHead Update opening paragraph
Additions:
The PostNuke Team has identified a number of areas in which we think we can benefit from the Google Summer of Code programme. These are fairly large projects, all of which will contribute immensely to the PostNuke feature set and our aims of providing a solid Application Framework on which third party developers can build. This page is under development, and following acceptance into the GSoC? programme full specifications for each project will be published. In the meantime, the projects we have identified are:
Deletions:
The PostNuke Team has identified a number of areas in which we think we can benefit from the Google Summer of Code programme. These are fairly large projects, all of which will contribute immensely to the PostNuke feature set and our aims of providing a solid Application Framework on which third party developers can build. To this end, the projects we have identified are:
Edited on 2008-03-04 11:58:37 by Guite Added two ideas and extended general content structure
Additions:
Difficulty: medium
Required experience: PHP, MySQL
Difficulty: easy
Required experience: PHP, MySQL, Language structure
Difficulty: medium
Required experience: PHP
The current categories system uses path based categories resolution, useful for keeping semantic reasoning but not the most efficient solution. This project would involve changing the categories system to use a nested set algorithm, updating the code base as necessary. An additional requirement would be an improvement of the current categories administration interface, which currently has usability issues and could be improved with an Ajax interface (with proper fallback).
Improved search engine capabilities
Difficulty: hardRequired experience: PHP, MySQL
In order to be able to extend the search module's abilities this project aims on developing a powerful search engine. It should be possible to perform unsharp searches finding also terms being similar to the search term. Another important feature is supporting semantic queries. An easy example is finding all content of a particular person. This can be enhanced for several directions, e.g. groups, relations, and so on. The third important function is indexing office and pdf documents for providing extended search capabilities.
Semantic-Driven Content Management
Difficulty: hardRequired experience: PHP, XML, XSL
As the internet evolves new clients are appearing continuously. Separating form and function becomes more important than ever - also in the static content parts a website may produce. PostNuke should become able to serve appropriate content without having to adapt templates for each type of user agent. Therefore this projects is about creating a new approach of storing and managing information. A writer should only define the structural/semantical information of his article which is being stored in XML for example. In addition a few "channels" are selected (which can be web, mobile, office aso) defining how the final rendering will happen and look like. One possibillity for the technical realisation is XSL-FO processing converting XML content to other file types as XHTML, PDF or XLS. XSL is very interesting and powerful, because for example it allows a clean and reliable PDF generation.
Deletions:
The current categories system uses path based categories resolution, useful for keeping semantic reasoning but not the most efficient solution. This project would involve changing the categories system to use a nested set algorithm, updating the code base as necessary. An additional requirement would be an improvement of the current categories administration interface, which currently has usability issues and could be improved with an Ajax interface (with proper fallback).
Oldest known version of this page was edited on 2007-03-06 13:02:19 by HammerHead [ ]
|
Last Editor :
Owner :