This page has been archived. The contents have been moved from another page for reference purposes only, and should be preserved in their current form. Any additions you make will probably not be read and may be undone without notice.
|Please sign all edits with your signature by typing four tildes (e.g., ~~~~)|
With the release of STEP v2.2.9, STEP will shift it's focus to our new paradigm outlined out the STEP:Mandate page for STEP v2.3.0 and beyond. This also means STEP:Extended will be shifted from the main STEP:Guide to a Pack and will be the Official STEP Pack. What is a Pack? Well to quote the Mandate:
One of the primary reasons for keeping STEP:Core pretty strict with regards to vanilla is that the overarching STEP project intends to evolve into a more community-driven initiative of mod 'recipes' constructed as extensions of a central core recipe (aka, STEP:Core). These mod recipes are simply extensible build instructions that we have been referring to as STEP 'Packs'. These packs are themselves extensions of STEP:Core that build on it in ways that express or support different visions of the game. ...
STEP Packs are where the substantive deviations from vanilla Skyrim can and will occur, depending on the vision of any given pack author. Some of the packs may be focused on gameplay changes, others on further graphic enhancements, but together they will allow users more flexibility and choice when determining their modded Skyrim experience. The real beauty of this paradigm is that ANY STEP member will be able to author their own STEP Pack and host their guide on the STEP wiki. Think of it as a 'Nexus' of mod-recipe add-ons that will serve to expand on the ideas of the Steam Workshop, the Nexus, TES Alliance, Planet Elder Scrolls, etc. as a "mod-setup-creation infrastructure" using a common set of development tools to derive a limitless expanse of potential outcomes, each with its own support infrastructure (e.g., forum threads, wiki resources, custom tools, etc.). ...
STEP:Core will provide a common, front-end Guide to modding Skyrim and articulate (via the Semantic Mediawiki infrastructure) with the community-authored Pack guides. The build interface will allow modders to assemble mod compilations complete with detailed instructions specific to mods, mod compatibility patches, Packs and Pack-compatibility solutions as well as a whole host of other relevant attributes, flags and tags for describing Packs and mods. This will be accomplished using forms on the wiki, and the result will be dynamically-created mod lists and Pack Guides that will "snap" together over STEP:Core. The result will be a series of (hopefully seamless) unique instructions for creating the particular build desired by the end user.
You can see a list of example Packs created by users here. Some are using the in-place infrastructure which we're considering to be a Beta format and some are simply using a normal Wiki page. Our goal is to have all Packs using the infrastructure that the Wiki Devs have put their hard work into; however, we need help from the community and that's where you come in!
The infrastructure is still in a Beta state; however, is working for simple Pack creation and should be mostly, if not completely, bug free. We need you, the community, to help improve this infrastructure by using it and providing feedback on its use. Even if you don't play on creating a Pack, you can use it to create a "dummy pack" for testing purposes and these "dummy packs" can be removed later. We're looking for all and any feedback! Everything from feature suggestions to changes and/or improvements on existing features and its use will be helpful. Even if there are Core mods that you think would be best shifted to Extended, we want to hear about it! If you're interesting in testing this out, please contact a Staff member to be added to the Pack Author group on the wiki.
If you know your stuff with Wiki Development and are interested in becoming part of that team, please let us know! We're always looking for new members that can work in this area. Keep in mind the wiki uses https://semantic-mediawiki.org/ .
Feature Ideas, Suggestions and Improvements
- Ability to use a custom CSS file via the forms as well as a default one if no custom CSS is provided
- Add Pack Author group to forums with or without a badge
- Tabs to the form on the Mod Pages which users can access to for adding general and Pack information. See discussion starting here.
- See this post for Nearox's well rewritten ideas for mod tables, ToC and more.
- Feature Ideas
- Multiple Layouts
- Mod Pages
- Features Implemented
I've always been curious if the text field in the short description could become something with a button that would open it up if there was lots of text there. It would be used for displaying larger install instructions, but would not take up space since the button would function as show/hide feature. Seems like it would solve an aesthetics problem, for packs and the STEP Guide.EssArrBee (talk) 17:33, August 19, 2014 (EDT)
Do we want to create more than one kind of Pack layout, or standardize a single one? DoubleYou (talk) 19:47, August 17, 2014 (EDT)
Perhaps by adding enough options in the form/template, we can stick with one, but yet have multiple possibilities.DoubleYou (talk) 06:53, August 18, 2014 (EDT)
Currently there are four tabs for a mod page form. We might benefit from adding one or two. One could be for pack authors' (restricted to that user group) and the other could just be a general page info text field (no restrictions) that displays below the STEP stuff, like the flags and install instructions. This opens up mod pages for S&T info, FAQs, special install instructions for differing mod setups, full descriptions, and anything users want to put on it.EssArrBee (talk) 17:30, August 19, 2014 (EDT)