Updateproject - Revision history

Eklektikos: Flagged for deletion

2023-06-29T16:56:02Z

Flagged for deletion

← Older revision		Revision as of 16:56, 29 June 2023
Line 1:		Line 1:
			{{delete\|Redundant page documenting an ancient, long-abandoned project.}}
	=Wiki Update Project=		=Wiki Update Project=
	My short tracking page for the wiki update project. Actual work orders and discussion threads can be found [http://www.avlis.org/viewforum.php?f=394 here], though unauthorized members won't be able to view that link. This wiki page will necessarily lag somewhat behind the development goals we achieve, but it's useful for tracking the project's progress and exposing to the rest of the community what we've accomplished so far.		My short tracking page for the wiki update project. Actual work orders and discussion threads can be found [http://www.avlis.org/viewforum.php?f=394 here], though unauthorized members won't be able to view that link. This wiki page will necessarily lag somewhat behind the development goals we achieve, but it's useful for tracking the project's progress and exposing to the rest of the community what we've accomplished so far.

Spool32: /* Just Look At This Awesome Banana Wiki Page */

2010-09-29T05:25:08Z

Just Look At This Awesome Banana Wiki Page

← Older revision		Revision as of 05:25, 29 September 2010
Line 22:		Line 22:
	*[http://wiki.avlis.org/User:TripleAught TripleAught]		*[http://wiki.avlis.org/User:TripleAught TripleAught]

	==Just Look At This Awesome Banana Wiki Page==		==Just Look At This Awesome Banana Wiki Page.==
	[[Image:BananaWiki.JPG]]		[[Image:BananaWiki.JPG]]


	[http://boingboing.net/2010/09/09/just-look-at-this-aw-14.html Just look at it.]		[http://boingboing.net/2010/09/09/just-look-at-this-aw-14.html Just look at it.]



	==Completed Sections==		==Completed Sections==

Spool32 at 04:40, 29 September 2010

2010-09-29T04:40:56Z

@@ Line 7: / Line 7: @@
 Our goal is to unify and impose some structure on the wiki, reduce duplicate pages, beautify it, recategorize many subjects, and rethink the pathways we take for navigating it. As an iterative process driven by volunteers, it's necessarily going to take some time and happen a little haphazardly but with effort and a good PM we can reduce the work into manageable chunks and digest it bit by bit.
-As we go forward, we'll also be migrating much of the static content on [http://www.avlis.org the Avlis forums] to the wiki. By static, I mean threads (such as the Rules threads) where the community (and often the Team as well) do not comment and the thread of discussion doesn't need to be referenced in order to understand the rule.
+As we go forward, we'll also be migrating much of the static content on [http://www.avlis.org the Avlis forums] to the wiki. By static, I mean threads (such as the Rules threads) where the community (and often the Team as well) does not comment and the thread of discussion doesn't need to be referenced in order to understand the entry.
 ==Participants==

Spool32 at 03:55, 29 September 2010

2010-09-29T03:55:30Z

← Older revision		Revision as of 03:55, 29 September 2010
Line 1:		Line 1:
	=Wiki Update Project=		=Wiki Update Project=
	My short tracking page for the wiki update project. Actual work orders and discussion can be found [http://www.avlis.org/viewforum.php?f=394 here], though unauthorized members won't be able to view that link. This wiki page will necessarily lag somewhat behind the development goals we achieve, but it's useful for tracking the project's progress and exposing to the rest of the community what we've accomplished so far.		My short tracking page for the wiki update project. Actual work orders and discussion threads can be found [http://www.avlis.org/viewforum.php?f=394 here], though unauthorized members won't be able to view that link. This wiki page will necessarily lag somewhat behind the development goals we achieve, but it's useful for tracking the project's progress and exposing to the rest of the community what we've accomplished so far.
			__TOC__
			==Goals==
			That we have a wiki with the content it contains is remarkable in itself! Few other worlds in the NWN community have attempted this, and none on the scale of Avlis. Unfortunately, in its current form the wiki is a shambles. There's no graphic convention, no structure, navigation is horrid, we've made poor decisions in how we organize our information and the info we do have is sometimes hard to find, it's page titles make many important sections unsearchable (try searching for the login ports!), and it's generally chaotic.

			Our goal is to unify and impose some structure on the wiki, reduce duplicate pages, beautify it, recategorize many subjects, and rethink the pathways we take for navigating it. As an iterative process driven by volunteers, it's necessarily going to take some time and happen a little haphazardly but with effort and a good PM we can reduce the work into manageable chunks and digest it bit by bit.

			As we go forward, we'll also be migrating much of the static content on [http://www.avlis.org the Avlis forums] to the wiki. By static, I mean threads (such as the Rules threads) where the community (and often the Team as well) do not comment and the thread of discussion doesn't need to be referenced in order to understand the rule.
			==Participants==

Spool32: New page: =Wiki Update Project= My short tracking page for the wiki update project. Actual work orders and discussion can be found [http://www.avlis.org/viewforum.php?f=394 here], though unauthorize...

2010-09-29T03:31:08Z

New page: =Wiki Update Project= My short tracking page for the wiki update project. Actual work orders and discussion can be found [http://www.avlis.org/viewforum.php?f=394 here], though unauthorize...

New page

=Wiki Update Project=
My short tracking page for the wiki update project. Actual work orders and discussion can be found [http://www.avlis.org/viewforum.php?f=394 here], though unauthorized members won't be able to view that link. This wiki page will necessarily lag somewhat behind the development goals we achieve, but it's useful for tracking the project's progress and exposing to the rest of the community what we've accomplished so far.