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|
We (Lydia, Olivier and Ken) decided to go with Drupal. The choice is supported by (some) other members. The website is on https://www-devel.kde.org
We want to release something as early as possible, even if not finished.
What is mandatory: Announcements + Theme + Plain pages (what is KDE...)
The Applications things can be worked on later, after release.
The theme will be based on the current neon.kde.org. It looks modern and has good feedback.
If Ingo and Minh could begin to see how to port the neon theme to Neverland? + Ken should start a repo with his work on the theme.
The theme must be usable (in term of style and colors) by all the KDE websites and represent its identity.