Search results
Jump to navigation
Jump to search
Create the page "Template documentation" on this wiki! See also the search results found.
- {{[[Template:Todo|Todo]]}} — A to-do list template for use in talk pages '''only''' This template adds a todo list to a talk page. It categorises the page into [[:Category:2 KB (231 words) - 10:34, 9 November 2007
- ...ature|Infobox Feature]]}} — A software feature infobox template. [[Category:Template Documentation]]2 KB (235 words) - 13:15, 28 November 2007
- : The zone for the actual documentation of PhpGedView. It contains no prefix, and pages in this namespace are crea ===Template:===3 KB (510 words) - 19:16, 16 May 2010
- == Inclusion of Module Documentation on PGVWiki which is not in SVN == ...a, I'll add it to the template so it's automatically added when you use [[:Template:3rd party code]]. --[[User:Nathanhaigh|Nath]] | [[User talk:Nathan_Watson-H2 KB (311 words) - 13:02, 3 March 2008
- ...trac/sourceforge/wiki/Release%20files%20for%20download SourceForge release documentation] for information on how to create a release on SourceForge ...is to directly edit the website files using SSH. Refer to the sourceforge documentation for information on how to access the website files.6 KB (868 words) - 20:55, 6 June 2010
- ...box Software|Infobox Software]]}} — A software infobox template ...h), not both - select the one which matches the content of the article the template is used in.4 KB (470 words) - 15:57, 9 November 2007
- The top menu items should be taken as a template for placing any other To Do's on the System Design page naming protocols for PGVWiki to ensure consistency in the documentation of the site and to assist in the easy navigation of the site.5 KB (851 words) - 00:23, 29 November 2007
- ...hese pages? The best way to accomplish the header you mention is is via a template inserted into each such page. For example, I have done so at [[Installatio ...ers Guide etc so I see this as being very important if we are to do a good documentation process.4 KB (609 words) - 19:25, 16 May 2010
- ...a nagging desire to find ''at least one'' previous example of a successful documentation and tech support wiki. [[User:Tom Haws|Tom Haws]] 06:44, 24 November 2005 I copied the Wikipedia [[PGV Wiki:Community Portal]] template for us to use for PGVWiki oriented work coordination and discussion. There3 KB (419 words) - 17:57, 3 November 2008
- The headers on the pages are a template { { phpgedview } } ...ave in the wiki. Your changes have moved away from the original namespace documentation we wrote (no problems there) This area needs to be clarified - what names9 KB (1,485 words) - 22:45, 6 February 2009
- /* Infobox template style */ /* Standard talk template style */22 KB (2,611 words) - 00:44, 14 February 2009
- #Primary Purpose: PGVWiki is a high quality documentation site related to phpGedView, that is maintained and updated by the user comm ...thoughtful [http://www.llrx.com/features/librarywikis.htm Using a Wiki for Documentation and Collaborative Authoring] "''the greatest success factors for integ16 KB (2,715 words) - 12:06, 8 November 2007
- ...viduals they are within a certain relationship radius to. See the Privacy Documentation for more information about using the unique privacy options of PhpGedView. ...e by modifying one of the provided themes. The themes are made up of HTML template files and CSS style sheets.8 KB (1,383 words) - 22:37, 21 June 2009
- ...port wiki. I would like to examine it and follow its guiding principles. Documentation/tech support is a little different than an encyclopedia, and I want to incr I copied the Wikipedia [[PGV Wiki:Community Portal]] template for us to use for PGVWiki oriented work coordination and discussion. Ther39 KB (6,320 words) - 01:33, 9 February 2011
