Merx provides the most basic sections. You can overwrite them with your own sections and/or use them in your own blueprints.
Sections
order
type: fields
fields:
items:
label: field.items
type: structure
width: 2/3
fields:
key:
label: field.key
type: text
required: true
width: 1/2
id:
label: field.id
type: text
multiple: false
required: true
width: 1/2
quantity:
label: field.quantity
type: number
required: true
width: 1/3
price:
extends: fields/price
required: true
width: 1/3
tax:
label: field.tax
type: number
required: true
width: 1/3
translate: false
infoOrder:
label: field.info
type: info
width: 1/3
text:
en: >
Invoice Number: {{ page.invoiceNumber }}<br>
Sum: {{ page.formattedSum }}<br>
Invoice Date: {{ page.invoiceDate }}<br>
Paid Date: {{ page.paidDate }}<br>
de: >
Rechnungsnummer: {{ page.invoiceNumber }}<br>
Summe: {{ page.formattedSum }}<br>
Rechnungsdatum: {{ page.invoiceDate }}<br>
Bezahldatum: {{ page.paidDate }}<br>
orders
headline: section.headline.orders
type: pages
parent: site.find(kirby.option('ww.merx.ordersPage'))
template: order
sortBy: num desc
text: "#{{ page.invoiceNumber }}"
info: "{{ page.formattedSum }} {{ page.paidDate }}"
payment-method
No such file or directory. (plugins/merx/blueprints/sections/payment-method.yml)