You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The online version of this documentation is hosted at [https://devdocs.qloapps.com](https://devdocs.qloapps.com/).
4
+
5
+
## Contribution guide
6
+
7
+
Contributions are more than welcome! To start contributing to this documentation, you need to deploy it locally and make the required changes. Here is how to deploy:
8
+
9
+
- Fork this repository.
10
+
11
+
- Clone your fork.
12
+
13
+
- Follow the [Install dependencies](#Install-dependencies) section.
14
+
15
+
Before making a contribution using a pull request make sure:
16
+
17
+
- If adding a new page, its topic has not been covered already.
18
+
19
+
- To use proper terminology as used in this documentation when referring to parts of QloApps.
20
+
21
+
- To use `kebab-case` when adding a new file. For example, `new-file-one.md`, `new-file-two.md` etc.
22
+
23
+
Follow VuePress official guide at [https://vuepress.vuejs.org/guide](https://vuepress.vuejs.org/guide/) for further help.
Contains the default adapter classes providing an interface to interact with Db, entity, hooks used in QloApps, and much more.
52
+
Contains the default adapter classes providing an interface to interact with Db, entity, hooks used in QloApps, and much more.
52
53
53
54
### /admin
54
55
55
-
The admin directory contains the main endpoint to access the Back Office. When accessing this folder with your browser, you will be asked for your employee credentials.
56
-
This directory is renamed automatically when you install it from a ZIP package and access it for the first time.
56
+
The admin directory contains the main endpoint to access back office. When accessing this folder with your browser, you will be asked for your employee credentials.
57
+
This directory is renamed automatically when you install it from a ZIP package and access it for the first time.
57
58
58
59
It contains the following subdirectories:
59
60
60
61
-`/autoupgrade`: scratch directory for the 1-click upgrade module
61
-
-`/backups`: contains database backups generated from the back-office
62
+
-`/backups`: contains database backups generated from the backoffice
62
63
-`/export`: contains data export files
63
-
-`/filemanager`: sources for the back-office file manager
64
+
-`/filemanager`: sources for the backoffice file manager
64
65
-`/import`: contains data import files
65
-
-`/themes`: contains the templates for two back-office themes, default and new-theme
66
+
-`/themes`: contains templates for backoffice theme **default**
66
67
67
68
68
69
### /cache
69
70
70
-
Contains temporary cache files. No longer used by QloApps but kept for backward compatibility.
71
+
Contains temporary cache files.
71
72
72
73
### /classes
73
-
Contains all the legacy classes, including:
74
+
Contains all the classes, including:
74
75
75
76
- Object models
76
77
- Utility classes (like Db, Helper, Tools…)
77
78
- Base controllers (like FrontController, AdminController…)
78
79
79
-
80
80
### /config
81
81
82
82
Contains bootstrapping and configuration files. Unless asked, you should never edit them, as they are directly handled by QloApps’ installer and back office.
83
83
84
84
### /controllers
85
-
It Contains controllers – as in MVC (Model-View-Controller), the software architecture used by QloApps. Each file controls a specific part of QloApps.
85
+
It contains controllers – as in MVC (Model-View-Controller), the software architecture used by QloApps. Each file controls a specific part of QloApps.
86
86
87
-
-`/admin`: contains legacy controllers for the Back Office
88
-
-`/front`: contains controllers for the Front Office
87
+
-`/admin`: contains controllers for the back office
88
+
-`/front`: contains controllers for the front office
89
89
90
90
### /Core
91
-
This folder contains a new architecture design to provide easier modularity to code and unit testing.
91
+
This folder contains a new architecture design to provide easier modularity to code and unit testing.
92
92
93
93
### /css
94
94
This folder used to contain style sheets for jquery plugins, now those files are moved to the /js/jquery directory.
@@ -98,7 +98,7 @@ Contains documentation files, licenses, sample import files, and more.
98
98
99
99
### /download
100
100
101
-
Contains files that can be downloaded by the customers. Files are stored with an md5 filename.
101
+
Contains files that can be downloaded by customers. Files are stored with an md5 filename.
102
102
103
103
### /img
104
104
@@ -109,7 +109,7 @@ Contains all of QloApps’ default images, icons and, picture files – which do
@@ -134,17 +134,17 @@ This is where you can find the jQuery framework.
134
134
Contains all of QloApps localization packs — that is, files that contain local information such as default currencies and languages, tax rules and tax rule groups, states used in each country.
135
135
136
136
### /log
137
-
This directory contains exception logs generated in QloApps
137
+
This directory contains exception logs generated by QloApps.
138
138
139
139
### /mails
140
140
141
-
Contains all HTML and text templates for e-mails sent by QloApps. Every language has its specific folder, where you can manually change the content. QloApps contains a tool to edit your e-mails, located in the back office, in the Localization > translations page.
141
+
Contains all HTML and text templates for e-mails sent by QloApps. Every language has its specific folder, where you can manually change the content. QloApps contains a tool to edit your e-mails, located in the back office, in the **Localization > Translations** page.
142
142
143
143
### /modules
144
-
Contains all of the QloApps modules, each in its folder.
144
+
Contains all of the QloApps modules, each in its own folder.
145
145
146
146
### /override
147
-
This directory contains the overridden classes. The overriding is done through modules or manually to change the behavior of legacy classes without actually changing them.
147
+
This directory contains the overridden classes. The overriding is done through modules or manually to change the behavior of core classes without actually changing them.
148
148
149
149
### /pdf
150
150
@@ -154,17 +154,16 @@ Contains all the template files (.tpl) related to PDF file generation (invoice,
154
154
155
155
It contains all the themes that you have installed. Each theme will be in its specific folder.
156
156
157
-
158
157
### /tools
159
-
This directory contains all the 3rd party library used in QloApps.
158
+
This directory contains all the 3rd party libraries used in QloApps.
160
159
161
160
### /translations
162
161
163
-
Contains zip packages that you downloaded for the translation packs.
162
+
Contains zip packages that you downloaded for translation packs.
164
163
165
164
### /upload
166
-
This directory contains the files uploaded by the customer through the contact page or customizations.
165
+
This directory contains files uploaded by the customer through the contact page or customizations.
Copy file name to clipboardExpand all lines: docs/architecture/technical.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -4,11 +4,11 @@
4
4
-**View End**: HTML, CSS, JS
5
5
-**Language Used**: PHP
6
6
-**Database**: MySQL, XML
7
-
-**Template Engine**: SMARTY
7
+
-**Template Engine**: Smarty
8
8
-**Technology**: JavaQuery, SASS, Bootstrap
9
9
10
10
11
-
## MVC (Model–view–controller)
11
+
## MVC (Model–View–Controller)
12
12
[MVC](https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller) is a software design pattern containing three main logical components.
13
13
14
14
Each of these parts is worked to deal with explicit advancement parts of an application. MVC is one of the most habitually utilized industry-standard web improvement systems to make adaptable and extensible systems.
@@ -23,6 +23,6 @@ The View part is utilized for all the UI logics of the application. For instance
23
23
24
24
### Controller
25
25
26
-
Controllers go about as an interface among Model and View segments to handle all the business logics and approaching solicitations, control data utilizing the Model segment and cooperate with the Views to deliver the last yield.
26
+
Controllers go about as an interface between Model and View segments to handle all the business logics and approaching solicitations, control data utilizing the Model segment and cooperate with the Views to deliver the last yield.
27
27
28
28
For instance, the Customer controller will deal with all the cooperations and contributions from the Customer View and update the database utilizing the Customer Model. A similar controller will be utilized to see the Customer data.
Copy file name to clipboardExpand all lines: docs/contribute/README.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ Again we are using the Github PR system to take the bug fixings.
32
32
33
33
### Optimization
34
34
35
-
If you have an idea to make the system more optimized and you can make the system work better then its time to make a pull request at the QloApps Github repository.
35
+
If you have an idea to make the system more optimized and you can make the system work better then its time to make a pull request at the [QloApps Github repository](https://github.com/webkul/hotelcommerce).
36
36
37
37
The better-written code the better is the software performance.
38
38
@@ -55,7 +55,7 @@ Every release goes through a process of quality analysis before reaching you. Bu
55
55
56
56
So we need you to report any bug you find in the system to our QA Team. Our team will check the bug and find the best possible solution to resolve it.
57
57
58
-
You can report a bug either on our Github repository or on our [Forum](http://forums.qloapps.com/).
58
+
You can report a bug either on our [Github repository](https://github.com/webkul/hotelcommerce) or on our [Forum](http://forums.qloapps.com/).
0 commit comments