Welcome to the POV-Ray wiki. This site is intended to serve a number of purposes. These include:
- Providing a means to summarize discussions on a variety of topics involving POV-Ray.
- Providing an online copy of the POV-Ray documentation to which users may add comments and possibly even edit.
- Contributing webspace to authors of popular POV-Ray add-ons or tools.
- Encouraging users to develop and add to a POV-Ray knowledgebase and FAQ.
- Possible integration of the 3d links list to allow editing by authorized users.
This wiki is in its initial stages of construction. Not all categories have been created and the final layout is yet to be decided. Making permanent links into content is probably not a good idea at this point.
Editing this Wiki
To discourage spamming, anonymous editing is not permitted. Additionally, even for registered users, some parts of this site will not be editable (primarily this will apply to the top-level portions of the wiki - a.k.a. the 'project' namespace).
If you wish to suggest changes to these areas, please discuss in the 'talk' page associated with the page in question.
Persons with experience with POV-Ray or topics of interest to POV-Ray users (e.g. mathematics, solid modeling, and so forth) who are interested in contributing and maintaining content are welcome to contact us.
All Kinds of Help
All application downloads come with documentation, however you might find these additional resources useful.
- Distribution documentation in html format.
- Printable forms of the distribution docs in a variety of formats.
- The web view of available POV-Ray newsgroups, or perhaps you'd prefer to use a newsreader.
- The POV-TAG (Technical Assistance Group) Questions and Tips page.
- See the links at the top of this page for resources on this Wiki.
To Do List
- At this point, there is no centralized log-in system in use between the main povray.org site, this site, and other related sites such as lib.povray.org. We realize this is undesirable and are looking into whether or not it is sufficiently important for us to devote programming resources into fixing it.