docs: change directory notation

This commit is contained in:
kenjis 2022-05-25 16:08:46 +09:00
parent 2cebaaf954
commit 95e5a6a916
No known key found for this signature in database
GPG Key ID: BD254878922AF198
2 changed files with 14 additions and 14 deletions

View File

@ -28,7 +28,7 @@ the data storage.
At their most basic, controllers and models are simply classes that have a specific job. They are not the only class
types that you can use, obviously, but they make up the core of how this framework is designed to be used. They even
have designated directories in the **/app** directory for their storage, though you're free to store them
have designated directories in the **app** directory for their storage, though you're free to store them
wherever you desire, as long as they are properly namespaced. We will discuss that in more detail below.
Let's take a closer look at each of these three main components.

View File

@ -12,8 +12,8 @@ can change to meet the needs of your application.
Default Directories
*******************
A fresh install has five directories: ``/app``, ``/public``,
``/writable``, ``/tests`` and ``/system`` or ``/vendor``.
A fresh install has five directories: ``app/``, ``public/``,
``writable/``, ``tests/`` and ``vendor/`` or ``system/``.
Each of these directories has a very specific part to play.
app
@ -24,17 +24,17 @@ structure that works well for many applications. The following folders make up t
.. code-block:: none
/app
/Config Stores the configuration files
/Controllers Controllers determine the program flow
/Database Stores the database migrations and seeds files
/Filters Stores filter classes that can run before and after controller
/Helpers Helpers store collections of standalone functions
/Language Multiple language support reads the language strings from here
/Libraries Useful classes that don't fit in another category
/Models Models work with the database to represent the business entities.
/ThirdParty ThirdParty libraries that can be used in application
/Views Views make up the HTML that is displayed to the client.
app/
Config/ Stores the configuration files
Controllers/ Controllers determine the program flow
Database/ Stores the database migrations and seeds files
Filters/ Stores filter classes that can run before and after controller
Helpers/ Helpers store collections of standalone functions
Language/ Multiple language support reads the language strings from here
Libraries/ Useful classes that don't fit in another category
Models/ Models work with the database to represent the business entities
ThirdParty/ ThirdParty libraries that can be used in application
Views/ Views make up the HTML that is displayed to the client
Because the ``app`` directory is already namespaced, you should feel free to modify the structure
of this directory to suit your application's needs. For example, you might decide to start using the Repository