|
|
|
|
Synopsis |
|
|
|
Documentation |
|
|
A custom page.
| Instances | |
|
|
|
:: String | Destination of the page, relative to _site.
| -> [FilePath] | Dependencies of the page.
| -> [(String, Either String (Hakyll String))] | Mapping.
| -> CustomPage | | Create a custom page.
The association list given maps keys to values for substitution. Note
that as value, you can either give a String or a Hakyll String.
A Hakyll String is preferred for more complex data, since it allows
dependency checking. A String is obviously more simple to use in some
cases.
|
|
|
|
:: Renderable a | | => String | Template to render all items with.
| -> FilePath | Renderables in the list.
| -> [a] | Additional context.
| -> [(String, String)] | | -> CustomPage | | A createCustomPage function specialized in creating listings.
This function creates a listing of a certain list of Renderables. Every
item in the list is created by applying the given template to every
renderable. You can also specify additional context to be included in the
CustomPage.
let customPage = createListingWith
"index.html" -- Destination of the page.
"templates/postitem.html" -- Path to template to
-- render the items with.
posts -- ^ Renderables to create the list with.
[("title", "Home")] -- ^ Additional context
|
|
|
|
:: Renderable a | | => ContextManipulation | Destination of the page.
| -> String | Template to render all items with.
| -> FilePath | Renderables in the list.
| -> [a] | Additional context.
| -> [(String, String)] | | -> CustomPage | | A createCustomPage function specialized in creating listings.
In addition to createListing, this function allows you to specify an
extra ContextManipulation for all Renderables given.
|
|
|
|
PagePath is a class that wraps a FilePath. This is used to render Pages
without reading them first through use of caching.
| Instances | |
|
|
|
Create a PagePath from a FilePath.
|
|
data CombinedRenderable a b | Source |
|
A combination of two other renderables.
| Instances | |
|
|
|
Combine two renderables. The url will always be taken from the first
Renderable. Also, if a `$key` is present in both renderables, the
value from the first Renderable will be taken as well.
Since renderables are always more or less key-value maps, you can see
this as a union between two maps.
|
|
|
Combine two renderables and set a custom URL. This behaves like combine,
except that for the url field, the given URL is always chosen.
|
|
Produced by Haddock version 2.6.0 |