First of all, THANK YOU so much for adding subdirectories! It was perfect timing for me - I hit a project recently that there just was no real way to work around that. BUT, there’s a problem. When I exported my site and uploaded it, I found that all the pages within a subdirectory incorrectly referenced assets - the assets were being linked as if they were within the subdirectory, rather than stepping up to the main asset folder. Example:
<link rel="stylesheet" type="text/css" href="css/normalize.css">
should be:
<link rel="stylesheet" type="text/css" href="../css/normalize.css">
on any pages within a subdirectory.
For anyone else who runs into this issue, I was actually able to create a very simple workaround in my Nginx configuration file. I added this to my server{} block:
location ~ /[a-zA-Z_-]+/(?<type>(css|js|images))/(?<asset>.*)/?$ {
alias /var/www/vhosts/afterschool.lummiisland.info/html/$type/$asset;
}
Ultimately, though, it would be better if the asset was properly referenced in Webflow. Again, though, still want to make sure the Webflow folks know that I am super appreciative that you added this feature in - life saver! Now if only I could publish to a remote server without having to export… 