KDE.org: Difference between revisions

From KDE Community Wiki
No edit summary
m (→‎Coding: Mention preferred Hugo version)
 
(11 intermediate revisions by 5 users not shown)
Line 3: Line 3:
== Introduction ==
== Introduction ==


KDE hosts a variety of websites, from highly dynamic sites to info, documentationational or promotional sites. Volunteering involves very different aspects ranging from  
KDE hosts a variety of websites, from the highly dynamic to info, documentation, and promotional sites. Volunteering involves very different aspects ranging from:
 
* writing content
* writing content
* moderating in the forum
* moderating in the forum
Line 14: Line 15:
* etc etc
* 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.
The web team works closely with the promo and the sysadmin teams to make sure that KDE has a nice-looking and functional web presence.
 
== Getting involved ==
 
=== Coding ===
 
KDE primarily uses [https://gohugo.io Hugo] for its websites. In most cases, running a website locally consists of [https://invent.kde.org/websites/hugo-kde/-/wikis/getting-started installing Go and Hugo] (preferably Hugo Extended version 0.134), and then:
 
{{Input|1=<nowiki>
git clone <repository-link>
cd <cloned-repository>
hugo server
</nowiki>}}
 
A few special websites might have additional instructions on how to set up local development, like  the [https://invent.kde.org/websites/kde-org main KDE.org website], [https://invent.kde.org/websites/planet-kde-org Planet KDE], or the [https://invent.kde.org/documentation/develop-kde-org KDE Developer platform].
 
You can read more about developing with Hugo in the [https://invent.kde.org/websites/hugo-kde/-/wikis/home Hugo KDE repository wiki]. You might also want to check out the [https://invent.kde.org/websites/hugo-kde Hugo KDE] repository itself, as it's where most HTML/SCSS/JS development happens.
 
To create a new Hugo website from scratch, you will want to read the [https://invent.kde.org/websites/hugo-kde-template Tutorial from scratch] and take a look at the [https://invent.kde.org/websites/hugo-kde-template Hugo KDE Website Template].
 
Lastly, to deploy our websites, we use [[Infrastructure/Continuous_Integration_System|Continuous Delivery (CD)]].
 
In addition to Hugo, we also use [[KDE.org/mediawiki|MediaWiki]] for our wikis, and [[KDE.org/Jekyll|Jekyll]] in some rare cases.
 
KDE's web needs steadily change, and there is always room for coders who are able to contribute HTML, SCSS, or JS. Contributing is a matter of:
 
* Visiting our [https://community.kde.org/Matrix Matrix] group: [https://go.kde.org/matrix/#/#kde-www:kde.org #kde-www:kde.org]
* Checking out the [https://invent.kde.org/websites list of KDE Websites]
* Start hacking!
 
=== Contacting the KDE Web team ===
 
* IRC channel: [irc://irc.libera.chat/kde-www #kde-www] (see [https://userbase.kde.org/IRC_Channels IRC Channels] for details)
* Matrix channel: [https://go.kde.org/matrix/#/#kde-www:kde.org #kde-www] (see [https://community.kde.org/Matrix Matrix] for details)
* Mailing list: [http://mail.kde.org/mailman/listinfo/kde-www KDE Mailing Lists] (see http://kde.org/mailinglists/ for details)
 
==  Documentation ==


== Applications ==
=== Setting up kde.org or other capacity based website on your computer ===
See [[KDE.org/applications|kde.org/applications page]].


=== Discussion about kde websites ===
In order to do any development you will want to have a local version of the websites to test before committing. The instructions for how to set this up are here: [[KDE.org/Local Setup|Local Website Setup]].
* IRC channel: #kde-www
* Mailinglist: [http://mail.kde.org/mailman/listinfo/kde-www kde-www] See http://kde.org/mailinglists/ for details


== Getting involved ==
=== Documentation for MediaWiki ===
 
KDE's MediaWiki instance are using the [https://www.mediawiki.org/wiki/Manual:Wiki_family#Giant_switch_statement|WIki family setup].


=== Coding ===
The theme is located at [https://invent.kde.org/websites/aether-mediawiki/ Aether-mediawiki gitlab] and the extensions are the following:


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:
* ConfirmEdit
* DocumentationTags
* Contribution_Scores
* DynamicPageList_(third-party)
* EmbedVideo
* ImageMap
* ParserFunctions
* MassEditRegex
* LiquidThreads
* SpamBlacklist
* TitleBlacklist
* UserMerge
* Interwiki
* Matomo
* Nuke
* And the translation bundle


* [[KDE.org/mediawiki|MediaWiki]]
=== Documentation for the Jekyll theme ===
* Drupal
* [[KDE.org/phpBB|phpBB]]
* GOsa
* WordPress
* Redmine


The needs steadily change, and there is always room for coders who are able to contribute HTML, CSS or PHP.
You can find the documentation for the Jekyll theme in the [https://invent.kde.org/websites/jekyll-kde-theme project README] and a Tutorial is available at [[KDE.org/Jekyll]].


{{Note|Capacity is about to become deprecated, as the mainsite gets prepared to be moved to <del>WordPress</del> Drupal}}
=== Documentation for the cdn export (webpack) ===


=== Setting up the website on your computer ===
The code is available at [https://invent.kde.org/websites/aether-sass/ websites/aether-sass].
In order to do any development you will want to have a local version of the websites to test before committing.
The instructions how to set it up are here [[KDE.org/Local_Setup|Local Website Setup]].


=== Working with Wordpress on kde.org ===
Websites using this theme:
Note: this is not reflecting the current state of kde.org but will be helpful once kde.org has been ported to neverland and wordpress. [[KDE.org/Wordpress_Help|Wordpress Help]]


* Discussion for a new site [[/New Site|here]]
* The wikis: userbase, techbase and community
* [[KDE.org/applications|kde.org/applications]]
* kde.org


==Documentation for Capacity==
=== Documentation for Capacity ===


The current default framework for many *.kde.org domains
The current default framework for many *.kde.org domains
Line 58: Line 103:
* [[KDE.org/Capacity HOWTO| Capacity HOWTO]]
* [[KDE.org/Capacity HOWTO| Capacity HOWTO]]
* [[KDE.org/kde.org-menu]]
* [[KDE.org/kde.org-menu]]
{{Warning|Probably outdated content below}}
=== Working with Wordpress on kde.org ===
Note: this is not reflective of the current state of kde.org but will be helpful once kde.org has been ported to neverland and wordpress. [[KDE.org/Wordpress_Help|Wordpress Help]]
* Discussion for a new site [[/New Site|here]]


== Themes ==
== Themes ==
Line 74: Line 126:
* [[KDE.org/Meetings/June09|wiki meeting in june 2009]]
* [[KDE.org/Meetings/June09|wiki meeting in june 2009]]
* [[KDE.org/Meetings/Akademy 2009|website meeting at GCDS 2009]]
* [[KDE.org/Meetings/Akademy 2009|website meeting at GCDS 2009]]


==The Team==
==The Team==

Latest revision as of 02:22, 5 October 2024

Konqi connects to the internet.

Introduction

KDE hosts a variety of websites, from the highly dynamic to info, documentation, and 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 web team works closely with the promo and the sysadmin teams to make sure that KDE has a nice-looking and functional web presence.

Getting involved

Coding

KDE primarily uses Hugo for its websites. In most cases, running a website locally consists of installing Go and Hugo (preferably Hugo Extended version 0.134), and then:

git clone <repository-link>
cd <cloned-repository>
hugo server

A few special websites might have additional instructions on how to set up local development, like the main KDE.org website, Planet KDE, or the KDE Developer platform.

You can read more about developing with Hugo in the Hugo KDE repository wiki. You might also want to check out the Hugo KDE repository itself, as it's where most HTML/SCSS/JS development happens.

To create a new Hugo website from scratch, you will want to read the Tutorial from scratch and take a look at the Hugo KDE Website Template.

Lastly, to deploy our websites, we use Continuous Delivery (CD).

In addition to Hugo, we also use MediaWiki for our wikis, and Jekyll in some rare cases.

KDE's web needs steadily change, and there is always room for coders who are able to contribute HTML, SCSS, or JS. Contributing is a matter of:

Contacting the KDE Web team

Documentation

Setting up kde.org or other capacity based website on your computer

In order to do any development you will want to have a local version of the websites to test before committing. The instructions for how to set this up are here: Local Website Setup.

Documentation for MediaWiki

KDE's MediaWiki instance are using the family setup.

The theme is located at Aether-mediawiki gitlab and the extensions are the following:

  • ConfirmEdit
  • DocumentationTags
  • Contribution_Scores
  • DynamicPageList_(third-party)
  • EmbedVideo
  • ImageMap
  • ParserFunctions
  • MassEditRegex
  • LiquidThreads
  • SpamBlacklist
  • TitleBlacklist
  • UserMerge
  • Interwiki
  • Matomo
  • Nuke
  • And the translation bundle

Documentation for the Jekyll theme

You can find the documentation for the Jekyll theme in the project README and a Tutorial is available at KDE.org/Jekyll.

Documentation for the cdn export (webpack)

The code is available at websites/aether-sass.

Websites using this theme:

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:

Warning

Probably outdated content below


Working with Wordpress on kde.org

Note: this is not reflective of the current state of kde.org but will be helpful once kde.org has been ported to neverland and wordpress. Wordpress Help

  • Discussion for a new site here

Themes

Site Maintainance

Meetings

The Team

See here

Sub projects