This guide contains reference information for creating business applications using the platform, while does not explain framework documentation. If you are already familiar with it, read the following chapters, otherwise, recommend reading the “Laravel” documentation from beginning to end on laravel.com.
To suggest improvements to this tutorial, create a new issue. If you have questions or find a documentation error, please show the chapter and accompanying the text to show an error.
ORCHID is a tool of sped up development open source (MIT license), to create applications in the style of administration. It abstracts common business application templates so that developers can easily implement beautiful and elegant interfaces with little effort.
- Form Builder – no need to describe HTML fields of the same type every time.
- Screens – a good balance between CRUD generation and manual writing.
- Fields – over 40 types.
- Permissions – offers convenient management in development and support.
- Menus, graphics, settings, notifications, etc.
Delivered as a Laravel package and interacted with other components. It can act as a basis for back-office based applications, administration panels, or as a content management system.
A classic web application is a subsystem with a common three-tier architecture, which comprises:
Presentation level – a graphical interface presented to the user (browser), including scripts, styles, and other resources.
The level of applied logic – in our cases, this framework is the link where most business logic concentrated, work with the database (Eloquent), sending resources and various processing.
Level of resource management – provides we implement data storage using database management systems (MySQL, PostgreSQL, Microsoft SQL Server, SQLite).
Reducing development time directly related to the distribution of responsibilities between each of the levels. This is especially noticeable when it is necessary to create auxiliary code, while it takes most of the really useful work over by the application layer.
As various examples of opposing duties can be cited:
- Generation of
Bladetemplate engine or the
- Using ORM or stored procedures.
Depending on the choice of decisions, responsibilities will be allocated, where each decision has both advantages and disadvantages.
In the same way, the platform endows the application layer with new responsibilities for managing the mapping and bridging of data.
Classic | Orchid ├── Route | ├── Route ├── Model | ├── Model ├── Controller | └── Screen └── View | ├── HTML | ├── CSS | └── JS |