Skip Navigation

HowTos

Apache 2.2 mod_cache

Server Tuning

Petal i18n and I18NFool

HowTo Compile Apache 1.3 for MKDoc

Integrate Soupermail

Creating new document components

Translate MKDoc Templates

Checkout MKDoc via anon CVS

Configuring MKDoc::Apache_Cache

MySQL commands to make a user account an editor account

Using news headlines

Customisation with CSS

Hiding documents and creating private areas

Upgrade from 1.4 to 1.6

Discussion Board Moderation

Text Component Formatting

Site Administration

Email newsletters

Edit Templates in a Subversion Repository

Update the Metadata for all Documents

Import MS Word files into MKDoc

Sign up

If you sign up for an account on this web site you can customise elements of this site and subscribe to an email newsletter.

If you have an account on this web site you may login.

If you have an account on this site but have forgotten your user name and / or your password then you can request an account reminder email.

Hiding documents and creating private areas

In most circumstances, MKDoc documents are available for wide distribution via as many channels as possible:

  • Clean and clear navigation lets users and search engines find existing documents.

  • RSS XML syndication, headlines and email newsletters allow visitors to discover new content.

  • Extensive metadata such as audience categories and Dublin Core Metadata make searching and indexing more accurate.

Limiting the distribution of documents is sometimes necessary for various reasons:

  • A press-release needs to be written now, but not published for several days.

  • Reference material exists on the site that isn't interesting to the general public.

  • There are documents and areas which should only available to a private group of users.

  • Work-in-progress has to be approved before publication.

  • Partially-trusted users shouldn't be able to edit anything on the public area of the site.

This article explains the technique for shutting-down access channels so these documents can't be found.

Creating a hidden or private document

Simply create or rename a document so that the URI_name (the part that appears in the navigation bar in your browser) starts with either of these magic words: private- or hidden-.

For example, these documents will only appear to exist for logged-in editors:

http://www.example.com/help/private-area/
http://www.example.com/press-releases/hidden-test/

What is the effect?

Make a document hidden and links to the document disappear from everywhere: navigation, sitemap, headlines, RSS, newsletters etc… In addition, any documents attached to that document are themselves hidden — no matter how many there are or how deep the tree is.

Users with editor accounts can see these documents, so if you want to create an intranet, just create a document called hidden-intranet and start adding stuff there.

What else can MKDoc do?

MKDoc uses standard http-authentication, so there are any number of ways of using existing authentication systems to provide fine grained control over who has access to particular documents.

For example, if only two users, sue and bob, are allowed to access hidden documents, then you might configure the apache web server like this:

<LocationMatch /(private|hidden)->
    AuthName "Editors only - Keep Out!"
    AuthGroupFile /var/www/mkdoc/sites/example.com/httpd/groups
    Require group editors
</LocationMatch>

The groups file then needs to contain a list of editors:

editors: sue bob

<< | Up | >>

This document was last modified by Bruno Postle on 2004-07-16 14:19:00
MKDoc Ltd., 31 Psalter Lane, Sheffield, S11 8YL, UK.
Copyright © 2001-2005 MKDoc Ltd.