forked from tower-archive/tower
-
Notifications
You must be signed in to change notification settings - Fork 0
documentation
Lance Pollard edited this page Apr 12, 2012
·
1 revision
Tower has two main sets of documentation: The guides help you to learn Tower, and the actual code API for reference.
You can help improve the Tower guides by making them more coherent, adding missing information, correcting factual errors, fixing typos, bringing it up to date with the latest edge Tower.
Tower should also have a development guide that goes through the main structure of Tower, the APIs and how to add functionality while following the existing conventions and design/architecture.
The development guide should be structured according to the folder structure inside lib/tower:
- Application
- Locale
- Client
- Application
- Controller
- Store
- View
- Controller
- Http
- Param
- Route
- Middleware
- Model
- Locale
- Relation
- Scope
- Validator
- Server
- Application
- Command
- Controller
- Generator
- Mailer
- Middleware
- Store
- Store
- Memory
- Support
- Locale
- View
- Form
- Helpers
- Locale