Jump to content
Sign in to follow this  

Shifting the STEP 3.0 Development Trajectory

Recommended Posts

Aborting Step 3.0 CMS Development
This was a hard decision to make. For the past two years we've been slowly developing a custom CMS/website for STEP v3.0 with Mator. However, slow and unpredictable development progress, lack of core feature development, problems with integrated software and stability --along with feedback from the our beta testers has led us to reevaluate our project trajectory. The fact is that the CMS was an ambitious goal that we had been aiming towards for a long time; however, the current trajectory we've been on simply isn't working out to get us to that goal. Coupled with the fact that the Mod Picker mod analysis service is still in need of refinement (and probably won't be upgraded) and the current low number of staff helping with our project, we've made the decision to abort this integration.


Next steps...
This decision allows us to focus on what we know best and can update relatively quickly under the current paradigm: upgrading the forum and wiki software to support modding of multiple games. As a first measure, the forums will be upgraded on the latest major/minor version trajectories and will also be restructured to support multiple games. In parallel, we'll provide our final release of our STEP LE Guide and continue with soft/partial releases of updated content and continued maturity of our beta STEP SE Guide --supporting LE & SE as two distinct modding platforms. This work will formulate the backbone of future wiki development and multi-game support using fully updated versions of (and revisions to) software that we and this community have always used. This will all include upgraded backend solutions to align with modern webdev and server best practices.



There is one question that we'd like to address for our veteran members...

What about the stability of using the wiki going forward?

We know the wiki has been an issue in the past. The main cause of these issues was a combination of the dated Mediawiki software and the likewise dated server infrastructure that it relied upon. Since that time, we have moved to a far more reliable and scalable server solution. The current platform has been running on these new servers for some time now, less the upgraded backend software and services. This will all be upgraded, and we don't foresee performance bottlenecks of the past being an issue with the latest infrastructure in our revised development environment.



Feel free to discuss and ask any questions below.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Create New...

Important Information

By using this site, you agree to our Terms of Use.