KDE.org/New Site: Difference between revisions
< KDE.org
Created page with "== We need to get things done. == There were discussions about what to use. At the end, 3 solutions where retained: * custom CMS ** pro: does exactly what we need ** con: not..." |
|||
| Line 20: | Line 20: | ||
=== Step 2 === | === Step 2 === | ||
* Get a test host by the sysadmin | * Get a test host by the sysadmin [in progress] | ||
* build the solution and test things | |||
* Create palette and style | * Create palette and style | ||
Revision as of 16:06, 30 August 2016
We need to get things done.
There were discussions about what to use. At the end, 3 solutions where retained:
- custom CMS
- pro: does exactly what we need
- con: not enough manpower, need to maintain in the future
- wordpress
- pro: very easy to deal with, should be easy to maintain (updates)
- con: maybe not flexible enough, might need to create/edit plugins
- drupal
- pro: easy to maintain (updates) and for users to edit
- con: more complex than wordpress
Steps
Might need to be reorganized...
Step 1
Choose solution. Solution: ......
Step 2
- Get a test host by the sysadmin [in progress]
- build the solution and test things
- Create palette and style
Step 3
- Create neverland-based theme.
Step N
- replace current kde.org
Specifications
Type of content
- Pages
- normal pages with text/picture content
- Difficulty: easy
- Applications
- Grid with applications, on click, show details
- Idea: use e-commerce plugin and remove prices (can we subclass a plugin?)
- Blogs, tweets and other feeds
- Feeds plugin,
Theme
The theme must be usable (in term of style and colors) by all the KDE websites and represent its identity.
Other features
- Access
- Need a ldap/phabricator connection
- Need to know who is allowed to do what