Basic BMS content structure

[jenbennings]

This is (loosely) based off the structure we've used to date. We originally planned to use separate pages for content however this was put aside due to a combination of short timelines and lean content.

.
├── introduction
│
├── guidelines
│   ├── logos
│   ├── colours
│   ├── typography
│   ├── do’s & don’ts
│   └── etc.
│
└── assets
│   ├── logos
│   ├── fonts
│   ├── images
│   ├── document templates
│   ├── copy
│   └── etc.
│
└── anything else?

[haustraliaer]

An idea I've been thinking about (semi related to this) would be to consider all things "items". While things would be collected in broader categories (views) as you have above - each item would also contain it's own url in which it's detail and history etc could be viewed.

Oddball idea for version control on the server: every asset get's it's own git repo (why not?).

Kind of thinking forward to the product with that stuff though, but worth keeping in mind.