KDE.org/New Site: Difference between revisions

Latest revision as of 02:57, 14 November 2017

Comparison

A very nice table that I'm very proud of having done by myself, because, hey it looks nice!

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. The website is on https://www-devel.kde.org

Plan

Overview

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.

Currently on progress

Content transposition from one website to another.
Theming (by Ken)

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.

Scratch repos for themes

Ken:
Neverland:

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?)

Announcements: Based on a normal blog post, however we need to link this somehow to the git repos/scripts

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 [done]; Need to know who is allowed to do what [reflection to continue with sysadmin]

@@ Line 1: / Line 1: @@
-== We need to get things done. ==
+== Comparison ==
+=== A very nice table that I'm very proud of having done by myself, because, hey it looks nice! ===
+There were discussions about what to use. At the end, 3 solutions where retained:
+{|class="wikitable" style="border: 1px solid grey;"
+! 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. The website is on https://www-devel.kde.org
+== Plan ==
+=== Overview ===
+We want to release something as early as possible, even if not finished.
-There were discussions about what to use. At the end, 3 solutions where retained:
+'''What is mandatory: Announcements + Theme + Plain pages (what is KDE...)'''
-* 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 ==
+The Applications things can be worked on later, after release.
-Might need to be reorganized...
-=== Step 1 ===
+The theme will be based on the current neon.kde.org. It looks modern and has good feedback.
-Choose solution.
-Solution: ......
-=== Step 2 ===
+=== Currently on progress ===
-* Get a test host by the sysadmin [in progress]
+* Content transposition from one website to another.
-* build the solution and test things
+* Theming (by Ken)
-* Create palette and style
-=== Step 3 ===
+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.
-* Create neverland-based theme.
-=== Step N ===
+=== Scratch repos for themes ===
-* replace current kde.org
+* Ken:
+* Neverland:
 == Specifications ==
@@ Line 40: / Line 68: @@
 : Grid with applications, on click, show details
 : Idea: use e-commerce plugin and remove prices (can we subclass a plugin?)
+; Announcements
+: Based on a normal blog post, however we need to link this somehow to the git repos/scripts
 ; Blogs, tweets and other feeds
@@ Line 49: / Line 80: @@
 === Other features ===
 ; Access
-: Need a ldap/phabricator connection
+: Need a ldap/phabricator connection [done]
-: Need to know who is allowed to do what
+: Need to know who is allowed to do what [reflection to continue with sysadmin]