Package maintainers and Hackage trustees are allowed to edit certain bits
of package metadata after a release, without uploading a new tarball.
Note that the tarball itself is never changed, just the metadata that is
stored separately. For more information about metadata revisions, please
refer to the
Hackage Metadata Revisions FAQ.
| No. |
Time |
User |
SHA256 |
| -r1 (markup-3.1.0-r1) |
2015-11-12T01:51:42Z |
athanclark |
afb6565079dbae62dda5e69e61c9ef1d0617558ba6792c3e93f3788f8d05a3ab
|
|
Changed description
from This library tries to simplify deployment of common HTML constructs, for different
HTML engines.
Deployment, from this library's perspective, means /how/ something can be
rendered to markup, yet still achieve the same "result" to the end user (namely
the DOM). For instance, we could use a @<link>@ tag to reference external Css,
or we might insert the Css code /inline/ a @<style>@ tag.
We use simple tags to infer the deployment mechanism for a context of
markup. The three deployment mechanisms provided include
* /inline/ - the asset inserted between markup tags
* /local/ - assets on the current server
* /remote/ - assets referenced with a complete URI
to This library tries to simplify deployment of common HTML constructs, for different
HTML engines.
Deployment, from this library's perspective, means /how/ something can be
rendered to markup, yet still achieve the same "result" to the end user (namely
the DOM). For instance, we could use a @<link>@ tag to reference external Css,
or we might insert the Css code /inline/ a @<style>@ tag.
We use simple tags to infer the deployment mechanism for a context of
markup. The three deployment mechanisms provided include
* /inline/ - the asset inserted between markup tags
* /local/ - assets on the current server
* /remote/ - assets referenced with a complete URI
|
| -r0 (markup-3.1.0-r0) |
2015-11-12T01:36:41Z |
athanclark |
7aaab0fb62f91d6485673eab9576ba703752adec4486bcc81327d42a24492ac2
|
|
|