One docs page per feature approach (plus structure for docs pages)

[rufuspollock]

would like to propose we have a rough principle of:

"One docs page per feature"

In particular this would mean refactoring https://flowershow.app/docs/syntax to split out the "beyond core markdown" stuff into their own pages.

In addition can also propose a rough structure for docs pages along the lines of

• Intro to the feature: what it is
• How to use it (as a user)
• How to admin it (if relevant)