Rename "Edit site pages" to "General pages" to "Static pages"

Patch for "master" branch: https://reviews.mahara.org/3025

To test:

1. Go to Administration -> Configure site. You should see "General pages" in the menu.
2. On that page (/admin/site/pages.php), the heading needs to read "General pages" and the text is changed slightly as well.
3. Go to Administration -> Institutions and you'll see "General pages" in the menu.

Reviewed: https://reviews.mahara.org/3025
Committed: http://gitorious.org/mahara/mahara/commit/7a32362d3dd11ff620827634b5e5b20550f17e22
Submitter: Robert Lyon (<email address hidden>)
Branch: master

commit 7a32362d3dd11ff620827634b5e5b20550f17e22
Author: Kristina D.C. Hoeppner <email address hidden>
Date: Wed Feb 19 20:11:25 2014 +0100

Rename "Edit site pages" to "General pages" (Bug #1282219)

This renaming is to avoid confusion to other site
pages that can be built like portfolio pages and are
very different from these here where only a little
bit of text can be changed.

I also took the opportunity to get rid of the "Edit"
as no other menu item has a verb included.

Change-Id: Iafb5d9ca09d5bc5c3c483b0caeb28b77e88e6c72
Signed-off-by: Kristina D.C. Hoeppner <email address hidden>

I agree that we need to change these from being called "site pages". However, I think "general pages" is maybe not the best replacement. It avoids the confusion of the word "site", but I'd like to get something more descriptive than "general".

I'd also like to avoid calling these "pages" at all, because:

1. In Mahara, a "Page" means a portfolio page, with blocks on it. It's confusing to use it in other contexts, especially other editable contexts that use a different editing mechanism.

2. Some of these are not even standalone webpages. "Home (Dashboard)" and "Terms and Conditions" are inserted as text snippets into other webpages.

How about... "system messages"?

There are not really "Messages" either. Messages means for me that it is something that can be sent via a notification, but the pages are the terms and conditions and About us amongst dashboard and logged-out home which are proper pages.

Some more possibilities:

1. Sitepages (all one word -- might not translate well, though)

2. System screens

3. System notices

I wouldn't go for 1.

What about "General information"? I'd be OK with "System screens" though they are a bit like "Site" as we usually speak of the entire system when we mean the site, but an institution admin would change certain information. "System notices" has the same issue for me as above. It's even closer to notifications.

It's a tricky one. Maybe we should ask for some feedback on the forums and/or Twitter? :)

How about "static pages"? I think that's the term that comes the closest to conveying what these things are.

It also passes the self-documenting test. If I were a new Mahara admin looking through the admin menu and I saw "edit static pages", I would imagine that it means something like the "About us" page. And coming from the other direction, if I was trying to figure out how to change the "About us" page, I'd click on "edit static pages".

It does have the downside of having the word "page" in it, but since portfolio Pages are by definition not static, it's clear it doesn't refer to those. There's still the problem that some of these "static pages" are snippets rather than pages... but no solution is perfect. :)

Patch for "master" branch: https://reviews.mahara.org/3132

We asked on the forums and no one really had any useful suggestions there. Well, they had useful suggestions, but those suggestions were around the idea of replacing the current system of HTML fields with one where sitepages/generalpages/staticpages are full-on Portfolio Pages with blocks and everything. And while that would be a good idea in the long run, it's not doable right now before 1.9.0 and it didn't help us come up with a better name.

So I've pushed a patch to rename these from "general pages" to "static pages". One of my pet peeves with Moodle administration is that it is full of names for things that don't tell you anything about how those things are different from each other. For instance, groups, groupings, and cohorts. All basically synonyms, and thus the names are not self-documenting in the least.

Since Mahara already has usability issues, I'd like to try to make it so that when we rename Mahara features, we give them names that make it self-evident to the user, how these features are different from each other. To that end, "static pages" is better than "general pages" when it comes to differentiating these from normal portfolio Pages.

Reviewed: https://reviews.mahara.org/3132
Committed: http://gitorious.org/mahara/mahara/commit/d4c63e88439c574e8f1d565177fc715a1276635d
Submitter: Robert Lyon (<email address hidden>)
Branch: master

commit d4c63e88439c574e8f1d565177fc715a1276635d
Author: Aaron Wells <email address hidden>
Date: Fri Mar 28 12:31:29 2014 +1300

Renaming general pages to static pages

Bug1282219: See the lengthy discussion on the bug tracker. No perfect name
for these items has arisen yet, but I think "static pages" is the best
so far because:

1. It means they're obviously not the same type of thing as the Pages in your
portfolio, because those are dynamic.

2. It's more self-evident. If I were brand new to Mahara and were
trying to figure out how to change the "Privacy Policy" page, "Static pages"
is probably what I would think to click on.

Change-Id: I7dd4e3fe6e86fd35dce973afb78b3e56049aab69