Get Involved/Web Development: Difference between revisions
m fix formating |
mNo edit summary |
||
Line 13: | Line 13: | ||
Once you're happy with your patch and have verified that it does what you want, it's time to '''generate a diff.''' A diff is a textual representation of the differences between original versions of the files you changed, and the new ones you've produced. You can generate a diff by entering the source repository and running <code>git diff</code>, but we recommend using the <code>arc</code> tool, which will generate a diff and submit it for review very quickly and easily! You can learn how to set it up [https://community.kde.org/Infrastructure/Phabricator#Using_Arcanist_to_post_patches here]. | Once you're happy with your patch and have verified that it does what you want, it's time to '''generate a diff.''' A diff is a textual representation of the differences between original versions of the files you changed, and the new ones you've produced. You can generate a diff by entering the source repository and running <code>git diff</code>, but we recommend using the <code>arc</code> tool, which will generate a diff and submit it for review very quickly and easily! You can learn how to set it up [https://community.kde.org/Infrastructure/Phabricator#Using_Arcanist_to_post_patches here]. | ||
Often you will need to use {{Input|1=arc diff --conduit-uri=https://phabricator.kde.org/ }} instead of {{Input|1=arc diff}} | Often you will need to use {{Input|1=arc diff --conduit-uri=https://phabricator.kde.org/ }} instead of {{Input|1=arc diff}} | ||
KDE uses [https://phabricator.kde.org Phabricator] for patch submission and review. [[Infrastructure/Phabricator|Learn more about how to submit a patch with Phabricator]]. | KDE uses [https://phabricator.kde.org Phabricator] for patch submission and review. [[Infrastructure/Phabricator|Learn more about how to submit a patch with Phabricator]]. |
Revision as of 21:46, 15 September 2019
Introduction
The KDE websites are using a vast varieties of web technology, from CMS to static site generator.
Setting up Jekyll based websites
Setting up Hugo based websites
Setting up Capacity based websites
Submit a patch
Once you're happy with your patch and have verified that it does what you want, it's time to generate a diff. A diff is a textual representation of the differences between original versions of the files you changed, and the new ones you've produced. You can generate a diff by entering the source repository and running git diff
, but we recommend using the arc
tool, which will generate a diff and submit it for review very quickly and easily! You can learn how to set it up here.
Often you will need to use
arc diff --conduit-uri=https://phabricator.kde.org/
instead of
arc diff
KDE uses Phabricator for patch submission and review. Learn more about how to submit a patch with Phabricator.
Communicate with the team
There are several ways to get in touch with KDE web developers, either generally or for a specific project. The most important communications channels are:
- The #kde-www channel on Matrix or the freenode IRC, which is where KDE developers chat in real time about their work.
- The kde-www mailing list is the primary development mailing list. Learn more about mailing lists.