The page object represents a page on the site. The following fields are available in it:
content — raw page content in markdownhtml — after processing, text rendered into html (available only in templates).meta — page metadata (see below)file — an object, representing a file. Important field — file.path contains the path to the page, generated from the file on the site.permalink — link to the page on the site, like the file.path, but for paginated content contains link to first page.virtual — true for virtual pagesindex — true if the page is an index.md file or any of its subpageslist — field is defined if the main content of the page is a list. For tag pages, this field contains a list of pages marked with the tag.page_count — after pagination — the number of subpagespage_links — list of links to subpagespage_number — current subpage number, numbering starts from 1list_page — the part of the paginated list that should be displayed on the current subpagelocal_data — if the page was generated from data — the data of this pageAny additional fields can be specified in the metadata, for example, page or group identifiers.
Here is a list of fields that are used (reserved) by Mukha:
title — title, mandatory fielddate — date, entered in the format YYYY.MM.DD HH:SS, replaced with a Date objecttags — list of tags separated by commas, converted into a list of tag pages.image — image for the page, if not defined, Mukha will try to find the first image in the textexcerpt — excerpt, if not defined, it may be filled with the first paragraph of the textdraft — if true, the file is skipped during processingkeywords — additional keywords for embedded search, optional