https://community.kde.org/api.php?action=feedcontributions&user=Johnpaulding&feedformat=atomKDE Community Wiki - User contributions [en]2024-03-28T15:46:45ZUser contributionsMediaWiki 1.40.2https://community.kde.org/index.php?title=KDE.org/New_Site&diff=78801KDE.org/New Site2017-11-14T02:57:16Z<p>Johnpaulding: Comparation to Comparison (US Eng)</p>
<hr />
<div>== Comparison ==<br />
=== A very nice table that I'm very proud of having done by myself, because, hey it looks nice! ===<br />
There were discussions about what to use. At the end, 3 solutions where retained:<br />
{|class="wikitable" style="border: 1px solid grey;"<br />
! Type <br />
! Getting things done <br />
! Maintainability <br />
! Custom themes <br />
! Localization<br />
|-<br />
! Wordpress<br />
| Very fast for basic stuff, more difficult for specific needs<br />
|| Very good if we don't need to develop new plugins<br />
|| Not sure if possible to have several presentations of posts<br />
|| Seems to be possible with extra plugins (POT?)<br />
|-<br />
! Drupal<br />
| A little more difficult for basic stuff but constant learning curve<br />
|| 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<br />
|| A theme should be written from scratch / expended. Almost everything possible<br />
|| Feature present in core. POT files should be exportable with plugins<br />
|-<br />
! Custom solution<br />
| Very specific, unexpected issues can appear because of corner cases<br />
|| 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?<br />
|| Everything possible, should be written.<br />
|| Whatever we want<br />
|-<br />
|}<br />
<br />
=== Conclusion ===<br />
* Wordpress seems too simplistic for what we need. <br />
* Drupal will need a custom theme and certainly some extra modules (specially for the applications page + announcements) but the tests are very promising.<br />
* 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... <br />
<br />
<br />
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<br />
<br />
== Plan ==<br />
<br />
=== Overview ===<br />
We want to release something as early as possible, even if not finished. <br />
<br />
'''What is mandatory: Announcements + Theme + Plain pages (what is KDE...)'''<br />
<br />
The Applications things can be worked on later, after release.<br />
<br />
The theme will be based on the current neon.kde.org. It looks modern and has good feedback.<br />
<br />
=== Currently on progress ===<br />
* Content transposition from one website to another.<br />
* Theming (by Ken)<br />
<br />
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.<br />
<br />
=== Scratch repos for themes ===<br />
* Ken:<br />
* Neverland:<br />
<br />
== Specifications ==<br />
<br />
=== Type of content ===<br />
; Pages<br />
: normal pages with text/picture content<br />
: Difficulty: easy<br />
<br />
; Applications <br />
: Grid with applications, on click, show details<br />
: Idea: use e-commerce plugin and remove prices (can we subclass a plugin?)<br />
<br />
; Announcements<br />
: Based on a normal blog post, however we need to link this somehow to the git repos/scripts<br />
<br />
; Blogs, tweets and other feeds<br />
: Feeds plugin,<br />
<br />
=== Theme ===<br />
The theme must be usable (in term of style and colors) by all the KDE websites and represent its identity.<br />
<br />
=== Other features ===<br />
; Access<br />
: Need a ldap/phabricator connection [done]<br />
: Need to know who is allowed to do what [reflection to continue with sysadmin]</div>Johnpaulding