With not much content
\n\t\t`\n\t }\n }\n ```\n\nStageny in its core supports Components and Layouts.\n\n### Layouts\n\nA page's frontmatter `layout: default` points to a specific layout:\n\n`layouts/default.pug`:\n```\nhtml\n\thead\n\t\ttitle #{_meta.title}\n\tbody\n\t\t!= content\n```\n\nA layout too can have frontmatter which will be overruled by the page (except for `layout` which you use to define a super layout).\n\n### Components\n\nComponents must be uniquely named, no matter their file path. Frontmatter serves as default paramters.\n\n`components/Button.pug`:\n```\n---\ntag: button\ncontent: Button\n---\n\n#{tag}.Button(type=(tag === 'button' && tag))!= content\n```\n\n`content` is a special parameter, at least in pug, as the slot will be put into it.\n\n`page.html.pug`:\n```\n+Component('Button')\n\ti.Icon(data-icon=\"plus\")\n\t| Add\n```\n\n`page.html.js`:\n```\nmodule.exports = function(data) {\n\treturn data.component('Button', {\n\t\tcontent: ` Add`\n\t})\n}\n```\n\n\n\n\n## Data\n\nData can be global or on a page level.\n\nData will be applied in this order:\n\n- _page and internal component helper\n- data and _data (if Data Plugin)\n- helpers and _helpers (if Helper Plugin)\n- page frontmatter (also via _page.meta)\n\n\n## Page\n\n- url\n- meta\n- content\n- result\n- render\n- rawMeta\n\n\n\n## Events / Plugins\n\nPlugins (and helpers) can sneak into any of those events:\n\n- init (before first run)\n- on every run:\n\t- start\n\t- sitemap (array of pages)\n\t- for every page:\n\t\t- beforepageprocess (file)\n\t\t- beforepagedata (file, data)\n\t\t- afterpagedata (file, data)\n\t\t- beforepagerender (file)\n\t\t- afterpagerender (file)\n\t\t- afterpagewrite (file)\n\t\t- pageerror (file)\n\t- end\n","readmeFilename":"Readme.md"}