Sep 24, 2020
Sep 24, 2020
Sep 24, 2020
This video features one of the first real FF&E workflows built in Layer by an early user, Louise Cupac from Plusparts LTD. Louise was also our first customer outside the US.
She walks through how she used categories, elements, and fields to track product data across a large project using one of the earliest versions of Layer. While the core structure is still familiar, the platform shown here doesn’t include features like templates, shared views, or document reports.
We’re keeping this available as part of the Layer v1 archive to show how users were already solving real problems in the early days of the product.
For current workflows and tools, visit layer.team/4.
This video features one of the first real FF&E workflows built in Layer by an early user, Louise Cupac from Plusparts LTD. Louise was also our first customer outside the US.
She walks through how she used categories, elements, and fields to track product data across a large project using one of the earliest versions of Layer. While the core structure is still familiar, the platform shown here doesn’t include features like templates, shared views, or document reports.
We’re keeping this available as part of the Layer v1 archive to show how users were already solving real problems in the early days of the product.
For current workflows and tools, visit layer.team/4.
This video features one of the first real FF&E workflows built in Layer by an early user, Louise Cupac from Plusparts LTD. Louise was also our first customer outside the US.
She walks through how she used categories, elements, and fields to track product data across a large project using one of the earliest versions of Layer. While the core structure is still familiar, the platform shown here doesn’t include features like templates, shared views, or document reports.
We’re keeping this available as part of the Layer v1 archive to show how users were already solving real problems in the early days of the product.
For current workflows and tools, visit layer.team/4.
