Skip to content

Fixed the components 404 to component gems and tags #138

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions en/docs/components.md
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# Components

Apps are made up of Components. Each folder under ```app/``` is a component. Components can also be included from gems. Apps are commonly broken up into multiple components. Components can be anything from a small reusable widget to a large section of the app. Since components can be included in other components, we recommend starting with smaller components and building up larger ones. Components that are likely to be reused can be built as [component gems](docs/component_gems.md), or you can move a component into a gem at a later time.
Apps are made up of Components. Each folder under ```app/``` is a component. Components can also be included from gems. Apps are commonly broken up into multiple components. Components can be anything from a small reusable widget to a large section of the app. Since components can be included in other components, we recommend starting with smaller components and building up larger ones. Components that are likely to be reused can be built as [component gems](component_gems.md), or you can move a component into a gem at a later time.

The code inside of a component can be accessed in a few ways. Model code is accessible from anywhere in the app. Views/controllers can be accessed using tags or view bindings. See [tags](docs/tags.md) for info on how view path lookup works.
The code inside of a component can be accessed in a few ways. Model code is accessible from anywhere in the app. Views/controllers can be accessed using tags or view bindings. See [tags](tags.md) for info on how view path lookup works.

The overall idea of components is to keep more parts of your code isolated so they can be independently tested and abstracted.

Expand Down Expand Up @@ -36,4 +36,3 @@ You can add a new component to an app with:
## Components and Routing

When you visit a route, it loads all of the files in the component on the front end, so new pages within the component can be rendered without a new http request. If a URL is visited that routes to a different component, the request will be loaded as a normal page load and all of that component's files will be loaded. You can think of components as the "reload boundary" between sections of your app. [Note: currently only the "main" component is supported for initial page load, expect "reload boundry" support soon]