This page has been moved to FSFE docs.
Activities Section
Under fsfe.org/activities, we collect all (potentially) time-limited, concrete activities. This could be huge campaigns like "Public Money? Public Code!", short-term actions like "Save Code Share", or long-term engagements like the FSFE Legal Network. They are separated from general, more time-less information texts, e.g. about why Free Software is important for democracy, education; or what Open Standards are.
All activities are categorised in at least three sections: Public Awareness, Policy Advocacy and Legal Support. Some activities can span multiple categories.
Add a new activity
You have a new activity that you want to display on the website? Here's how:
Create a new folder under the /activities/ directory. Give it a good name: short, but understandable. No spaces, avoid hyphens if possible, all lower case. Example here: /activity/myaction/
In it, add a file with the same name as the folder, including the language indicator, e.g. myaction.en.xhtml. This works like any other page on fsfe.org, see the existing ones for inspiration
In the myaction/ folder, add a file called activity.en.xml. Don't change this name! In order to have your activity displayed correctly, read below which meta data it should contain.
Translate an activity
Translators can just copy an activity.en.xml file, exchange en with their language code, and save it in the same directory (e.g. activity.fr.xml).
Then you can start translating all texts between the brackets (>translate me<), no stuff in the attributes (like href="https://" or key="awareness"). Basically, just like all other files on the website.
As with other files, you can check whether your translation is up to date by comparing the <version> number, or just have a look on the Translation status page.
Activity File Syntax
The activity file (activity.en.xml, but can also be translated) contains meta data for an activity. It will be collected by our build system and displayed nicely on the activities page and its category-specific siblings.
As an example, see how the activity file of the PMPC campaign looks like. We will go through each relevant line:
As with every XML/XHTML file, please take care of the <version> tag. Increment it if you changed relevant content of the file that has to be respected for translations. If you just fix a typo, don't touch the version number.
The id attributes holds the ID of the activity. Just set it the same name as the folder.
The date attribute defines the start date of the activity. This is currently not displayed but relevant for sorting. It does not have to be super-specific, but please come up with something in a YYYY-MM-DD format.
The status attribute defines the state of the activity. It can either be active or finished.
The title tag contains the name of the activity.
The description tag contains a description of the activity. Try to keep it at the same length of the other activities. Please no line breaks or special formatting!
In <link href you define where the activity leads to when someone clicks on it
In <image url you can set a square logo for your campaigns. A logo is only displayed if the activity is highlighted (see next point). Please place it to where the other pictures are. Size max. 800x800 pixels, and reduce its file size as good as possible to save space and bandwidth for our users.
In the order tag you can set whether an activity is highlighted, so displayed with a logo and in full width. The higher the priority number, the higher its position compared to the other activities. Check their numbers for comparison.
With a tag, you can set which category an activity belongs to. Choose at least one of awareness, policy and legal. The tags work similar as the tags for news. Please do not randomly other tags than these without corresponding with the Web team!