Jump to content

KDE.org: Difference between revisions

From KDE Community Wiki
Neverendingo (talk | contribs)
No edit summary
Sayakb (talk | contribs)
Line 37: Line 37:
The needs steadily change, and there is always room for coders who are able to contribute HTML, CSS or PHP.
The needs steadily change, and there is always room for coders who are able to contribute HTML, CSS or PHP.


{{Note| Note: Capacity is about to become deprecated, as the mainsite gets prepared to be moved to Wordpress}}
{{Note|Capacity is about to become deprecated, as the mainsite gets prepared to be moved to Wordpress}}


=== Other ===
=== Other ===

Revision as of 23:13, 15 July 2011

Introduction

KDE hosts a variety of websites, from highly dynamic sites to info, documentationational or promotional sites. Volunteering involves very different aspects ranging from

  • writing content
  • moderating in the forum
  • coordinating announcements
  • staying in contact with KDE developers to be aware of latest changes
  • administering dynamic sites like forum, wikis
  • watching out for spammers in those
  • enhancing functionality of the codebase
  • styling/designing the look of our sites
  • etc etc

The webteam works closely with the promo and the sysadmin team in KDE to make sure KDE has a nice working and nice looking web presence.

Discussion about kde websites

Getting involved

Coding

There are a variety of options to get involved. KDE websites use either its own framework (Capacity, see below), or one of the well known frameworks around the web. This includes:

The needs steadily change, and there is always room for coders who are able to contribute HTML, CSS or PHP.

Note

Capacity is about to become deprecated, as the mainsite gets prepared to be moved to Wordpress


Other

Documentation for Capacity

The current default framework for many *.kde.org domains is the /media-framework, aka Capacity. Any documentation about this should go here:

Site Maintainance

KDE.org Upgrade/Overhaul

ToDo (Small tasks)

  • Update award page > Mark Ziegler, Thomas Thym

Meetings


The Team

see here