Lightning Talk - Plone and Webflow
CC Attribution 3.0 Germany:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Bain, David
Strengths, weaknesses & trade-offs for these two platforms
 Plone and Webflow. Both platforms are for building websites and web experiences, but they approach things in different ways. I'm hoping that from this, this may inspire maybe things that may happen in the Plone community, as well as I wanted to bear in mind that these two platforms have different motivations and that may account for some of the strengths and weaknesses. Okay, so Plone, we know it has an enterprise content management platform and perhaps the probably two big things that tend to be emphasized are its security and flexibility. You can make it integrate with almost anything. Webflow, on the other hand, focuses very much on visual web design and content management has been kind of added on at a later date. So it has really strong design tools and it has an emphasis on no code development and was put development to make quotation marks because there's some limitations to what it can do. Let's look at Webflow strength. Top things that I like about Webflow tend to be associated with what you can do as a designer and also some of the editing experiences. Here's a Webflow interface and in this case I'm working in an existing project so I'm using pre-created symbols as they call it. You can think of these as blocks of visual code and I'm just placing those symbols onto the screen to create my layout and I can add other things as well that are not these are built-in things such as sections and what they call containers and I can put in a heading and paragraph. Now while I'm doing all of this I want to point out to you that this thing is responsive so at different screen sizes I can change the styles to get what I want. Webflow supports the concept of content types. It actually calls them collections so you can have a collection of news items or a collection of profiles. In this case these are basic documents and I'm previewing how each of these documents will look. There's also the capability to create interactions so what you see in me do here is create a simple interaction and test it out and all of this is visual and you can do really fancy interactions like what you see in here and here. So there's a lot of flexibility when it comes to designing the visual experience and here are the clone advantages. A common task like linking to an attachment is actually pretty challenging in Webflow whereas in clone it's it's pretty much standard so if I want to have a link to an image I can upload that image then link to that image. Some of those things are a little tricky in Webflow. So I call that CMS attachment but clone is also way more flexible for forms and they're half of those and other things where clone really shines. Here's a site that we built in Webflow. It's basically not more than four pages and simple whereas this one we built in Webflow but then we implemented it on top of clone so it uses Webflow's interactions but a lot of clones functionality. I would say to wrap up that you should use Webflow when you want to do simple designs and rapid prototypes. Go for clone when you need more robust CMS functionality.
 Plone and Webflow. Both platforms are for building websites and web experiences, but  they approach things in different ways.  I'm hoping that from this, this may inspire maybe things that may happen in the Plone  community, as well as I wanted to bear in mind that these two platforms have  different motivations and that may account for some of the strengths and  weaknesses. Okay, so Plone, we know it has an enterprise content management  platform and perhaps the probably two big things that tend to be emphasized are  its security and flexibility. You can make it integrate with almost anything.  Webflow, on the other hand, focuses very much on visual web design and content  management has been kind of added on at a later date. So it has really strong  design tools and it has an emphasis on no code development and was put  development to make quotation marks because there's some limitations to what  it can do. Let's look at Webflow strength. Top things that I like about Webflow tend  to be associated with what you can do as a designer and also some of the editing  experiences. Here's a Webflow interface and in this case I'm working in an  existing project so I'm using pre-created symbols as they call it. You can  think of these as blocks of visual code and I'm just placing those symbols onto  the screen to create my layout and I can add other things as well that are not  these are built-in things such as sections and what they call containers  and I can put in a heading and paragraph. Now while I'm doing all of this I want to  point out to you that this thing is responsive so at different screen sizes  I can change the styles to get what I want. Webflow supports the concept of  content types. It actually calls them collections so you can have a collection  of news items or a collection of profiles. In this case these are basic  documents and I'm previewing how each of these documents will look. There's also  the capability to create interactions so what you see in me do here is create a  simple interaction and test it out and all of this is visual and you can do  really fancy interactions like what you see in here and here.  So there's a lot of flexibility when it comes to designing the visual experience  and here are the clone advantages. A common task like linking to an attachment  is actually pretty challenging in Webflow whereas in clone it's it's pretty  much standard so if I want to have a link to an image I can upload that image  then link to that image. Some of those things are a little tricky in Webflow. So  I call that CMS attachment but clone is also way more flexible for forms and  they're half of those and other things where clone really shines. Here's a site  that we built in Webflow. It's basically not more than four pages and simple  whereas this one we built in Webflow but then we implemented it on top of clone  so it uses Webflow's interactions but a lot of clones functionality. I would say  to wrap up that you should use Webflow when you want to do simple designs and  rapid prototypes. Go for clone when you need more robust CMS functionality.
Lightning_Talk_-_Plone_and_Webflow_-_David_Bain_Pci60VwzthM_0_671.png Lightning_Talk_-_Plone_and_Webflow_-_David_Bain_Pci60VwzthM_672_719.png Lightning_Talk_-_Plone_and_Webflow_-_David_Bain_Pci60VwzthM_720_2399.png Lightning_Talk_-_Plone_and_Webflow_-_David_Bain_Pci60VwzthM_2400_2459.png Lightning_Talk_-_Plone_and_Webflow_-_David_Bain_Pci60VwzthM_2460_5435.png Lightning_Talk_-_Plone_and_Webflow_-_David_Bain_Pci60VwzthM_5436_7501.png