mirror of
https://github.com/marko-js/marko.git
synced 2025-12-08 19:26:05 +00:00
Merge branch 'master' of https://github.com/tindli/marko
This commit is contained in:
Patrick Steele-Idem
commit
b1d340ef57
60
README.md
60
README.md
@ -173,7 +173,7 @@ app.get('/profile', function(req, res) {
|
||||
- [Scanning for Tags](#scanning-for-tags)
|
||||
- [Nested Tags](#nested-tags)
|
||||
- [Taglib Discovery](#taglib-discovery)
|
||||
- [FAQ](#faq)
|
||||
- [Frequently Asked Questions (FAQ)](#frequently-asked-questions-faq)
|
||||
- [Additional Resources](#additional-resources)
|
||||
- [Further Reading](#further-reading)
|
||||
- [Screencasts](#screencasts)
|
||||
@ -1904,63 +1904,9 @@ As an example, given a template at path `/my-project/src/pages/login/template.ma
|
||||
7. `/my-project/marko-taglib.json`
|
||||
8. `/my-project/node_modules/*/marko-taglib.json`
|
||||
|
||||
# FAQ
|
||||
# Frequently Asked Questions (FAQ)
|
||||
|
||||
__Question:__ _Is Marko ready for production use?_
|
||||
|
||||
__Answer__: Yes, Marko has been battle-tested at [eBay](http://www.ebay.com/) and other companies for well over a year and has been designed with high performance, scalability, security and stability in mind.
|
||||
|
||||
<hr>
|
||||
|
||||
__Question:__ _Can templates be compiled on the client?_
|
||||
|
||||
__Answer__: Possibly, but it is not recommended and it will likely not work in older browsers. The compiler is optimized to produce small, high performance compiled templates, but the compiler itself is not small and it comes bundled with some heavyweight modules such as a [JavaScript HTML parser](https://github.com/fb55/htmlparser2). In short, always compile your templates on the server. [Lasso.js](https://github.com/lasso-js/lasso) is recommended for including compiled templates as part of a web page.
|
||||
|
||||
<hr>
|
||||
|
||||
__Question:__ _Which web browsers are supported?_
|
||||
|
||||
__Answer__: The runtime for template rendering is supported in all web browsers. If you find an issue please report a bug.
|
||||
|
||||
<hr>
|
||||
|
||||
__Question:__ _How can Marko be used with Express?_
|
||||
|
||||
__Answer__: The recommended way to use Marko with Express is to bypass the Express view engine and instead have Marko render directly to the response stream as shown in the following code:
|
||||
|
||||
```javascript
|
||||
var template = require('./template.marko');
|
||||
|
||||
app.get('/profile', function(req, res) {
|
||||
template
|
||||
.render({
|
||||
name: 'Frank'
|
||||
}, res);
|
||||
});
|
||||
```
|
||||
|
||||
With this approach, you can benefit from streaming and there is no middleman (less complexity).
|
||||
|
||||
Alternatively, you can use the streaming API to produce an intermediate stream that can then be piped to the response stream as shown below:
|
||||
|
||||
```javascript
|
||||
var template = require('./template.marko');
|
||||
|
||||
app.get('/profile', function(req, res) {
|
||||
template.stream({
|
||||
name: 'Frank'
|
||||
})
|
||||
.pipe(res);
|
||||
});
|
||||
```
|
||||
|
||||
<hr>
|
||||
|
||||
__Question:__ _What is the recommended directory structure for templates and "partials"_
|
||||
|
||||
__Answer__: Your templates should be organized just like all other JavaScript modules. You should put your templates right next to the code that refers to them. That is, do not create a separate "templates" directory. For a sample Express app that uses Marko, please see [marko-express](https://github.com/marko-js-samples/marko-express).
|
||||
|
||||
<hr>
|
||||
Please see [FAQ](docs/faq.md).
|
||||
|
||||
# Additional Resources
|
||||
|
||||
|
||||
62
docs/faq.md
Normal file
62
docs/faq.md
Normal file
@ -0,0 +1,62 @@
|
||||
FAQ - Marko
|
||||
===================
|
||||
|
||||
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
|
||||
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
|
||||
|
||||
- [Questions](#questions)
|
||||
- [Is Marko ready for production use?](#is-marko-ready-for-production-use)
|
||||
- [Can templates be compiled on the client?](#can-templates-be-compiled-on-the-client)
|
||||
- [Which web browsers are supported?](#which-web-browsers-are-supported)
|
||||
- [How can Marko be used with Express?](#how-can-marko-be-used-with-express)
|
||||
- [What is the recommended directory structure for templates and "partials"?](#what-is-the-recommended-directory-structure-for-templates-and-partials)
|
||||
|
||||
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
|
||||
|
||||
# Questions
|
||||
|
||||
## Is Marko ready for production use?
|
||||
|
||||
Yes, Marko has been battle-tested at [eBay](http://www.ebay.com/) and other companies for well over a year and has been designed with high performance, scalability, security and stability in mind.
|
||||
|
||||
## Can templates be compiled on the client?
|
||||
|
||||
Possibly, but it is not recommended and it will likely not work in older browsers. The compiler is optimized to produce small, high performance compiled templates, but the compiler itself is not small and it comes bundled with some heavyweight modules such as a [JavaScript HTML parser](https://github.com/fb55/htmlparser2). In short, always compile your templates on the server. [Lasso.js](https://github.com/lasso-js/lasso) is recommended for including compiled templates as part of a web page.
|
||||
|
||||
## Which web browsers are supported?
|
||||
|
||||
The runtime for template rendering is supported in all web browsers. If you find an issue please report a bug.
|
||||
|
||||
## How can Marko be used with Express?
|
||||
|
||||
The recommended way to use Marko with Express is to bypass the Express view engine and instead have Marko render directly to the response stream as shown in the following code:
|
||||
|
||||
```javascript
|
||||
var template = require('./template.marko');
|
||||
|
||||
app.get('/profile', function(req, res) {
|
||||
template
|
||||
.render({
|
||||
name: 'Frank'
|
||||
}, res);
|
||||
});
|
||||
```
|
||||
|
||||
With this approach, you can benefit from streaming and there is no middleman (less complexity).
|
||||
|
||||
Alternatively, you can use the streaming API to produce an intermediate stream that can then be piped to the response stream as shown below:
|
||||
|
||||
```javascript
|
||||
var template = require('./template.marko');
|
||||
|
||||
app.get('/profile', function(req, res) {
|
||||
template.stream({
|
||||
name: 'Frank'
|
||||
})
|
||||
.pipe(res);
|
||||
});
|
||||
```
|
||||
|
||||
## What is the recommended directory structure for templates and "partials"?
|
||||
|
||||
Your templates should be organized just like all other JavaScript modules. You should put your templates right next to the code that refers to them. That is, do not create a separate "templates" directory. For a sample Express app that uses Marko, please see [marko-express](https://github.com/marko-js-samples/marko-express).
|
||||
Loading…
x
Reference in New Issue
Block a user