File: views/layout.ejs

Recommend this page to a friend!
  Classes of Alien Fernandez   Seed Sails Angular   views/layout.ejs   Download  
File: views/layout.ejs
Role: Auxiliary data
Content type: text/plain
Description: Auxiliary data
Class: Seed Sails Angular
Full stack framework based on Sails, Node, Angular
Author: By
Last change: Update of views/layout.ejs
Date: 2 years ago
Size: 2,334 bytes


Class file image Download
<!DOCTYPE html> <html> <head> <title><%= typeof title == 'undefined' ? 'New Sails App' : title %></title> <!-- Viewport mobile tag for sensible mobile support --> <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1"> <!--STYLES--> <link rel="stylesheet" href="/styles/importer.css"> <!--STYLES END--> </head> <body ng-cloak> <%- body %> <!-- Client-side Templates ======================== HTML templates are important prerequisites of modern, rich client applications. To work their magic, frameworks like Backbone, Angular, Ember, and Knockout require that you load these templates client-side. By default, your Gruntfile is configured to automatically load and precompile client-side JST templates in your `assets/templates` folder, then include them here automatically (between TEMPLATES and TEMPLATES END). To customize this behavior to fit your needs, just edit `tasks/pipeline.js`. For example, here are a few things you could do: + Import templates from other directories + Use a different template engine (handlebars, jade, dust, etc.) + Internationalize your client-side templates using a server-side stringfile before they're served. --> <!--TEMPLATES--> <!--TEMPLATES END--> <!-- Client-side Javascript ======================== You can always bring in JS files manually with `script` tags, or asynchronously on the client using a solution like AMD (RequireJS). Or, if you like, you can take advantage of Sails' conventional asset pipeline (boilerplate Gruntfile). By default, files in your `assets/js` folder are included here automatically (between SCRIPTS and SCRIPTS END). Both JavaScript (.js) and CoffeeScript (.coffee) are supported. In production, your scripts will be minified and concatenated into a single file. To customize any part of the built-in behavior, just edit `tasks/pipeline.js`. For example, here are a few things you could do: + Change the order of your scripts + Import scripts from other directories + Use a different preprocessor, like TypeScript --> <!--SCRIPTS--> <script src="/js/dependencies/"></script> <script src="/js/define/highlight-js.js"></script> <!--SCRIPTS END--> </body> </html>