PmWiki.PmWiki History

Hide minor edits - Show changes to markup - Cancel

Changed line 19 from:

For more on how the Pm Wiki has been used in this site, contact the site editor.

to:

For more on how the Pm Wiki has been used in this site, contact the Site Editor.

Changed line 19 from:

For more on how the Pm Wiki has been used in this site, contact site editor?

to:

For more on how the Pm Wiki has been used in this site, contact the site editor.

Added lines 18-19:

For more on how the Pm Wiki has been used in this site, contact site editor?

Changed lines 3-4 from:

Pm Wiki pages look and act like normal web pages, except they have an "Edit" link that makes it easy to modify existing pages and add new pages into the website, using basic editing rules. You do not need to know or use any HTML or CSS. Page editing can be left open to the public or restricted to small groups of authors.

to:

Pm Wiki pages look and act like normal web pages, except they have an "Edit" link that makes it easy to modify existing pages and add new pages into the website, using basic editing rules. You do not need to know or use any HTML or CSS. Page editing can be left open to the public or restricted to small groups of authors. However, in this Pm Wiki the site administrator has required password access to editing. in this way the content of this particular Pm Wiki is subject to editorial control.

Changed lines 7-11 from:
Custom look-and-feel: A site administrator can quickly change the appearance and functions of a Pm Wiki site by using different skins and HTML templates. If you can't find an appropriate skin already made, you can easily modify one or create your own.
Access control: Pm Wiki password protection can be applied to an entire site, to groups of pages, or to individual pages. Password protection controls who can read pages, edit pages, and upload attachments. Pm Wiki's access control system is completely self-contained, but it can also work in conjunction with existing password databases, such as .htaccess, LDAP servers, and My SQL? databases.
Customization and plugin architecture: One principle of the PmWikiPhilosophy is to only include essential features in the core engine, but make it easy for administrators to customize and add new markup. Hundreds of features are already available by using extensions (called "recipes") that are available from the Pm Wiki Cookbook.
to:
Custom look-and-feel: A site administrator can quickly change the appearance and functions of a Pm Wiki site by using different skins and HTML templates. If you can't find an appropriate skin already made, you can easily modify one or create your own. In this case the site administrator has set the skin to the Gemini skin, but has modified it in certain ways to better suit the look and feel he requires.
Access control: Pm Wiki password protection can be (and has been) applied to an entire site, to groups of pages, or to individual pages. Password protection controls who can read pages, edit pages, and upload attachments. Pm Wiki's access control system is completely self-contained, but it can also work in conjunction with existing password databases, such as .htaccess, LDAP servers, and My SQL? databases.
Customization and plugin architecture: One principle of the PmWikiPhilosophy is to only include essential features in the core engine, but make it easy for administrators to customize and add new markup. Hundreds of features are already available by using extensions (called "recipes") that are available from the Pm Wiki Cookbook. Many of these are used in this implementation.


Page last modified on January 12, 2013, at 09:33 AM