Initial commit

site/blueprints/fields/cover.yml

@@ -0,0 +1,9 @@
+# Fields can be defined in their own field blueprints
+# and reused across multiple blueprints
+# This field is used in the album.yml and note.yml blueprints
+# See http://getkirby.com/docs/guide/blueprints/extending-blueprints#reusing-and-extending-single-fields
+type: files
+multiple: false
+query: page.images.template('image')
+uploads:
+  template: image

site/blueprints/files/blocks/image.yml

@@ -0,0 +1,4 @@
+# The blocks/image template is automatically assigned to all uploaded
+# images in the blocks field. We don't really need a separate blueprint
+# for this and can therefor extend the already existing files/image blueprint
+extends: files/image

site/blueprints/files/image.yml

@@ -0,0 +1,47 @@
+# Each file blueprint must have a title, the title may be different from the file name
+title: Image
+
+# Like page blueprints, file blueprints can define a layout with tabs, columns, sections and fields
+# File blueprints define what sort of information should get stored in a file's meta data file
+# In addition to the fields defined in this example blueprint, you can also set what type of file is acceptable
+# when this blueprint is used, which allows you to control what users can upload.
+# More about file blueprints: https://getkirby.com/docs/reference/panel/blueprints/file
+
+accept: 
+  type: image
+
+columns:
+  - width: 1/2
+    sections:
+      content:
+        type: fields
+        fields:
+          caption:
+            label: Caption
+            type: textarea
+            size: medium
+  - width: 1/2
+    sections:
+      meta:
+        type: fields
+        fields:
+          alt:
+            label: Alternative Text
+            type: text
+          photographer:
+            label: Photographer
+            type: text
+            width: 2/3
+          license:
+            label: License
+            type: select
+            width: 1/3
+            options:
+              - Unsplash
+              - CC BY 4.0
+              - CC BY-SA 4.0
+              - CC BY-NC 4.0
+              - CC BY-ND 4.0
+          link:
+            label: Link
+            type: url

site/blueprints/pages/about.yml

@@ -0,0 +1,79 @@
+# Each page blueprint must have a title, the title may be different from the file name
+title: About us
+
+# Each page can have an icon that is shown in page listings when no preview image is available.
+icon: ☎️
+
+# Limit the possible page statuses to `draft` and `listed`.
+# More about page statuses: https://getkirby.com/docs/reference/panel/blueprints/page#statuses
+status:
+  draft: true
+  listed: true
+
+# Page options allow you to control how users can interact with the page.
+# Here we prevent changing the page slug and page deletion
+# More about page options: https://getkirby.com/docs/reference/panel/blueprints/page#options
+options:
+  changeSlug: false
+  delete: false
+
+# We use tabs here to focus on the layout in one tab
+# and have the additional contact fields in a secondary
+# tab. Tabs can really help to clean up the interface
+# when it otherwise gets too complicated
+tabs:
+  content:
+    icon: text
+    label: Content
+    fields:
+      layout:
+        label: Layout
+        type: layout
+        layouts:
+          - "1/1"
+          - "1/2, 1/2"
+          - "1/3, 1/3, 1/3"
+  # The contact tab pre-defines a set of address
+  # fields for the contact box at the bottom of the about
+  # page. Combining modular content from layouts with
+  # pre-defined content from such fields is a great way to
+  # offer flexibility and yet keep certain constraints.
+  #
+  # The form layout is created with two columns,
+  # each column has a set of fields
+  # More about columns:
+  # https://getkirby.com/docs/guide/blueprints/layout#defining-columns
+  contact:
+    icon: map
+    label: Contact
+    columns:
+      - width: 1/2
+        # Kirby has many different field types, from simple text fields to the more complex structure field that contains subfields
+        # All available field types: https://getkirby.com/docs/reference/panel/fields
+        fields:
+          address:
+            label: Address
+            type: writer
+            inline: true
+          email:
+            label: Email
+            type: email
+          phone:
+            label: Phone
+            type: tel
+      - width: 1/2
+        fields:
+          social:
+            label: On the web
+            type: structure
+            columns:
+              platform: true
+            fields:
+              platform:
+                label: Platform
+                type: text
+                width: 1/2
+              url:
+                label: URL
+                type: url
+                width: 1/2

site/blueprints/pages/album.yml

@@ -0,0 +1,54 @@
+# Each page blueprint must have a title, the title may be different from the file name
+title: Album
+
+# Each page can have an icon that is shown in page listings when no preview image is available.
+icon: 🖼
+
+# Page status can be limited, here to `draft` and `listed`.
+# More about page status: https://getkirby.com/docs/reference/panel/blueprints/page#statuses
+status:
+  draft: true
+  listed: true
+
+# Define the form layout with two columns
+# Columns are optional but help structure the form layout
+# The first column defines an files section, the second a set of fields
+# More about different types of sections: https://getkirby.com/docs/reference/panel/sections
+# More about columns: https://getkirby.com/docs/guide/blueprints/layout#defining-columns
+
+columns:
+  - width: 1/3
+    # The first column contains a set of fields to store
+    # information about the album.
+    #
+    # List of all available field types:
+    # https://getkirby.com/docs/reference/panel/fields
+    fields:
+      # If you need the same field in multiple locations, you can define them once and reuse whereever needed.
+      # Here we use a files field defined in `/site/blueprints/field/cover.yml`
+      cover: fields/cover
+      headline:
+        type: text
+        placeholder: "{{ page.title }}"
+        help: Leave empty to use the title as headline
+      subheadline:
+        type: text
+      text:
+        type: writer
+      tags: true
+
+  - width: 2/3
+    sections:
+      # The `images` files section shows all images of
+      # the current page that use the `image` template
+      images:
+        type: files
+        layout: cards
+        template: image
+        info: "{{ file.dimensions }}"
+        image:
+          ratio: 5/4
+          cover: true
+        min: 1
+        size: small
+

site/blueprints/pages/default.yml

@@ -0,0 +1,42 @@
+# Each page blueprint must have a title, the title may be different from the file name
+# This default blueprint is used to display a page in the Panel whenever a custom page blueprint is missing.
+title: Simple Page
+
+# Each page can have an icon that is shown in page listings when no preview image is available.
+icon: 📝
+
+# Custom descriptions of page statuses depending on use case
+# More about page statuses: https://getkirby.com/docs/reference/panel/blueprints/page#statuses
+status:
+  draft: true
+  unlisted:
+    label: Hidden Page
+    text: The page is not listed in the main menu
+  listed:
+    label: Menu Page
+    text: The page is listed in the main menu
+
+# Content area width 2 columns and 3 sections: fields, pages, and files
+# Columns: https://getkirby.com/docs/guide/blueprints/layout#defining-columns
+columns:
+  main:
+    width: 2/3
+    sections:
+      # Fields section: https://getkirby.com/docs/reference/panel/sections/fields
+      fields:
+        type: fields
+        fields:
+          text:
+            type: textarea
+            size: huge
+  sidebar:
+    width: 1/3
+    sections:
+      # Pages section: https://getkirby.com/docs/reference/panel/sections/pages
+      pages:
+        type: pages
+        template: default
+      # Files section: https://getkirby.com/docs/reference/panel/sections/files
+      files:
+        type: files
+

site/blueprints/pages/error.yml

@@ -0,0 +1,9 @@
+# Each page blueprint must have a title, the title may be different from the file name
+title: Error
+
+# Page options allow you to control how users can interact with the page.
+# Here we prevent reading of the page, so it is not shown to anyone in the Panel.
+# If you want to allow users to modify the error page content in the Panel, remove this option.
+# More about page options: https://getkirby.com/docs/reference/panel/blueprints/page#options
+options:
+  read: false

site/blueprints/pages/home.yml

@@ -0,0 +1,34 @@
+# Each page blueprint must have a title, the title may be different from the file name
+title: Home
+
+# Each page can have an icon that is shown in page listings when no preview image is available.
+icon: 🏠
+
+# Page options allow you to control how users can interact with the page.
+# Here we prevent changing the page status (the home page cannot be renamed or deleted by default)
+# More about page options: https://getkirby.com/docs/reference/panel/blueprints/page#options
+options:
+  changeStatus: false
+
+# Here we define an info section and a pages section (`photography`)
+sections:
+  content:
+    type: fields
+    fields:
+      headline:
+        type: text
+        width: 1/2
+      gap:
+        width: 1/2
+      subheadline:
+        type: text
+        width: 1/2
+
+  # The photography section extends a pages section defined in the `/site/blueprints/section/album.yml` blueprint
+  # More about reusing and extending sections: https://getkirby.com/docs/guide/blueprints/extending-blueprints#reusing-and-extending-sectionss
+  photography:
+    label: Photography
+    extends: sections/albums
+    status: listed
+    size: small
+    help: All projects for the homepage are being pulled from the photography page.

site/blueprints/pages/note.yml

@@ -0,0 +1,55 @@
+# Each page blueprint must have a title, the title may be different from the file name
+title: Note
+
+# Sorting number scheme that is applied when page status is changed to `listed`
+# More about page sorting: https://getkirby.com/docs/reference/panel/blueprints/page#sorting
+num: date
+
+# Each page can have an icon that is shown in page listings when no preview image is available.
+icon: 📖
+
+# Custom descriptions for each page status depending on use case
+# More about page status: https://getkirby.com/docs/reference/panel/blueprints/page#statuses
+status:
+  draft:
+    label: Draft
+    text: The note is still in draft mode. It can only be seen by editors with panel access.
+  unlisted:
+    label: In Review
+    text: The note is online and can be visited with the direct URL. The team must still give the final go to publish it.
+  listed:
+    label: Published
+    text: The note is online and listed in the blog
+
+# Define the form layout with two columns
+# Columns are optional but help structure the form layout
+# More about columns: https://getkirby.com/docs/guide/blueprints/layout#defining-columns
+columns:
+  - width: 2/3
+    # This columns only has a single field
+    fields:
+      text:
+        type: blocks
+
+  - width: 1/3
+    # This second column holds a fields section with multiple fields
+    # More about fields sections: https://getkirby.com/docs/reference/panel/sections/fields
+    sections:
+      meta:
+        type: fields
+        fields:
+          # If you need the same field in multiple locations, you can define them once and reuse whereever needed.
+          # Here we use a files field defined in `/site/blueprints/field/cover.yml`
+          cover: fields/cover
+          date:
+            type: date
+            time: true
+            default: now
+          author:
+            type: users
+          # Fields types can be added using the shortcut `fieldname: true`
+          # (however, you can only use a fieldname once per page and this only makes sense for simple fields without configuration)
+          tags: true
+      files:
+        type: files
+        template: blocks/image

site/blueprints/pages/notes.yml

@@ -0,0 +1,35 @@
+# Each page blueprint must have a title, the title may be different from the file name
+title: Notes
+
+# Each page can have an icon that is shown in page listings when no preview image is available.
+icon: 📖
+
+# Define the form layout with two columns
+# More about columns: https://getkirby.com/docs/guide/blueprints/layout#defining-columns
+
+columns:
+  - width: 1/3
+    # In the first column, we reuse the `notes` section
+    # (defined in `/site/blueprints/sections/notes.yml` twice with different page status and headline
+    sections:
+      drafts:
+        extends: sections/notes
+        label: Drafts
+        status: draft
+
+      unlisted:
+        extends: sections/notes
+        label: In Review
+        status: unlisted
+
+  - width: 2/3
+    # In the second column, we reuse the same section, this time for listed pages and with a different headline
+    sections:
+      listed:
+        extends: sections/notes
+        label: Published
+        status: listed
+        size: small
+        layout: cards
+
+# More about pages sections: https://getkirby.com/docs/reference/panel/sections/pages

site/blueprints/pages/photography.yml

@@ -0,0 +1,18 @@
+# Each page blueprint must have a title, the title may be different from the file name
+title: Photos
+
+# Each page can have an icon that is shown in page listings when no preview image is available.
+icon: 🖼
+
+# Here we extend two sections which are defined in `/site/blueprints/sections/albums.yml`
+# They differ in their page status and the headline.
+sections:
+  drafts:
+    extends: sections/albums
+    label: Drafts
+    status: draft
+
+  listed:
+    extends: sections/albums
+    label: Published Albums
+    status: listed

site/blueprints/sections/albums.yml

@@ -0,0 +1,16 @@
+# This section blueprint defines a pages section that can be reused across multiple blueprints
+# or multiple times within the same blueprint, see `/site/blueprints/pages/photography.yml`  and `/site/blueprints/site.yml`
+# Sections can have different layouts and display additional information or a preview image
+# More about pages sections: https://getkirby.com/docs/reference/panel/sections/pages
+type: pages
+label: Photography
+parent: kirby.page("photography")
+size: small
+info: "{{ page.images.count }} image(s)"
+layout: cards
+template: album
+empty: No albums yet
+image:
+  query: page.cover
+  cover: true
+  ratio: 5/4

site/blueprints/sections/notes.yml

@@ -0,0 +1,15 @@
+# This section blueprint defines a pages section that can be reused across multiple blueprints
+# or multiple times within the same blueprint, see `/site/blueprints/pages/notes.yml` and `/site/blueprints/site.yml`
+# Sections can have different layouts and display additional information or a preview image
+# More about pages sections: https://getkirby.com/docs/reference/panel/sections/pages
+type: pages
+label: Notes
+parent: kirby.page("notes")
+info: "{{ page.published }}"
+template: note
+empty: No notes yet
+sortBy: date desc
+image:
+  query: page.cover
+  cover: true
+  ratio: 3/2

site/blueprints/site.yml

@@ -0,0 +1,32 @@
+# The `site.yml` blueprint defines the look of the start page (Dashboard) of the Panel.
+
+# The site blueprint usually provides easy access to all main pages of the site.
+# In this example blueprint, we also show subpages of the `photography` and `notes` pages.
+# More about the site blueprint: https://getkirby.com/docs/reference/panel/blueprints/site
+
+# The layout of this form has two columns:
+columns:
+  # The first column has one section for the subpages of the `photography` page in card layout
+  # It reuses the pages section defined in `/site/blueprints/sections/albums.yml`
+  - width: 1/2
+    sections:
+      albums: sections/albums
+
+  # The second column has two sections, `notes` and `pages`
+  - width: 1/2
+    sections:
+      # The `notes` section reuses the pages section defined in `/site/blueprints/sections/notes.yml`
+      notes: sections/notes
+
+      # The `pages` pages section shows other main pages of the site
+      # Using the `templates` option, we limit which types of pages are shown
+      # Using the `create` option, we limit the type of page that can be created when a new page is created
+      # Note that the `sandbox` page and the `error` page that also exist in the content folder but use different blueprints thus do not show up in the list
+      # Since the error page's blueprint is set to `read: false`, it wouldn't show up here even if you added the error blueprint to the templates list
+      pages:
+        type: pages
+        create: default
+        templates:
+          - about
+          - home
+          - default

site/blueprints/users/default.yml

@@ -0,0 +1,41 @@
+# User blueprints are used to create new user roles, define form fields for each user role and set role permissions.
+# By default, Kirby only has the `admin` role, a user role that is allowed to do anything.
+# The title is required, everything else is optional.
+# The default user blueprint does not define a role, but a standard set of fields
+# available for each defined user role with blueprints that only contain a title.
+# More about users, roles and permissions: https://getkirby.com/docs/guide/users/managing-users
+title: User
+
+columns:
+  - width: 1/2
+    fields:
+      street:
+        label: Street
+        type: text
+      zip:
+        label: ZIP
+        type: text
+        width: 1/4
+      city:
+        label: City
+        type: text
+        width: 3/4
+      country:
+        label: Country
+        type: text
+
+  - width: 1/2
+    fields:
+      website:
+        label: Website
+        type: url
+      fediverse:
+        label: Fediverse URL
+        type: url
+        icon: mastodon
+        placeholder: https://example.com/@username
+      instagram:
+        label: Instagram
+        type: text
+        icon: instagram
+        placeholder: username