From WikiWorld

Jump to: navigation, search



A page that describes the function and purpose of a content page.


Append the key word Meta to the name of an existing page and insert it in a sentence that instructs members/users to read the meta page for instructions on how to improve the content page.

Example: Feel free to add your touch to the HomePage. Take a look at the MetaHomePage for instructions and guidelines on how to make it a better page.

Common Topics for a MetaPage


One or more statements that describe why the page is important.



A user member may submit ideas for major revisions to a key page before implementing them. A consensus could be implied if no one voices opposition or if the voices of support out weigh the voices of opposition.

Task List

A list of things that should or could be done to a page. A proposal that has reached consensus would be moved to the Task List

Any thing else about the content page

Basically, anything that is not content but rather describes the page itself should belong in a MetaPage.

General Guidelines

Keep it simple

Not every page needs a MetaPage. Some pages are central to how WikiWorld functions, others are a collection of opinions. The content that seems to be guiding or focusing the efforts of the collective may benefit by having a page that separates the 'how the page should function' from the 'meat and potatoes' of the page itself.


Why bother with MetaPages|?

Help readers transition into users that transition into members.

Make editing key pages more accessible to new members/users

  • The purposes of most pages are self-evident. Some are not so. New users may be too polite to add content to the home page, for example, unless they are certain these additions are welcome to the community as a whole. A MetaHomePage would describe the purpose of the home page along with suggestions for improvements and further encouragements to make the page useful to each user. --DavidSiegel


Violates the WikiSimple principle.

I'll bet you didn'y know that wiki pages already have hidden meta information. I have thought about employing it in ObjectWiki.
I've sort of regretted bad mouthing meta classes. I've grown pessimistic about the value of trying to teach about meta classes, yet we do want to keep information about object behavior somewhat separate from the objects themselves for the sake of clearity. Objects that contain information about other objects are meta classes, if they define object behavior they are classes which are both, Class objects themselves, and meta objects for the instances of the class. In SmallTalk the Class and the MetaClass are separate object instances, but they need not be necessarily. To the user it is rarely an issue.
MetaPage, as soon as I saw it, seemed it sould define the object protocol of the Page object. We do want to declare such a page.
  • That's a good point. In other words we may want to reserve the keyword 'MetaPage' for the purpose of describing the Page object and use something like 'Description' as in HomePageDescription for the purpose of containing the collection of information that describes HomePage? --DavidSiegel
Information "about" an object is meta information. It's values are external to the internal state of the object. A method defines a behavior, the definition is meta information, it's invovation is action of the object.
Meta data can come from many sources. FirstClassObjectsOfTheWeb should provide access to all sources, and dynamically add sources when possible.
When we inquire "about" an object, we are accessing it's meta object.
When we define attributes "about" an object or define it's behavior, we are defining it's meta class.
I used to think I was indecisive, but not I am not so sure.... --JimScarver
Personal tools