I’ve just started experimenting with Elements and after publishing some pages, it seems that it creates a separate folder and css file for every page. I found I could get around the folder issue by using / as the folder location, but it still produces a separate css file for each page.
Is there a way to not have it do that? I’d really prefer the more traditional structure. I was toying with the idea of converting a fairly large site, but this kind of puts me off on that.
Thanks
Hi @jamorin,
Can you describe the output you’re trying to achieve or share a screenshot showing the layout?
We use a folder per page to keep the output organised and allow the use of cruftless links, so you don’t need to specify a filename on the url. Each page references its own CSS file containing just the styles in use on that page. How were you intending to store the CSS for your pages?
Cheers
Is it possible for a setting to be added to use the organization that we have set up in the Pages window with the naming of the individual pages controlled from there, rather than having to set them from the page inspector?? That way the site could be organized as set in that window. (Instead of using the default method of how Elements names / renames pages when uploading or sets page names in the inspector.
I do recognize that if that were done, we would have to make sure the names are web safe, etc., but that shouldn’t be much of a problem.
Yes, this should now be the case. New pages/folders don’t set a folder name and will use a web safe name based on the title by default. If you change the title in the project organiser, the folder will also update. The URL field in the page inspector should show a preview of this.