KDE.org/New Site: Difference between revisions
< KDE.org
| Line 38: | Line 38: | ||
== Plan == | == 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...) | What is mandatory: Announcements + Theme + Plain pages (what is KDE...) | ||
| Line 46: | Line 47: | ||
The theme will be based on the current neon.kde.org. It looks modern and has good feedback. | The theme will be based on the current neon.kde.org. It looks modern and has good feedback. | ||
=== Currently on progress | === Currently on progress === | ||
* Content transposition from one website to another. | * Content transposition from one website to another. | ||
* Theming (by Ken) | * Theming (by Ken) | ||
| Line 54: | Line 55: | ||
Repos for themes: | Repos for themes: | ||
* Ken: | * Ken: | ||
* Neverland: | * Neverland: | ||
== Specifications == | == Specifications == | ||
Revision as of 17:44, 7 September 2016
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.
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.
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]