Guide Talk:XEdit

From Step Mods | Change The Game

Discussion[edit source]

Howdy guys. I have a few things I want to discuss before changing so we don't have to go through edit wars or anything like that. Please share your thoughts on these items, be sure to sign your comments with ~~~~. Mator (talk) 13:14, August 6, 2015 (EDT)

Byline[edit source]

The xEdit guide -- by Kesta and the S.T.E.P. Team

It's not right to have a byline on a wiki article. A wiki page is a page that can be edited by anyone. It doesn't make sense to attribute it to any group or person. I wasn't able to find an explicit policy on this on wikipedia but I can assure you that this is never done and conflicts with everything that a wiki stands for. Can we please reconsider having this here and remove it? Mator (talk) 13:14, August 6, 2015 (EDT)

Capitalization in headers[edit source]

In my past wiki experience I often tried capitalizing too many words in headers, and I have noticed this practice is also present in this article. E.g. this header would be === Capitalization in Headers === instead of what it is now. A friend of mine helped me break this habit. A header isn't a title -- only the first word should be capitalized unless the word would normally be capitalized in a sentence. Mator (talk) 13:14, August 6, 2015 (EDT)

Forum threads[edit source]

Is it standard to link forum threads from a STEP wiki page? I'd say that both of those should be on the talk page or put into a "useful links" section on the article. They shouldn't be arbitrarily at the top of the article. Mator (talk) 13:14, August 6, 2015 (EDT)

Breaking things up[edit source]

Do we really want this all to be on one page? It seems to me that this page is extremely large already and will only be getting larger as we add more content. I know I'm questioning a fundamental aspect of how this wiki operates, so this should really be escalated to the proper location for discussion. It's just been my experience that it's easier for users to digest content if it is broken into multiple articles. Yes a linked table of contents is nice, but I could easily see this content broken up into multiple articles. E.g.

  • xEdit - A general overview of what xEdit is, how it has been used by the community, who has been developing it, history of development and use, etc. This article wouldn't have any how-to/guide components.
  • Guide: xEdit Setup - A guide for downloading, installing, and setting up xEdit.
  • Guide: Basic xEdit Usage - A guide pertaining to basic usage of xEdit. This would cover what different parts of the interface do and the Basic Functionalities section.
  • Guide: Advanced xEdit Usage - A guide for advanced usage of xEdit. This would cover the advanced functionalities.
  • Guide: xEdit Scripting - A guide for xEdit scripting.

By breaking things up like this we will enable users to feel less overwhelmed, keep track of separate information in different articles, and allow individual sections to grow more. Mator (talk) 13:14, August 6, 2015 (EDT)