html-next/flexi-layouts

Name: flexi-layouts

Owner: HTMLNext

Description: The layouts portion of flexi

Created: 2017-01-11 14:04:10.0

Updated: 2018-05-16 15:54:42.0

Pushed: 2018-05-16 15:54:43.0

Homepage: null

Size: 1617

Language: JavaScript

GitHub Committers

User	Most Recent Commit	# Commits

Other Committers

User	Email	Most Recent Commit	# Commits

README

Flexi

Flexi-layouts is the layouts portion of flexi.

It includes the following concepts:

• Viewport Specific Templates
• Blueprints for generating viewport specific templates or moving existing templates into a layouts structure.
• Layout Service for checking isMobile, isDesktop and other various things

Installation

It is recommended that you manage your flexi addons through the main flexi addon:

r install flexi

This will provide a prompt to install only the addons you want. Flexi will also maintain compatibility between addons.

Alternatively install just this package:

r instal @html-next/flexi-layouts

That's all that required if you're using the classic component layout. If you are using a pod-based structure you will also need to install the shim for ember-app. This is done by modifiying your ember-cli-build.js file. This shim makes ember-cli's template tree able to find the templates for layouts.

EmberApp = require('ember-cli/lib/broccoli/ember-app');
shim = require('@html-next/flexi-layouts/lib/pod-templates-shim');

(EmberApp);

Support, Questions, Collaboration

Join the flexi channel on Slack.

Contributing

• Open an Issue for discussion first if you're unsure a feature/fix is wanted.
• Branch off of develop (default branch)
• Use descriptive branch names (e.g. <type>/<short-description>)
• Use Angular Style Commits
• PR against develop (default branch).

Commmits

Angular Style commit messages have the full form:

pe>(<scope>): <title>

dy>

oter>

But the abbreviated form (below) is acceptable and often preferred.

pe>(<scope>): <title>

Examples:

• chore(deps): bump deps in package.json and bower.json
• docs(component): document the fast-action component

Thanks

A special thanks goes out to @ebryn for the inspiration to pursue a solution for explicit layouts, and IsleofCode for providing the time to built it.