Learn what’s different, and how.
If you are familiar with other frameworks, it will be much better to set your mind free first. Many concepts are quite different to what you are used to, and trying to translate these to the equivalent on other frameworks will just confuse you more. Take a moment to learn the basic and key differences you must bear in mind to switch to Artise. Note that not all of Artise’s features are shown here, but only those which are very different.
MVC to Artise Workflow
We chose dividing file types between code and design, and sub divide them for what they do. Learn how locating problems is easier, how every code is reutilizable, how organization saves time and how building a site is done right.
Design truly separated from Logic
You keep hearing Design is separated from PHP, but how is that better if you still have to learn Logic to design a website? Designers on Artise create and maintain static HTML pages, and that’s it. No logic tokens nor PHP code is added later on. It just works.
Organized from core
Artise's organized structure makes your web application stay always clear and scalable, no matter how big it grows: you can't mess it up. And thanks to Hunter, there is now a new way to debug, without echo nor die.
What Plugins do and don’t
On Artise, Plugins perform tasks only on demand, and handle the information I/O, but never are the whole business logic nor have anything to do with the view. Which is application-specific. Plus, there can be multiple instances of one. Learn how they are supposed to be used.