Simplicity always, always, always comes at the price of a deep understanding of the subject matter.
–Raul Sanchez
We have put a lot of efforts to make sure that you can build websites an apps in very simple way. We have done our best to make sure that removed the complexity associated with building websites and apps, to help you focus on content and creating value for your customers.
There are, however, a couple of things that you should know about the builder that will help take advantage of the software.
Core
The builder application and any website or app that is build with the builder, it is built on top of what we call a “Core”. At the time of this writing, the most recent version of the Core is 0.2.0. The first component of the architecture that get initialized is the Core. Any website that you create will inherit this version of the Core. As we continue improving the Core framework, new versions will be released. Websites built in previous versions will not be updated automatically. This allows to continue improving the product and to protect websites that might still require legacy functionality to continue to run. Manual Core updates are available and it is our best interest to maintain backward compatibility up to 3 prior releases.
Wordpress
Every website, including the Builder Application, has a WordPress CMS attached to it. This allows to manage content (text, images, etc.), manage users, and url routes. Every WordPress instance comes with a “appcropolis” theme that carries website specific code. In the case of the Builder Application, its theme extended the functionality to provide not only the specific UI, but the necessary functionality. Similarly, each website uses the appcropolis theme to initialize standard website functionality.
View Types
A view type is one of the Core concepts that allows us to link a view type to a WordPress page type. The Core will automatically determine the view type depending on which WordPress page is loaded when users visit the the website. For example, if a website visitor goes to the home page, the view type is “front-page”, for a blog post the view type is “single”, and for a category page the view type is “category”.
NOTE: To learn more about the WordPress page architecture, please check http://wphierarchy.com/.
Special Pages
In other to link the work that you do to the WordPress instance that is linked to your website project, inside the Builder Application, you must name your pages in a way that will match the view type that you want to target. The name of your pages are also equivalent to the traditional theme pages. Below you can see the supported view types and the corresponding WordPress theme files *.
- 404 → 404.php
- front-page → front-page.php
- blog → blog.php
- cart → **
- checkout → **
- search → search.php
- single → single.php
- single-[blog_post_slug] → **
- category → category.php
- category-[blog_category_slug] → category-some_category.php
- tags → tags.php
- single-product → **
- page → page.php
- product → **
- [any-page-name] → **
NOTE:
* The appcropolis theme does not make use of any traditional theme pages.
** No matching page is standard WordPress theme.