From a860b9fca3f2fd2ba33a3a591824190eb74a3e1a Mon Sep 17 00:00:00 2001 From: Louise Crow Date: Wed, 16 Jul 2014 16:27:02 +0100 Subject: Add a 'next steps' page, referenced at the end of install guides. --- docs/installing/next_steps.md | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 docs/installing/next_steps.md (limited to 'docs/installing/next_steps.md') diff --git a/docs/installing/next_steps.md b/docs/installing/next_steps.md new file mode 100644 index 000000000..98a661416 --- /dev/null +++ b/docs/installing/next_steps.md @@ -0,0 +1,34 @@ +--- +layout: page +title: Next Steps +--- +# Next Steps + +

+ OK, you've installed a copy of Alaveteli, and can see the site in a browser. What next? +

+ + +### Create a superuser account for yourself + +* Sign up for a new account on the site. You should receive a confirmation email. Click on the link in it to confirm the account. + +* Get access to the [admin interface]({{ site.baseurl}}docs/running/admin_manual/#administrator-privileges). You can find the +`general.yml` file you'll need to get the `ADMIN_USERNAME` and +`ADMIN_PASSWORD` credentials in the `config` subdirectory of the +directory Alaveteli was installed into. + +* In the admin interface, go to the 'Users' section and find the account you just created. Promote the account you just created to superuser status by clicking the 'Edit' button and setting the 'Admin level' value to 'super'. + +### Test out the request process + +* Create a new public authority in the admin interface - give it a name something like 'Test authority'. Set the request email to an address that you will receive. + +* From the main interface of the site, make a request to the new authority. + +* You should receive the request email - try replying to it. Your response email should appear in Alaveteli. Not working? Take a look at our [troubleshooting tips]({{ site.baseurl}}docs/installing/manual_install/#troubleshooting). If that doesn't sort it out, [get in touch]({{ site.baseurl}}community/) on the project mailing list or IRC +for help. + +### Start thinking about customising Alaveteli + +Check out [our guide]({{ site.baseurl}}docs/customising/). -- cgit v1.2.3 From bf84fd817a33552f76424ff9760db35d9de0ce45 Mon Sep 17 00:00:00 2001 From: Gareth Rees Date: Fri, 18 Jul 2014 16:13:34 +0100 Subject: Update heading levels in next steps --- docs/installing/next_steps.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) (limited to 'docs/installing/next_steps.md') diff --git a/docs/installing/next_steps.md b/docs/installing/next_steps.md index 98a661416..a0655e74d 100644 --- a/docs/installing/next_steps.md +++ b/docs/installing/next_steps.md @@ -8,8 +8,7 @@ title: Next Steps OK, you've installed a copy of Alaveteli, and can see the site in a browser. What next?

- -### Create a superuser account for yourself +## Create a superuser account for yourself * Sign up for a new account on the site. You should receive a confirmation email. Click on the link in it to confirm the account. @@ -20,7 +19,7 @@ directory Alaveteli was installed into. * In the admin interface, go to the 'Users' section and find the account you just created. Promote the account you just created to superuser status by clicking the 'Edit' button and setting the 'Admin level' value to 'super'. -### Test out the request process +## Test out the request process * Create a new public authority in the admin interface - give it a name something like 'Test authority'. Set the request email to an address that you will receive. @@ -29,6 +28,6 @@ directory Alaveteli was installed into. * You should receive the request email - try replying to it. Your response email should appear in Alaveteli. Not working? Take a look at our [troubleshooting tips]({{ site.baseurl}}docs/installing/manual_install/#troubleshooting). If that doesn't sort it out, [get in touch]({{ site.baseurl}}community/) on the project mailing list or IRC for help. -### Start thinking about customising Alaveteli +## Start thinking about customising Alaveteli Check out [our guide]({{ site.baseurl}}docs/customising/). -- cgit v1.2.3 From 020357d24a79109f860871f3dabbc0f998b7a9bf Mon Sep 17 00:00:00 2001 From: Gareth Rees Date: Fri, 18 Jul 2014 16:14:00 +0100 Subject: Move creating test data to Next Steps page --- docs/installing/next_steps.md | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'docs/installing/next_steps.md') diff --git a/docs/installing/next_steps.md b/docs/installing/next_steps.md index a0655e74d..44660f5c8 100644 --- a/docs/installing/next_steps.md +++ b/docs/installing/next_steps.md @@ -8,6 +8,13 @@ title: Next Steps OK, you've installed a copy of Alaveteli, and can see the site in a browser. What next?

+## Load test data + +If you want some dummy data to play with, you can try loading the fixtures that +the test suite uses into your development database. You can do this with: + + script/load-sample-data + ## Create a superuser account for yourself * Sign up for a new account on the site. You should receive a confirmation email. Click on the link in it to confirm the account. -- cgit v1.2.3 From e945edffc896a8eeb35711ed3534c7808c3c9e60 Mon Sep 17 00:00:00 2001 From: Gareth Rees Date: Wed, 15 Oct 2014 15:31:40 +0100 Subject: Use consistent heading MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script loads “sample” data so the heading should say the same --- docs/installing/next_steps.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/installing/next_steps.md') diff --git a/docs/installing/next_steps.md b/docs/installing/next_steps.md index 44660f5c8..7763ede2b 100644 --- a/docs/installing/next_steps.md +++ b/docs/installing/next_steps.md @@ -8,7 +8,7 @@ title: Next Steps OK, you've installed a copy of Alaveteli, and can see the site in a browser. What next?

-## Load test data +## Load sample data If you want some dummy data to play with, you can try loading the fixtures that the test suite uses into your development database. You can do this with: -- cgit v1.2.3 From 5a58797a919d78d50a185633bd61049c75e12f61 Mon Sep 17 00:00:00 2001 From: Gareth Rees Date: Wed, 15 Oct 2014 15:32:00 +0100 Subject: Update search index after loading sample data --- docs/installing/next_steps.md | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'docs/installing/next_steps.md') diff --git a/docs/installing/next_steps.md b/docs/installing/next_steps.md index 7763ede2b..cd024343f 100644 --- a/docs/installing/next_steps.md +++ b/docs/installing/next_steps.md @@ -15,6 +15,10 @@ the test suite uses into your development database. You can do this with: script/load-sample-data +You should then update the Xapian search index for the new data: + + script/update-xapian-index + ## Create a superuser account for yourself * Sign up for a new account on the site. You should receive a confirmation email. Click on the link in it to confirm the account. -- cgit v1.2.3 From 015e4130975b44b9b5242045152bced5ec6068fa Mon Sep 17 00:00:00 2001 From: Gareth Rees Date: Wed, 5 Nov 2014 15:29:29 +0000 Subject: Add docs on importing authorities from CSV The uploader page is self documenting, so just point to the URL of the page. --- docs/installing/next_steps.md | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'docs/installing/next_steps.md') diff --git a/docs/installing/next_steps.md b/docs/installing/next_steps.md index cd024343f..146b0dad9 100644 --- a/docs/installing/next_steps.md +++ b/docs/installing/next_steps.md @@ -39,6 +39,12 @@ directory Alaveteli was installed into. * You should receive the request email - try replying to it. Your response email should appear in Alaveteli. Not working? Take a look at our [troubleshooting tips]({{ site.baseurl}}docs/installing/manual_install/#troubleshooting). If that doesn't sort it out, [get in touch]({{ site.baseurl}}community/) on the project mailing list or IRC for help. +## Import Public Authorities + +Alaveteli can import a list of public authorities and their contact email addresses from a CSV file. + +You can find the uploader in under the "Authorities" tab of the admin section, or go straight to `/admin/body/import_csv`. + ## Start thinking about customising Alaveteli Check out [our guide]({{ site.baseurl}}docs/customising/). -- cgit v1.2.3 From 5ce690b530772ec6dab0c9d12e3f0d3147f7973b Mon Sep 17 00:00:00 2001 From: Dave Whiteland Date: Mon, 29 Sep 2014 11:03:51 -0500 Subject: cleanup of AMI and Next Steps documentation Includes addition of the "emergency user" This is largely after following the instructions through on a clean AMI install and noticing all the pinnch-points where confusiion or even errors occurred. revisited on arrival in Mexico (after 2 weeks' holiday, so this got a bit behind) --- docs/installing/next_steps.md | 103 ++++++++++++++++++++++++++++++++++++------ 1 file changed, 88 insertions(+), 15 deletions(-) (limited to 'docs/installing/next_steps.md') diff --git a/docs/installing/next_steps.md b/docs/installing/next_steps.md index cd024343f..1426a2fce 100644 --- a/docs/installing/next_steps.md +++ b/docs/installing/next_steps.md @@ -8,36 +8,109 @@ title: Next Steps OK, you've installed a copy of Alaveteli, and can see the site in a browser. What next?

+## Create a superuser admin account + +Alaveteli ships with an +emergency user +that has access to the admin. So when you've just created a new site, you +should sign up to create your own account, then log into admin as the emergency +user to promote your new account to be an administrator with *super* privileges. + +As soon as that's done, disable the emergency user, because you don't need to +use it any more: you've superseded it with your new admin account. + +Alaveteli ships with sample data that includes a dummy admin user called "Joe +Admin". If the sample data has been loaded into the database (this will depend on +how you installed), you must revoke Joe's administrator status too, because you +will be using your own admin account instead. + +### Step-by-step: + +First, in the browser: + +* Go to `/profile/sign_in` and create a user by signing up. +* Check your email and confirm your account. +* Go to `/admin?emergency=1`, log in with the username and password you specified in + [`ADMIN_USERNAME`]({{site.baseurl}}docs/customising/config/#admin_username) + and [`ADMIN_PASSWORD`]({{site.baseurl}}docs/customising/config/#admin_password). + You can find these settings in `config/general.yml`. +* You're now on the Alaveteli admin page. +* Click on **Users** (in the navigation menu across the top of the page), and + click on your name in the list of users. On *that* page, click **Edit**. +* Change your *Admin level* to "super" and click **Save**. +* From now on, when you are logged into your Alavateli site, you'll have access + to the admin (at `/admin`). Furthermore, you'll see links to admin pages off + the main site (which don't appear for regular users). + +If your installation has loaded the sample data, there will be a dummy user in +your database called "Joe Admin" who has admin status too. You should remove +this status so there's no risk of it being used to access your site admin. You +can either do this while you're still logged in as the emergency user... or +else, later, logged in as yourself: + +* Go to `/admin/users` or click on **Users** in the navigation menu on any + admin page. +* Find "Joe Admin" in the list of users, and click on the name to see the + user details. On *that* page, click **Edit**. +* Change the *Admin level* from "super" to "none" and click **Save**. +* Joe Admin no longer has admin status. + +Now that your account is a superuser admin, you don't need to allow the +emergency user access to the admin. On the command line shell, edit +`/var/www/alaveteli/alaveteli/config/general.yml`: + +* It's important that you change the emergency user's password (and, ideally, + the username too) from the values Alavateli ships with, because they are + public and hence insecure. In `general.yml`, change + [`ADMIN_PASSWORD`]({{site.baseurl}}docs/customising/config/#admin_password) + (and maybe [`ADMIN_USERNAME`]({{site.baseurl}}docs/customising/config/#admin_username) + too) to new, unique values. +* Additionally, you can totally disable the emergency user. Under normal + operation you don't need it, because from now on you'll be using the admin + user you've just created. + Set [`DISABLE_EMERGENCY_USER`]({{site.baseurl}}docs/customising/config/#disable_emergency_user) + to `true`. +* To apply these changes restart the service as a user with root privileges: + `sudo service alaveteli restart` + +You can use the same process (logged in as your admin account) to add or remove +superuser admin status to any users that are subsequently added to your site. +If you accidentally remove admin privilege from all accounts (try not to do +this, though!), you can enable the emergency user by editing the `general.yml` +file and restarting Alaveteli. + ## Load sample data If you want some dummy data to play with, you can try loading the fixtures that -the test suite uses into your development database. You can do this with: +the test suite uses into your development database. As the `alaveteli` user, do: script/load-sample-data -You should then update the Xapian search index for the new data: - - script/update-xapian-index +If the sample data has already been loaded into the database, this command won't +do anything, but will instead fail +with an error. -## Create a superuser account for yourself +If you have added the sample data, update the Xapian search index afterwards: -* Sign up for a new account on the site. You should receive a confirmation email. Click on the link in it to confirm the account. - -* Get access to the [admin interface]({{ site.baseurl}}docs/running/admin_manual/#administrator-privileges). You can find the -`general.yml` file you'll need to get the `ADMIN_USERNAME` and -`ADMIN_PASSWORD` credentials in the `config` subdirectory of the -directory Alaveteli was installed into. + script/update-xapian-index -* In the admin interface, go to the 'Users' section and find the account you just created. Promote the account you just created to superuser status by clicking the 'Edit' button and setting the 'Admin level' value to 'super'. +Remember that the sample data includes a user with admin access to your site. +You should revoke that status so it cannot be used to access your site -- +follow the steps described in the previous section. ## Test out the request process -* Create a new public authority in the admin interface - give it a name something like 'Test authority'. Set the request email to an address that you will receive. +* Create a new public authority in the admin interface -- give it a name like + "Test authority". Set the request email to an address that you will receive. * From the main interface of the site, make a request to the new authority. -* You should receive the request email - try replying to it. Your response email should appear in Alaveteli. Not working? Take a look at our [troubleshooting tips]({{ site.baseurl}}docs/installing/manual_install/#troubleshooting). If that doesn't sort it out, [get in touch]({{ site.baseurl}}community/) on the project mailing list or IRC -for help. +* You should receive the request email -- try replying to it. Your response + email should appear in Alaveteli. Not working? Take a look at our + [troubleshooting tips]({{ site.baseurl}}docs/installing/manual_install/#troubleshooting). + If that doesn't sort it out, [get in touch]({{ site.baseurl}}community/) on + the [developer mailing list](https://groups.google.com/forum/#!forum/alaveteli-dev) or [IRC](http://www.irc.mysociety.org/) for help. ## Start thinking about customising Alaveteli -- cgit v1.2.3 From 931e54cf6a6289c20ff9fda08fa475b241c8007c Mon Sep 17 00:00:00 2001 From: Dave Whiteland Date: Wed, 7 Jan 2015 15:55:00 +0000 Subject: new entries and small tidies in glossary around admin/superuser --- docs/installing/next_steps.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'docs/installing/next_steps.md') diff --git a/docs/installing/next_steps.md b/docs/installing/next_steps.md index 4199daabf..20c69a504 100644 --- a/docs/installing/next_steps.md +++ b/docs/installing/next_steps.md @@ -14,7 +14,9 @@ Alaveteli ships with an emergency user that has access to the admin. So when you've just created a new site, you should sign up to create your own account, then log into admin as the emergency -user to promote your new account to be an administrator with *super* privileges. +user to promote your new account to be an administrator with +super +privilege. As soon as that's done, disable the emergency user, because you don't need to use it any more: you've superseded it with your new admin account. -- cgit v1.2.3 From 6401cabe3b5faf72afd470f6d990e69108e55827 Mon Sep 17 00:00:00 2001 From: Dave Whiteland Date: Tue, 27 Jan 2015 18:01:46 +0000 Subject: tidy maintenance: admin sectionn of admin_guide Remove duplicate instructions (link to next_steps instead), tidy up and use glossary. --- docs/installing/next_steps.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) (limited to 'docs/installing/next_steps.md') diff --git a/docs/installing/next_steps.md b/docs/installing/next_steps.md index 20c69a504..896f09b0a 100644 --- a/docs/installing/next_steps.md +++ b/docs/installing/next_steps.md @@ -8,6 +8,13 @@ title: Next Steps OK, you've installed a copy of Alaveteli, and can see the site in a browser. What next?

+ * [Create a superuser admin account](#create-a-superuser-admin-account) + * [Load sample data](#load-sample-data) + * [Test out the request process](#test-out-the-request-process) + * [Import Public Authorities](#import-public-authorities) + + + ## Create a superuser admin account Alaveteli ships with an @@ -118,7 +125,8 @@ follow the steps described in the previous section. Alaveteli can import a list of public authorities and their contact email addresses from a CSV file. -You can find the uploader in under the "Authorities" tab of the admin section, or go straight to `/admin/body/import_csv`. +Follow the instructions for +[uploading public authority data]({{ site.baseurl }}docs/running/admin_manual/#creating-changing-and-uploading-public-authority-data). ## Start thinking about customising Alaveteli -- cgit v1.2.3 From b608f2717c2ddc2230da26590980db4cb1e32e1b Mon Sep 17 00:00:00 2001 From: Louise Crow Date: Thu, 8 Jan 2015 12:55:24 +0000 Subject: Add some guidance about how to add public holidays. Also what the effect will be. --- docs/installing/next_steps.md | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) (limited to 'docs/installing/next_steps.md') diff --git a/docs/installing/next_steps.md b/docs/installing/next_steps.md index 4199daabf..d5c4675f0 100644 --- a/docs/installing/next_steps.md +++ b/docs/installing/next_steps.md @@ -118,6 +118,46 @@ Alaveteli can import a list of public authorities and their contact email addres You can find the uploader in under the "Authorities" tab of the admin section, or go straight to `/admin/body/import_csv`. +## Set the amount of time authorities will be given to respond to requests + +In most countries that have a Freedom of Information law, authorities +have a certain number of days in order to respond to requests. Alaveteli +helps requesters by reminding them when their request is overdue for a +response according to the law. You can set the number of days an +authority is given to respond to a request in the +[`REPLY_LATE_AFTER_DAYS`]({{site.baseurl}}docs/customising/config/#reply_late_after_days), +[`REPLY_VERY_LATE_AFTER_DAYS`]({{site.baseurl}}docs/customising/config/#reply_very_late_after_days) +and +[`SPECIAL_REPLY_VERY_LATE_AFTER_DAYS`]({{site.baseurl}}docs/customising/config/#special_reply_very_late_after_days) +options in `config/general.yml`. Most laws specify that the days are +either working days, or calendar days. You can set this using the +[`WORKING_OR_CALENDAR_DAYS`]({{site.baseurl}}docs/customising/config/#working_or_calendar_days) +option in `config/general.yml`. + +## Add some public holidays + +
+Interface introduced in Alaveteli version 0.21 +
+ +Alaveteli calculates the due dates of requests taking account of the +public holidays you enter into the admin interface. If you have set the +[`WORKING_OR_CALENDAR_DAYS`]({{site.baseurl}}docs/customising/config/#working_or_calendar_days) +setting for Alaveteli to `working`, the date when a response to a +request is officially overdue will be calculated in days that are not +weekends or public holidays. If you have set +[`WORKING_OR_CALENDAR_DAYS`]({{site.baseurl}}docs/customising/config/#working_or_calendar_days) +to `calendar`, the date will be calculated in calendar days, but if the +due date falls on a public holiday or weekend day, then the due date is +considered to be the next week day that isn't a holiday. + +To add public holidays, go to the "Holidays" tab of the admin interface. +From here you can either add each holiday day by hand, using the "New +Holiday" button, or you can create multiple holidays at once using the +"Create holidays from suggestions or iCal feed" button. + ## Start thinking about customising Alaveteli Check out [our guide]({{ site.baseurl}}docs/customising/). + + -- cgit v1.2.3 From 551e0a18cc474e70069f8bb219c17b082d967fb0 Mon Sep 17 00:00:00 2001 From: Dave Whiteland Date: Wed, 1 Apr 2015 19:33:02 +0100 Subject: update table of contents on next_steps page --- docs/installing/next_steps.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'docs/installing/next_steps.md') diff --git a/docs/installing/next_steps.md b/docs/installing/next_steps.md index 2c6e84e1b..d5c62a986 100644 --- a/docs/installing/next_steps.md +++ b/docs/installing/next_steps.md @@ -12,7 +12,9 @@ title: Next Steps * [Load sample data](#load-sample-data) * [Test out the request process](#test-out-the-request-process) * [Import Public Authorities](#import-public-authorities) - + * [Set the amount of time [...] to respond to requests](#set-the-amount-of-time-authorities-will-be-given-to-respond-to-requests) + * [Add some public holidays](#add-some-public-holidays) + * [Start thinking about customising Alaveteli](#start-thinking-about-customising-alaveteli) ## Create a superuser admin account -- cgit v1.2.3 From 130725a8d8b90d6d5bd350b6be59efb1b89cab47 Mon Sep 17 00:00:00 2001 From: Dave Whiteland Date: Wed, 1 Apr 2015 19:40:57 +0100 Subject: small changes to interface description in next_steps --- docs/installing/next_steps.md | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) (limited to 'docs/installing/next_steps.md') diff --git a/docs/installing/next_steps.md b/docs/installing/next_steps.md index d5c62a986..05a6445e1 100644 --- a/docs/installing/next_steps.md +++ b/docs/installing/next_steps.md @@ -153,20 +153,25 @@ Interface introduced in Alaveteli version 0.21 Alaveteli calculates the due dates of requests taking account of the -public holidays you enter into the admin interface. If you have set the +public holidays you enter into the admin interface. + +If you have set the [`WORKING_OR_CALENDAR_DAYS`]({{site.baseurl}}docs/customising/config/#working_or_calendar_days) setting for Alaveteli to `working`, the date when a response to a request is officially overdue will be calculated in days that are not -weekends or public holidays. If you have set +weekends or public holidays. + +If you have set [`WORKING_OR_CALENDAR_DAYS`]({{site.baseurl}}docs/customising/config/#working_or_calendar_days) to `calendar`, the date will be calculated in calendar days, but if the due date falls on a public holiday or weekend day, then the due date is considered to be the next week day that isn't a holiday. -To add public holidays, go to the "Holidays" tab of the admin interface. -From here you can either add each holiday day by hand, using the "New -Holiday" button, or you can create multiple holidays at once using the -"Create holidays from suggestions or iCal feed" button. +To add public holidays, go to the +admin interface +and click on **Holidays**. From here you can either add each day of holiday by +hand, using the **New Holiday** button, or you can create multiple holidays at +once using the **Create holidays from suggestions or iCal feed** button. ## Start thinking about customising Alaveteli -- cgit v1.2.3 From 38cab1a0fc57ce47266951885fbb951602db309c Mon Sep 17 00:00:00 2001 From: Dave Whiteland Date: Wed, 1 Apr 2015 19:58:41 +0100 Subject: add holiday to glossary (explaining why it matters) --- docs/installing/next_steps.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'docs/installing/next_steps.md') diff --git a/docs/installing/next_steps.md b/docs/installing/next_steps.md index 05a6445e1..af86331e8 100644 --- a/docs/installing/next_steps.md +++ b/docs/installing/next_steps.md @@ -153,7 +153,8 @@ Interface introduced in Alaveteli version 0.21 Alaveteli calculates the due dates of requests taking account of the -public holidays you enter into the admin interface. +public holidays +you enter into the admin interface. If you have set the [`WORKING_OR_CALENDAR_DAYS`]({{site.baseurl}}docs/customising/config/#working_or_calendar_days) -- cgit v1.2.3 From 6cc59ede7bca866f7e56c771cc12ca1afa9406ef Mon Sep 17 00:00:00 2001 From: Dave Whiteland Date: Wed, 1 Apr 2015 19:59:28 +0100 Subject: change iCal to iCalendar (used to be iCal, which it isn't any more http://en.wikipedia.org/wiki/ICalendar ) --- docs/installing/next_steps.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/installing/next_steps.md') diff --git a/docs/installing/next_steps.md b/docs/installing/next_steps.md index af86331e8..2b7acbd45 100644 --- a/docs/installing/next_steps.md +++ b/docs/installing/next_steps.md @@ -172,7 +172,7 @@ To add public holidays, go to the admin interface and click on **Holidays**. From here you can either add each day of holiday by hand, using the **New Holiday** button, or you can create multiple holidays at -once using the **Create holidays from suggestions or iCal feed** button. +once using the **Create holidays from suggestions or iCalendar feed** button. ## Start thinking about customising Alaveteli -- cgit v1.2.3