[/ Comments look like this! /]

[/ Boxup has a few special keywords -- `use` is one of them. 
 / It can be used to tell the compiler which schema to use (although
 / this is an implementation detail)
 /]
[use my.example]

[article]
  title = Hello world!
  slug = hello_world

[section one]
  css = "
    width: 100%;
    background: blue;
  "

  [header]
    Hey World!

  Boxup is a very simple markup language based 
  around square brackets and indentation.

  It has *bold text*, _italic text_ and you 
  can <tag stuff>[example content="This is a tag!"] too.

[/ A possible schema for the above: /]

[/ The `schema` keyword optionally names the schema. /]
[schema my.example]
  [/ You can import other schemas into this one via the `use` block. 
   / Note that `[use]` blocks in schemas must be children of the 
   / `[schema]` block.
   /]
  [use my.paragraph]

[root]
  [child article required = true]
  [child section]
  [child paragraph]

[block article]
  [property title required=true]
  [property slug]

[block section]
  [/ In addition to properties, you can define
   / "parameters" on your blocks. In Boxup, parameters
   / are *positional* rather than *named* properties,
   / which can be handy in some situations.
   /
   / Parameters *must* come before properties in a block header and 
   / they are space-delimited. 
   /
   / Also note that parameters are ALWAYS required (at least for now).
   /]
  [parameter type=String]
  [property css]
  [child header]
  [child paragraph]

[block header]
  [child paragraph required = true]

[schema my.paragraph]

[/ The `[root]` declaration is ignored when being imported. /]
[root]
  [child paragraph]

[/ When used by another schema, all the block definitions here will become
 / available in the parent file. 
 /]
[block paragraph]
  [/ Properties do not need to be defined in the block header: /]
  type = Paragraph
  [child example]

[block example type=Tag]
  [property content]
    required = true