rwatts3 on master
materialize -> 0.3.4 patch rele… (compare)
rwatts3 on master
materialize -> 0.3.3 (compare)
Greetings, everyone . I know it has been silent for a few weeks. I would like to announce that Scorpius is undergoing a major refactor for the 1.0 release. As the previous incremental updates have been focused on keeping functionality of the previous Orion project, as well as making incremental improvements. I'm happy to say the 1.0 Release will be a fresh implementation , a true implementation of what I originaly invisioned Scorpius to be.
Scorpius 1.0 will be focused as a Headless CMS, with an API backend. This will essentially allow you to build your front end in any language or system you please while leveraging the full power and control of Scorpius.
After vetting through just about every framework there is today, Angular2 , Angular1, Ember, Amber, React, Polymer, Blaze , ... Blaze2 and Vue. I have come to a conclusion that Vue is the most future proof and easy going framework to really take Scorpius to the next level. On that note, Scorpius 1.0 will be refactored and built on top of Vuejs
Hello everyone, So I want to share a major change that will be coming to Scorpius to help better prepare you. Scorpius will be moving to a
Headless CMS Approach . Where you will deploy your schema and the admin panel to your server, and be able to write the entire front end of your application using any technology you choose. It will not be tightly coupled with the framework, but I will be working on a few boilerplate projects to help get you started.
Some front end technologies may include React, Vue, Riot, and even Polymer , from a truly decoupled approach.
nuxt.jsevolved. If you are not familiar with Nuxt, it is the Vue equivalent of Next (react based)
scorpiusjs:accountsthrew an error regarding
The scorpius project will be moving to Gitlab as the future plans of Scorpius will be heading in the direction or building or utilizing Scorpius as a Docker service.
With Gitlab's integrated Docker/Image Registry, the process of building, testing, and releasing new Scorpius features will be more inline.
This shift will also make it much easier for community developers to contribute to the project in a pre-built production environment as well as roll out custom iterations of Scorpius to their own platform.