Why Record Looms

One of our company missions is to 'empower' teams to use Webflow and manage their Webflow website. Whilst we want companies to come back to us for more work, they have been sold the dream of being able to manage a lot of their own website, if they so choose to.

Therefore as part of the project closedown, once the site is about to be transferred to the client (assuming it is complete) you should record some easy to follow, bespoke Loom videos.

‍

What to Record

The exact nature of the Looms will vary depending on the project. But you should assume they are a non-technical user and explain things we may assume to be the case as Webflow Developers/regular users. Assume they do not know anything about Webflow and speak from that perspective. The Looms are there so the client can look back on them and also share with team members if needed.

Content of Looms should cover:

• Editor mode - How to change images, text, buttons(text and links), how to use the Page Settings (Meta title and description) (example)
• How to add items using the CMS (including different save/publlsh options, different Rich Text functions etc) (example) (example)
• Quick overview of the Designer mode, explaining that they shouldn't touch that (aside from components)
• How to use Component + variables in Designer
• If they have specific functions for the project (such as an Airtable integration) any applicable Looms need to be considered

‍

If they will likely use the Designer, cover how they should use or not use the Designer (such as to not mess with class-names etc)

‍

How to save the Looms

The Looms should always be saved in the Paddle Creative team workspace in Loom. And Looms foreachcompanyplacedinside a sub-folder with the company name. This way you can share the folder to the client.

It is likely they will have future questions and so any future Looms should also be saved in these folders.

Remember to change the save name for the Loom. By default, Loom will use the page name and date. Change the name of the Loom to ensure it is clear what the Loom is, such as 'How to add a blog using the CMS'.