STEP:Guide-Development Workflow

Step Guide-Developmental Workflow

A high-level overview of Step Modifications' Game Guide development process

by: Step Modifications  | Forum Topic

The Developmental Workflow is the process used for all of the Modding Guide development cycles. Within each workflow section is a Pre-release Checklist that much be completed directly prior to releasing a new Modding Guide version.

NOTE

Notice to Staff
In order for Game Guides to remain relevant, it is imperative that this generalized workflow be maintained by staff, Curators, and community contributors.

This workflow assumes the corresponding Development Guide and Mod List have already been propagated, which are covered in Step 4 and Step 5 of the Mod-Build Guide Framework article.

Wiki Workflow

Guide Propagation

Unless the Modding Guide is new, the Dev version should already exist from previous releases.

1. Ensure the GameName DEV version corresponds to the actual development release version! If this is not set correctly, then the platform will not behave as expected!
   1. Open the Step Portal
   2. Edit Guide Versioning by clicking the Create or edit button

      

   3. Change the GameName DEV number to the current dev release number for the respective Modding Guide. Change NOTHING else at this point!
2. From the Game's Portal, copy new Dev Guide
3. From the Game's Portal, copy new Dev Changelog

   

4. Propagate new a Mod List for the development release by entering the GameName DEV version into the second textbox and click the Propagate button.

   

Mod Pages

1. Create mod pages for all new ACCEPTED mods, if they do not exist
2. Ensure new mod pages are complete with the correct flags and instructions present
3. Ensure mods that were moved to new categories have had their mod category changed on their mod page

Forum Workflow

1. Ensure all new ACCEPTED topics are named correctly: NexusName (by AuthorName)
2. Ensure that all new ACCEPTED topic OPs are formatted with the correct mod topic header

   

3. Ensure the TESTING prefix has been removed from all new ACCEPTED mods

   Mods not accepted can keep their TESTING prefix, if testing is planned to continue for the next release; else, the prefix should be removed.

   1. From the Topic view, tick the box at right of the ACCEPTED topic
   2. Select Unmark for Testing from the menu in the tool pop-up at lower right
4. Ensure all mods that were dropped from a Guide have been prefixed as DROPPED and their ACCEPTED prefix/tags removed

Nexus Workflow

Unless the Modding Guide is new, the Nexus page should already exist.

Release Checklist

Forum Pre-release Checklist

1. Close old Feedback & Bug Reports topic, unpin and lock it
2. Start new Feedback & Bug Reports topic, pin it (edit accordingly to point to new release changelog)
3. Close old Dev topics found with the guide's Administration forum and start new one (edit accordingly to point to new Dev Changelog, pin/unpin accordingly)
4. Post new Release announcement topic in the Announcement forum and pin it
5. Unpin and lock the previous release's announcement topic in the Announcement forum

Wiki Pre-release Checklist

1. Check, double-check, and finalize the Dev Changelog!!!
2. Complete a final edit to Dev Mod List ensuring it matches the Dev Changelog by entering the GameName DEV version in the first textbox and clicking the Edit Existing button

   

Nexus Pre-release Checklist

1. Hide the Nexus page, giving a description that an update is underway
2. Update the Changelog with the appropriate information
3. Upload any new files, replacing the previous ones
4. Edit the Nexus description using the BBCode view and update all current version and changelog version links