# Name of the property. You can have multiple properties with completely
# different config blocks for different sections of your site.
# For example, you can have one property to handle comment submission and
# another one to handle posts.
simulations:
  allowedFields: ["benchmark", "metadata", "data"]
  allowedOrigins: ["localhost", "pages.nist.gov"]
  branch: "master"
  commitMessage: "New simulation: {fields.metadata.simulation_name}"
  filename: "meta"
  format: "yaml"
  moderation: true
  name: "https://pages.nist.gov/chimad-phase-field/"
  path: "_data/simulations/{fields.metadata.simulation_name}"
  requiredFields: ["benchmark", "metadata", "data"]
  generatedFields:
    date:
      type: date
      options:
        format: "timestamp-seconds"

# Name of the property. You can have multiple properties with completely
# different config blocks for different sections of your site.
# For example, you can have one property to handle comment submission and
# another one to handle posts.
simulations:
  allowedFields: ["benchmark", "metadata", "data"]
  allowedOrigins: ["localhost", "pages.nist.gov"]
  branch: "master"
  commitMessage: "New simulation: {options.simulation_name}"
  filename: "meta"
  extension: "yaml"
  format: "yaml"
  moderation: true
  name: "https://pages.nist.gov/chimad-phase-field/"
  path: "_data/simulations/{options.simulation_name}"
  requiredFields: ["benchmark", "metadata", "data"]
  generatedFields:
    date:
      type: date
      options:
        format: "timestamp-seconds"

Use options for sim name rather than fields
Use options for sim name rather than fields

Address #634

Don't need to to store simulation_name in meta.yaml. Only doing so for
the benefit of Staticman and it seems like this can be achieved using
options instead, which aren't added to the meta.yaml. This needs to be
committed to master to test a branch.
