| CARVIEW |
Getting Started
The Fundamentals
- Control Panel
- Templates
- Channels
- Fieldtypes
- Member Management
- Comments
Advanced Usage
- Add-Ons
- Add-On Development
- The addon.setup.php File
- Add-on Installer
- Plugins
- Modules
- Extensions
- Extension Hooks
- Global
- API Libraries
- Control Panel
- Models
- CategoryField Model
- CategoryGroup Model
- Category Model
- Channel Model
- Channel Entry Model
- ChannelFieldGroup Model
- ChannelField Model
- ChannelFormSettings Model
- ChannelLayout Model
- Comment Model
- File Model
- Fluid Field Library
- GlobalVariable Model
- MemberField Model
- Member Model
- Role Model
- Site Model
- Snippet Model
- SpecialityTemplate Model
- Status Model
- TemplateGroup Model
- TemplateRoute Model
- Template Model
- Modules
- Fieldtypes
- Jump Menu
- Architecture
- Services
- Addon Service
- CP/Alert Service
- Config Service
- Consent Service
- Cookie
- CSV Library
- Encrypt Service
- Event Service
- CP/FilePicker Service
- CP/Filter Service
- Format Service
- IP Address Service
- LivePreview Service
- Memory Service
- CP/Modal Service
- Model Service
- Cp/Form Service
- CP/Pagination Service
- Permission Service
- CP/Sidebar Service
- Spam Service
- CP/Table Service
- CP/URL Service
- Validation Service
- View Service
- Tree Datastructure
- Models
- Working with Models
- Action Model
- Channel Entry Model
- Channel Field Group Model
- Channel Field Model
- CP Log Model
- Developer Log Model
- Email Console Log Model
- File Model
- Fluid Field Model
- Member Model
- MemberField Model
- Role Model
- RoleGroup Model
- Status Model
- RoleSettings Model
- Template Model
- Template Group Model
- Upload Destinations Model
- Shared Form View
- Control Panel Javascript
- Constants Reference
- Cypress Tests
- JSON Version Feed
- Legacy Reference
- Common Functions
- Controllers
- Drivers
- Libraries
- Creating Libraries
- Benchmarking Class
- Cache Class
- Config Class
- CP Class
- Database Class
- Email Class
- File Uploading Class
- Form Validation Class
- Functions Class
- Image Manipulation Class
- Input Class
- Javascript Class
- Language Class
- Layout Class
- Loader Class
- Localize Class
- Logger Class
- Mime Type Class
- Output Class
- Pagination Class
- RSS Parser Class
- Security Class
- Session Class
- Table Class
- Template Class
- Typography Class
- URI Class
- XML Parser Class
- Database Driver
- Helpers
- Legacy API Library
- Guidelines
- v3 Add-on Migration
- v4 Add-on Migration
- v6 Add-on Migration
- Automated Upgrading
- Command Line Interface (CLI)
- ExpressionEngine Pro
- Multiple Sites
Best Practices
Community
The Big Picture
Channels
ExpressionEngine stores your content inside Channels. A channel is simply a container that holds information. This information might be the text of an article or blog post, or it could be an image, or some other type of information. Channel information exists independently from the pages your visitors see.
Important Concept: A channel is just data. There is no assumed association between this data and any particular page of your site.
In your control panel, Channels are managed and configured in the Channel Manager. ExpressionEngine supports a wide variety of Field Types, so that the information in each of your channels can be stored appropriately for that data type.
For example, you might need a “staff” page with employee biographies. To manage this you could create a channel with fields for the name, biography, an image, and any other relevant info.
Content is added to a channel by clicking the Entries link in the main control panel navigation and selecting the entry you wish to edit.
Jump Menu: Don’t forget to use the Jump Menu for quicker navigation. CMD/CTRL + J , then start typing “Edit Entry …”
Templates
In ExpressionEngine, a page (or a page component such as a header or footer) is called a Template.
The simplest way to think of a Template is as a container that represents a single page of your site. As such, a Template may contain anything that a webpage might contain: HTML, JavaScript, etc. A Template can also be a smaller component of your page. Through the use of the Embed Tag you can insert a Template into another Template. This allows you to reuse components such as headers or footers.
In addition to HTML and other markup, Templates will usually contain ExpressionEngine Tags. These Tags allow you to pull data from your channels (or from any other module, plugin, or add-on) and display it in a template.
Templates are organized into Template Groups. A Template Group is analogous to a folder on your server.
URL Structure
In ExpressionEngine, a URL will always contain the following structure, which allows a Template Group and a specific Template to be shown:
https://example.com/template_group/templateRead URL Structure for an in-depth look at URLs.
Summary
- A Channel consists of “information”–your articles, comments, preferences, and other related “data.”
- A Template represents a single page or a smaller section of your site.
- A Template Group contains a collection of Templates.
- ExpressionEngine Tags permit you to show data from a Channel, or any other Module or add-on, in your Templates.
Tip: Check out our 10 Minute Primer to get you started fast.
ExpressionEngine 6 Docs
©2002–2024 Packet Tide,LLC.
Edit this page