Devise Content Management System
WebsiteGithub
Primary version
Primary version
  • Devise Development Documentation
  • Getting Started
    • Requirements
    • Installation
    • Advanced Integration with VueJS
    • Advanced Integration Continued: Suggested CSS Setup
  • Creating content with Devise
    • Pages in Devise
      • Creating our first page
      • Page Versions
    • Slices
      • Slice Configuration
      • Database Powered Slices
    • Fields
      • Field Types and Examples
      • Field Configuration and Defaults
    • Language
    • Creating Sites
  • Vue Integration / Customizing Devise
    • User Permissions
    • Customizing the Login
    • Custom Administration Sections
  • Developers / Contributing
  • License
Powered by GitBook
On this page
  • Defaults
  • Enabler
  • Instructions
  • Editor Label
  1. Creating content with Devise
  2. Fields

Field Configuration and Defaults

Defaults

By setting the default property you provide a value before one has been set (or if it has been set to null).

@section('component')
  <script>
    var component = {
      fields: {
        someImage: {
          type: 'image',
          label: 'The Image'
          default: {
            url: '/imgs/default/image-hero.jpg',
            alt: 'We should do this for SEO reasons Jim'
          }
        }
      }
    }
  </script>
@endsection

Enabler

If you set the enabler property on a field it will add an "enabled" checkbox on the field editor and set it to false by default (Unless you set it's default to true as we do in this example)

@section('template')
  <div v-if="devise.someImage.enabled">
    <img :src="devise.someImage.url" :alt="devise.someImage.alt" class="w-full">
  </div>
@endsection

@section('component')
  <script>
    var component = {
      fields: {
        someImage: {
          type: 'image',
          label: 'The Image',
          enabler: true,
          default: {
            enabled: true
          }
        }
      }
    }
  </script>
@endsection

Instructions

Instructions give a little context to your content manager. It can also serve as some good sudo-documentation at times when you need to remember that image size you cut 3 months ago.

@section('component')
  <script>
    var component = {
      fields: {
        someImage: {
          type: 'image',
          label: 'The Image',
          instructions: 'Ensure this image is suitable for a white background'
        }
      }
    }
  </script>
@endsection

Editor Label

On the editor sidebar it's not very helpful when you see a huge list of slices, often which repeat. To help the user understand where they are it's helpful to provide an editorLabel property to the field that you feel best represents the slice when it's populated. Devise uses the slice name until that field is populated and then replaces it with the contents of that field when the user hydrates that instance. Title fields and even images can serve as great editor labels.

@section('component')
  <script>
    var component = {
      fields: {
        someImage: {
          type: 'text',
          label: 'Title',
          editorLabel: true
        }
      }
    }
  </script>
@endsection
PreviousField Types and ExamplesNextLanguage

Last updated 5 years ago