Jump to content

Testings Nearly Finished Photographers Site


Recommended Posts

Hey Everyone!

right I'm nearing the end of development on this photography agencies site and I was wondering if anyone could have a quick look for bugs etc.


It's not quite finished so there may be obvious stuff, also there's ALOT, going on in the front end, for example:

- pages are cached client side (to prevent unnecessary ajax requests for seen pages)

- Ajax page requests & pushstate

- pdf module for gallery pages

- slideshow animations

- add image to your custom gallery

- alot of menu logic

- responsive

- lazy loading images on gallery pages

Let me know what you think.


  • Like 10
Link to comment
Share on other sites

Indeed - it is a great site. very nicely built.

Must agree with Philipp here. In fact, there are several images that are too large. Sure, they're not all 2.3MB, but they're a tad too big.

May I suggest that you have a look at this article for more information on how to work around this:


The article makes reference to these as well:


http://adaptive-images.com/ (this looks quite promising)

And perhaps a loading indicator? Changing the title to "Loading..." was not easily noticeable for me; perhaps some people have slow connections/latency may question if a page is even loading.

Otherwise, I like it! :D

  • Like 1
Link to comment
Share on other sites

You can always make those images responsive. Thanks to Horst, PWs native images sizer provides images with much more quality than before. It's really easy to create responsive images with JS or even with the new SRCSET attribute for images or the <picture> element and respective polyfills http://scottjehl.github.io/picturefill/#examples

It's great that you give the option to collapse the menu to show the images in bigger, but I think the wording could be better: I don't really want to "collapse the menu", what I really want is to see the content in bigger. What I mean is that the wording could be something like "enlarge content" and turning it into "show menu" as you already have there. I also think that this ability should only be present in the gallery pages as there's no point on seeing the blog or the copyright notice in larger.

Just a suggestion :)

  • Like 1
Link to comment
Share on other sites

Really nice and clean website here, top notch photos everywhere!

May I ask you to point us (at least me) in the right direction to use requests and pushstate with processwire?


maybe more is to read here: https://processwire.com/talk/topic/4792-festival-site-with-processwire-and-ajax-boom-festival/


Edit: A very good site @benbyf. The only thing that I (personally) would change is the behave when clicking on a photographers name: one should get the "Main Gallery" directly, no need to click two times before seeing the first photo. / but also a bit nitpicking, I know :)

Edited by horst
Link to comment
Share on other sites

Thanks everyone, an image is still a hard won problem, especially when your not restricting the client in their uploads to much. Will look harder into this, but still loathed to use polyfills for images.

Really nice and clean website here, top notch photos everywhere!

May I ask you to point us (at least me) in the right direction to use requests and pushstate with processwire?


I was thinking about writing a lengthy description / tutorial on this site, as there's loads in it after it's live. I'll endeavour to do so after your interest.

  • Like 6
Link to comment
Share on other sites

  • 2 months later...

Loving the work. Im working on a very similar project, but I hadnt figured out how one would implement a add to custom list. I would really love to know how you plan on accomplishing this.

I have just a couple observations. A small thing that was kind of confusing from a navigation standpoint is how the links go to the parent page where the photographer is on as opposed to the page itself, it wasn't until I moused away from the link, and it faded the rest of the images that I understood why you did this. I think from a gut point click perspective if I were to click on an artist I would expect an artist page.

One little detail I think would really jazz up your page transitions, as you will be performing fades, would be using a little plugin like imagesloaded. Then you could fade images once they are loaded, and get rid of the loading of those big pretty images that you have.


Link to comment
Share on other sites

Thanks MuchDev.

In terms of the images, I am using a image loader for the galleries if you scroll down (try turning javascript off and your get the first 2 images), but I'm not using one ofr the page load itself so maybe something I can improve if the client agrees.

  • Like 1
Link to comment
Share on other sites

Thanks MuchDev.

In terms of the images, I am using a image loader for the galleries if you scroll down (try turning javascript off and your get the first 2 images), but I'm not using one ofr the page load itself so maybe something I can improve if the client agrees.

As I said though, just a suggestion. I did see the photographer loading which is what led me to want to comment in the first place. I really like you use of infinite loading on the pages. Also your tag display system is pretty slick, I like the ability to grab selections of work based on a tag, I have a mondo tag system I've been developing that will be very similar. Great work though, it is really coming along!

  • Like 1
Link to comment
Share on other sites

caching help? As pages can be got directly or via ajax Im having massive caching issues (as it wont work with ajax), anyone have any solutions they can direct me too?

Currently a page template is if'ing in ./head and ./foot if not ajax so that I'm only grabbing page content instead of all the page resources etc. But, obviously to me now, I'm unable to caching any of the pages with ajax on them as they get served without the head and foot as the ajaz version is more likely to be cached. interesting problem.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Similar Content

    • By Chris Bennett
      Inspired by @bernhard's excellent work on the new customisable LESS CSS getting rolled into the core soon, I thought I would offer up the module for beta testing, if it is of interest to anyone.

      It takes a different approach to admin styling, basically using the Cascade part of CSS to over-ride default UiKit values.
      Values are stored in ModuleConfig Module creates a separate AdminThemeTweaker Folder at root, so it can link to AdminThemeTweaker.php as CSS AdminThemeTweaker.php reads the module values, constructs the CSS variables then includes the CSS framework Can be switched on and off with a click. Uninstall removes everything, thanks to bernhard's wonderful remove dir & contents function.
      It won't touch your core. It won't care if stuff is upgraded. You won't need to compile anything and you don't need to touch CSS unless you want to.

      It won't do much at all apart from read some values from your module config, work out the right CSS variables to use (auto contrast based on selected backgrounds) and throw it on your screen.
      You can configure a lot of stuff, leave it as it comes (dark and curvy), change two main colors (background and content background) or delve deep to configure custom margins, height of mastheads, and all manner of silly stuff I never use.

      Have been developing it for somewhere around 2 years now. It has been (and will continue to be) constantly tweaked over that time, as I click on something and find something else to do.
      That said, it is pretty solid and has been in constant use as my sole Admin styling option for all of those 2 years.

      If nothing else, it would be great if it can provide any assistance to @bernhard or other contributor's who may be looking to solve some of the quirkier UiKit behavior.
      Has (in my opinion) more robust and predictable handling of hidden Inputfields, data-colwidths and showIf wrappers.
      I am very keen to help out with that stuff in any way I can, though LESS (and any css frameworks/tools basically) are not my go.
      I love CSS variables and banging-rocks-together, no-dependency CSS you can write with notepad.


    • By Richard Jedlička
      Tense (Test ENvironment Setup & Execution) is a command-line tool to easily run tests agains multiple versions of ProcessWire CMF.
      Are you building a module, or a template and you need to make sure it works in all supported ProcessWire versions? Then Tense is exactly what you need. Write the tests in any testing framework, tell Tense which ProcessWire versions you are interested in and it will do the rest for you.

      See example or see usage in a real project.
      How to use?
      1. Install it: 
      composer global require uiii/tense 2. Create tense.yml config:
      tense init 3. Run it:
      tense run  
      For detailed instructions see Github page: https://github.com/uiii/tense
      This is made possible thanks to the great wireshell tool by @justb3a, @marcus and others.
      What do you think about it? Do you find it useful? Do you have some idea? Did you find some bug? Tell me you opinion. Write it here or in the issue tracker.
    • By BitPoet
      Here's a small new module that adds a "Manage tags" button to the template list, just like the field list already has.
      Easily add, remove and change tags for your templates.

    • By gebeer
      Although the PW backend is really intuitive, ever so often my clients need some assistance. Be it they are not so tech savvy or they are not working in the backend often.
      For those cases it is nice to make some help videos available to editors. This is what this module does.
      ProcessHelpVideos Module
      A Process module to display help videos for the ProcessWire CMS. It can be used to make help videos (screencasts) available to content editors.
      This module adds a 'Help Videos" section to the ProcessWire backend. The help videos are accessible through an automatically created page in the Admin page tree. You can add your help videos as pages in the page tree. The module adds a hidden page to the page tree that acts as parent page for the help video pages. All necessary fields and templates will be installed automatically. If there are already a CKEditor field and/or a file field for mp4 files installed in the system, the module will use those. Otherwise it will create the necessary fields. Also the necessary templates for the parent help videos page and it's children are created on module install. The module installs a permission process-helpvideos. Every user role that should have access to the help video section, needs this permission. I use the help video approach on quite a few production sites. It is stable so far and well received by site owners/editors. Up until now I installed required fields, templates and pages manually and then added the module. Now I added all this logic to the install method of the module and it should be ready to share.
      The module and further description on how to use it is available on github: https://github.com/gebeer/ProcessHelpVideos
      If you like to give it a try, I am happy to receive your comments/suggestions here.
    • By Peter Knight
      I have a few web forms which require testing on a weekly basis and I don't want the recipients (administrators) to receive these test emails.
      What would be a good way to test approx 15 forms from the front end and have the test delivered a list of secondary administrator recipients?
      I'm thinking that I could have some kind of config file which watches for a trigger word or email and then understands that it's a test and to bypass the normal admins?
      All of the forms ask for an email address so I could setup an email such as 'testform@email.not' etc which my config file (hook?) would watch for.
      Or is there a better way to do this?
      Additionally, I have a few extra requirements...
      Forms should goto an alternative success page. This is because I don't want my test to skew my Google Analytics conversion tracking Forms would need to be tested from the front-end and not the PW admin area Any advice appreciated.
      BTW I realise this should be posted in the proper FormBuilder support forum. I am in the process of renewing my license for access to that support forum.
  • Create New...