Viewing Assets clean-up and single folder usage for images
Assets clean-up and single folder usage for images
|
User: Peter B. 11 years ago
|
|
|
The assets part is quite useful but it has some serious problems as I see it. Others have referred to this repeatedly and I am really wondering why nothing has been done about this yet. 1. Asset maintenance As we all know at times we add images to widgets and other sections and sometimes you may find you don't need these anymore after a while or when a page has been altered to not contain these used images anymore. It would be nice if there was some form of clean-up option that would remove the not needed files from those that are used. 2. Copying of Master page images in each and every folder. When using the MASTER page this makes set-up of your website and it's pages very simple and effective. Nice feature, but... there is a big downfall to this as when using the MASTER page the program copies all the image files used in the master page into each separate folder that is constructed using that master page. Please rearrange this so the program creates a /Master folder where all the Master page related images are stored. This makes loading faster because the browser can use the cache for the common images and it does not create 10 copies of the header image when using 10 pages in your site. 3. Single images folder It would also be an improvement if there would be a single images folder that could in itself contain subfolders where you can store images into for certain usage. For example,: Images / "foldername" (contains all the images you assign to that folder ( i.e. a images/logo's folder for logo's you use on your site) 4. Image renaming I tried to use image renaming by altering the names of the images in the assets folder. They are renamed in the view but when adding them to a slider or any other image widget, they kept their original names. So other then for your own viewing ease, the renaming of files in the Assets list is completely useless this way. Why not adjust the image names directly as well and adjust the names in the various htm* files as well. Even old FrontPage ( remember that ) could do this and did it quite well I may add. Peter |
|
|
User: Milo L. 11 years ago
|
|
| Yes, I'm going to have too many assets as I create my websites. I need subfolders desperately. Need to organize my assets like I did with dreamweaver. | |
|
User: John S. 11 years ago
|
|
| I've been experimenting with EverWeb and assumed the assets were going into a common folder for all pages to use. As noted above, for website caching and page load speeds, this would be very helpful. | |
| Post Reply |
| You must login or signup to post. |