Search the Community
Showing results for tags 'image library'.
Found 2 results
-
I've been reading through the forums for best practices on handling images on static pages - that's to say, how best to handle images in my static html markup when I don't have any need for image fields. On my current site, I have a lot of images on the home page and it seems silly creating an image field for all of these. Also, for pages where I do have image fields, I've been using the PageImageSource module to create wepb srcsets automatically (and it works great). I like setting my desired image sizes for the srcsets in one place, so I'd like to use this module for everything everywhere if possible. The problem is that it only works with PageImage objects, so I have to do something with my static images in order for the plugin to work with those. It looks like the media manager modules are not maintained. Could I just somehow put all my non-image field images in one page reference or something and have the PageImageSource module render those wherever they're needed? Could the following work? 1) Create an images/media page and template with images field. Set it to hidden. 2) // In _init.php: $media = $pages->get("template=media", include=hidden); 3) // on a template page markup: $desiredImage = $media->images->get("name=imageName.jpg"); .... <div><=?php $desiredImage->render()?></div> // renders the srcsets and <picture> tags with the PageImageSource module I don't know if this is the recommended way of dealing with <picture> tags for static pages (srcsets are such a pain to do manually!). Maybe there are some downsides to this that I'm not aware of. Any guidance would be very welcome. -
First up, a massive thanks to Ryan, the developers and community on this great CMS. We have spent the last 4 weeks looking at the best option for a client and it looks like ProcessWire will be the choice. We ignored the top 3 (Drupal, Joomla, WordPress) but spent a lot of time with Grav, Hugo, Concrete5, October and PimCore before we arrived here. I am not saying some of these are not great as well, but sometimes the best CMS is the one that matches your needs the most. I can't tell you how much of a pleasure it was to find your CMS and community So, one of the things we have seen that our client likes a lot is how many other systems handle Image and Asset Library. They like to be able to upload many 1000's of images, PDF's that get used on many different Pages. Content Editors can quickly find images from a tree/directory/tag structure and Drag and Drop over onto their pages. My question is anything like this on the roadmap ? If not, then does anyone in the community have a pointers or ideas on best practise to implement this ( a module? ) or is it something ( a use case ) that does not sit well with the way Processwire wants to be architected? Again, fantastic work folks, we are really enjoying Processwire and looking forward to looking at the ProDrafts & ProForms modules as well in a few weeks.
