Wiki:Scope: Difference between revisions

From Wiki of ZZT
Jump to navigation Jump to search
(Rewrite/reorganize large chunks of the page)
No edit summary
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
What is this wiki about? ZZT! What precisely is ZZT related? That's the question this page tries to answer.
What is this wiki about? ZZT!
 
What ''precisely'' is ZZT related? That's the question this page tries to answer.


If examples are more your thing, check out the [[Wiki:Requested articles|Requested articles]] page to get a better idea of what this wiki is looking for.
If examples are more your thing, check out the [[Wiki:Requested articles|Requested articles]] page to get a better idea of what this wiki is looking for.
Line 19: Line 21:
*ZZT-related tools that aren't part of ZZT itself
*ZZT-related tools that aren't part of ZZT itself
**Toolkits, external editors, font creation utilities, DOS emulation, etc.
**Toolkits, external editors, font creation utilities, DOS emulation, etc.
**For these topics,
*Specific ZZT techniques and engines
*Specific ZZT techniques and engines
**Potentially an endless topic, so if we cover these, I'd want to stick to stuff that's been named, like the kangaroo effect.
**Could be very useful, but it's a potentially endless topic.
**Maybe stick to stuff that's been named, like the kangaroo effect?
**I don't want to rule out original research, but maybe there should be some notability requirement to prevent a bunch of articles on people's pet engines.
**Maybe focus on general topics? Instead of a ZZT Music Box tutorial, document the concept/techniques to use terrain as rewritable memory.
*ZZT's descendants
*ZZT's descendants
**Super ZZT, Megazeux, maybe other ZZT clones like ZIG?
**Super ZZT, Megazeux, maybe other ZZT clones like ZIG?

Latest revision as of 04:11, 11 January 2021

What is this wiki about? ZZT!

What precisely is ZZT related? That's the question this page tries to answer.

If examples are more your thing, check out the Requested articles page to get a better idea of what this wiki is looking for.

Currently in scope

At this time, articles are welcome on anything that's part of ZZT itself. Examples include (but are not limited to):

  • ZZT's version history
  • File formats and other technical info
  • ZZT-OOP
  • Behavior and bugs
  • The official worlds: Town, Caves, City, Demo, Dungeons, Tour

In general, if it's part of an official ZZT distribution, feel free to make an article about it.

Not in scope right now (maybe later)

There are things that I want this wiki to cover, but the scope isn't 100% nailed down. Please don't create articles on these topics for the time being. I'd rather save these for later, and focus on getting a solid technical foundation first.

  • ZZT-related tools that aren't part of ZZT itself
    • Toolkits, external editors, font creation utilities, DOS emulation, etc.
  • Specific ZZT techniques and engines
    • Could be very useful, but it's a potentially endless topic.
    • Maybe stick to stuff that's been named, like the kangaroo effect?
    • I don't want to rule out original research, but maybe there should be some notability requirement to prevent a bunch of articles on people's pet engines.
    • Maybe focus on general topics? Instead of a ZZT Music Box tutorial, document the concept/techniques to use terrain as rewritable memory.
  • ZZT's descendants
    • Super ZZT, Megazeux, maybe other ZZT clones like ZIG?
  • Published ZZT worlds
    • This one's tricky because there's a huge number of worlds. There may be something worth writing about each one, but it's a huge undertaking. I don't want there to be a bias, e.g., most articles are about worlds from the early 2000s because that's the era that most of us are from, but maybe that's unavoidable and/or not such a bad thing.
  • ZZT community
    • Archives, websites, community gathering places, ZZTers (and greater ZZT/Zeux community?), history and significant events
    • I don't like notability requirements in general (wikis are electronic, no space limitations, etc), but maybe there should be something here.