README.md in hanami-assets-2.1.0.rc1 vs README.md in hanami-assets-2.1.0.rc2
- old
+ new
@@ -64,17 +64,17 @@
```erb
<!doctype HTML>
<html>
<head>
<title>Assets example</title>
- <%= assets.css "reset", "app" %>
+ <%= stylesheet_tag "reset", "app" %>
</head>
<body>
<!-- ... -->
- <%= assets.js "app" %>
- <%= assets.js "https://cdn.somethirdparty.script/foo.js", async: true %>
+ <%= javascript_tag "app" %>
+ <%= javascript_tag "https://cdn.somethirdparty.script/foo.js", async: true %>
</body>
</html>
```
It will output this markup:
@@ -96,19 +96,20 @@
</html>
```
### Available Helpers
-This gem ships with the following helpers:
+The `hanami` gem ships with the following helpers for assets:
- * `javascript` (aliased as `js`)
- * `stylesheet` (aliased as `css`)
- * `favicon`
- * `image` (aliased as `img`)
- * `video`
- * `audio`
- * `path`
+ * `asset_url`
+ * `javascript_tag`
+ * `stylesheet_tag`
+ * `favicon_tag`
+ * `image_tag`
+ * `video_tag`
+ * `audio_tag`
+ * `path_tag`
## App Structure
Hanami applications are generated via `hanami new` CLI command.
@@ -151,20 +152,10 @@
#### Destination Directory
The destination directory is `public/assets`.
-### Sources
-
-Hanami Assets works with [Yarn](https://yarnpkg.com/).
-
-In order to add/remove a source to your application, you should follow Yarn's dependencies management.
-
-### Preprocessors
-
-Hanami Assets is able to preprocess any kind of JavaScript and CSS flavor.
-
### Deployment
To process the assets during deployment run `bundle exec hanami assets compile`.
The destination directory will contain the processed assets with an hashed name.
@@ -263,10 +254,10 @@
__Hanami::Assets__ uses [Semantic Versioning 2.0.0](http://semver.org)
## Contributing
-1. Fork it ( https://github.com/hanami/assets/fork )
+1. Fork it (https://github.com/hanami/assets/fork)
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Add some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create new Pull Request