[beam] Metadata/ Document component

[agritheory]

Let's assume these items are required in a single document. We need to know what kind of document it is (header) and three or four configurable facts about it. Examples given in context on the BEAM repo.

[crabinak]

@agritheory Can you send me a few screenshots highlighting the relevant information we would want to include here?

[agritheory]

@crabinak I updated this with a very poor idea of what I mean. Don't worry about the property names, we can switch that around as needed

[crabinak]

@agritheory Let me know if this is heading in the right direction. I have job cards that list the quantity with actions for shipping, receiving, components required and the status of the job.

[agritheory]

@crabinak This looks great. There's some nomenclature we'll change on the way to ERPNext, but yes, this is where we want to be going. I think the "components" section you have there should scroll separately or put another way, this metadata component should stick to the top.

[crabinak]

@agritheory Here is an option where the components are scrollable.

[agritheory]

@crabinak Awesome, let's get it in a PR.

[agritheory]

@crabinak What's the status on this?

[crabinak]

@agritheory I just created a PR adding the design file into stonecrop/beam/design.

[agritheory]

@crabinak Design spec merged, let's turn this into a component with a slot.