KDE.org/New Site
< KDE.org
We need to get things done.
There were discussions about what to use. At the end, 3 solutions where retained:
| Type | Getting things done | Maintainability | Custom themes | Localization |
|---|---|---|---|---|
| Wordpress | Very fast for basic stuff, more difficult for specific needs | Very good if we don't need to develop new plugins | Not sure if possible to have several presentations of posts | Seems to be possible with extra plugins (POT?) |
| Drupal | A little more difficult for basic stuff but constant learning curve | Very good if we don't need to develop new plugins, a lot can be done through web interface, configuration can be exported/imported as xml | A theme should be written from scratch / expended. Almost everything possible | Feature present in core. POT files should be exportable with plugins |
| Custom solution | Very specific, unexpected issues can appear because of corner cases | With a good framework (Django, Sf2, Laravel), there are coding rules so it should not go everywhere but still need to maintain that. What about in 5 years? | Everything possible, should be written. | Whatever we want |
Conclusion:
- Wordpress seems too simplistic for what we need.
- Drupal will need a custom theme and certainly some extra modules (specially for the applications page + announcements) but the tests are very promising.
- I (ochurlaud) am afraid that we create a monster like Capacity again and that it's not maintainable on the long run. Also it means that we need to maintain it for security holes etc...
We (Lydia, Olivier and Ken) decided to go with Drupal. The choice is supported by (some) other members.
Steps
Might need to be reorganized...
Step 1
Choose solution. Solution: Drupal
Step 2
- Get a test host by the sysadmin www2-devel.kde.org
- build the solution and test things [doing]
- Create palette and style [doing]
Step 3
- Create neverland-based theme. [later?]
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