About last night… Thanks to everyone who came out. 26 in studio, 50+ on the stream and two people who drove 2+ hours to be there! #Webflow vs #WordPress https://t.co/m8PWQXl5pc for the replay
thanks again to @thepixelgeek and @TheDavidJohnson for sharing their knowledge pic.twitter.com/CWNWYVRlXM
— Raymmar Tirado (@RayTirado) September 13, 2019
After reading a tweet on Webflow, learning about their recent Series A funding, and attending a “Webflow v. WordPress Live Debate”, I was curious to see if I could use any “thing” from Webflow on a WordPress powered site.
Yes. Webflow to WordPress migrations are possible, depending on your content and goals.
On paid Webflow plans, select content can be exported. Files in the resulting zip are well-organized, but do not include collections, e-commerce, or search support.
Once you’ve exported your project, you do not need to maintain a paid Webflow account nor are your required to include any kind of Webflow attribution, according to Webflow documentation.
After obtaining my exported files, the next step was to create a WordPress theme, which requires the following files as a minimum starting point:
style.cssfunctions.phpindex.php
For this small scale test, index.html became index.php. Within the file, calls to wp_head(); and wp_footer(); were added. Adding in get_stylesheet_directory_uri() successfully updated pathing for css and js files. Google Analytics and other code was added to index.php. In future experiments, content from index.php will be placed in header.php and footer.php.
Basic information was added to style.css to set the theme info and styles were enqueued in functions.php.
A custom thumbnail image was added to the newly created theme directory.
Given the limited scale of this test, conversion assistance tools like Udesly and Pinegrow were not utilized.