Mike Rockett

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: http://www.smashingmagazine.com/2014/02/03/one-solution-to-responsive-images/ The article makes reference to these as well: - http://www.smashingmagazine.com/2013/07/08/choosing-a-responsive-image-solution/ - 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!

In a nutshell, I moved away from other systems and started using Bolt, due to its custom content-type-driven system. There are some features that Bolt lacks, some of which are not planned to be implemented as yet. Specifically I was interested in a hierarchy set-up, with content-types. That's when I stumbled into ProcessWire (not for the first time, I might add - I had seen it before, but the styling turned me off for some reason). When I did, I saw a new website, and an amazing admin-theme, which won me over pretty darn quickly. My first site in PW is for a Cameroon-based company, called AEG & Partners. For my first attempt, I'm quite proud. It was really easy to put together, and very straight-forward when it come to building custom modules. Glad to say that, at this point, I won't be looking back. Edit: Oh, and Ryan, I did pop an email through with regards to the showcase link - it doesn't have a thumbnail... Was my image incorrectly sized?

I love this - it's such a unique design, something I really appreciate. Going to +1 the scroll-with-touch-pad problem, and I think it's worth mentioning that it's quite jumpy on my touch-screen as well. It's probably a missing-link with regards to my resolution, which is 1366 x 768. When I drag that main slider up/down, it jumps a little, every now and then. Tapping the arrow, however, obviously creates a smooth effect.

Very nice work, dazzyweb.

Hi, and welcome cwsoft I'm also pretty new around here, having fully switched to ProcessWire a little over a month ago. I, too, came from various different systems (PyroCMS, SilverStripe, WordPress [yes, also forced ], Typo3, and Drupal). PW has really done a good job at melding everything together in such an elegant, and simple, fashion. So yeah, welcome to the club @renobird: I can't wait for 2.5 - going to give the dev branch a try today.

That's one thing that I did think of doing - moving the 'required' labels to the field labels, and perhaps putting them in brackets.

Thanks for your constructive input, Benjamin - much appreciated. I think the scrollable-list-box is the main thing behind why it seems like the form asks for two much information - it's really just a mindset thing. So, I will be changing the two of those to standard select-boxes. With regards to the placeholder texts, I can see where you're going with that, and you are quite right. For me, it isn't an issue, but I'm sure it can be for others. I'll either add placeholder texts to the name and email fields, or make the other placeholder texts pop up in little tooltips when the respective field is entered. Which ever looks simpler is the one I'll push to the server. I have found, through a bit of research, that many people actually don't focus on the meaning of the asterisk. Perhaps if I remove the 'optional' labels, and leave the 'required' ones on the form? And yes, I agree with the logo-link - I think it is necessary to have. Force of habit for most users, anyway.

Thanks,glad you like it I think I'd be the person to know that the arrows are not links simply because I am a UI designer, and am not 100% aware of what people expect links to be. I think I'm going to change them to diamonds, or many even circles. As for the phone number, it should be white on grey... Could you perhaps show me a screenshot?

Oh, and I'd also like to know what people think of the contact form, in terms of its layout. It has been pointed out to me that, at first glance, the form asks for too much, even though many of the fields are optional. Do you think I should make those 'optional' fields collapsed by default, ProcessWire-style?

Thanks! I would think that's old-school - I've only seen them to be links on really old sites (you know, with tables). From my perspective, a link should be highlighted in colour, perhaps with an underline, or should be in the form of a button. Simply, anything that looks clickable. Would love to know what others think of this. I could change it to a square-diamond, which would match the logo. What do you think of that?

Indeed - I'm one of those people that checks things out thoroughly.

Great site - I love your work Just noticed that the links to the websites you have made are incorrect - little bit of human-error in there somewhere: <div class='meta'><p><a href='Array' target='_blank'>www.reims.fi</a> ...

Thanks, Gayan - much appreciated.

Greetings Recently uploaded my first site made within the amazing walls of ProcessWire. It's a very simple, yet professional, site for an accounting, tax, and business consultancy in Limbe, Cameroon. The site uses well-built templates (especially on the backend - I really love the way everything works with the editing pages on a per-template basis), and a custom module for the contact form, which runs a clear and concise validation service, powered by the respective Illuminate components (yes, I had to mingle Composer into the scene). Looking forward to many more sites in PW - as it is, I have three more to upload by the end of July. Hope you like it - feedback is always welcome. www.aegpartners-cm.com

Just curious as to why all requests that are sent to index.php are routed through the it GET param... RewriteRule ^(.*)$ index.php?it=$1 [L,QSA] Any particular reason why it isn't simply this: RewriteRule ^(.*)$ index.php [L,QSA] Or even this: RewriteRule ^ index.php [L,QSA] ?

@owzim (better? ): I agree with the provision of content - though it would really be specific to each site. But, 99% of the time, you'd land up displaying the most important content in a very static way (your one column idea), and just display a friendly message that talks of dragons and the dark ages. And evolution.

@Martijn: Agreed. As with most things in life, everything is specific when it comes to determining which browsers to support. Over time, and looking into the future, most developers will be moving to Owzim's 'rule' (as you put it). People are moving into an era of auto-updates, which helps us developers - especially those just starting out. I remember when I started, and it was such a nightmare to make IE6 behave. Everything is clearer now, knowing that nobody cares for it. Personally, I don't believe in patches. If something doesn't work in IE8: tough. If a site needs a feature, and a browser doesn't support it, then we drop the browser. Unless, of course, the feature is really specific, and doesn't make a big difference to the end-user. So glad I will never see ie-fix.css in any of my code ever again.

Just an opinion here, but I don't think that's the best route to take. Think of Chrome and Firefox. Yes, whilst they do auto-update, there are many PCs around where the feature has been turned off. A colleague of mine is still running Firefox 16. I always do an analysis about the client's needs before I disclaim which browsers will be supported. From a general point of view, only browsers with full, native HTML5 support, and a good throw-in of CSS3, will make the list. That gives me IE9+ (sorry 8, but your days are over), Firefox 4 (though, I usually up that to 10, as it is not as old), and Chrome 25 (same reason).

Not to worry - looks like I got it. Simply added this to my module: $this->session->tokenName = $this->session->CSRF->getTokenName(); $this->session->tokenValue = $this->session->CSRF->getTokenValue(); Then in my view, called it like so: <form data-form-ident="contact-form" data-form-token-name="{{ session.get('tokenName') }}" data-form-token-value="{{ session.get('tokenValue') }}" autocomplete="off"> EDIT: Well, that screws it up I'm calling it from within a module: Fatal error: Call to a member function path() on a non-object in [omitted]\wire\core\SessionCSRF.php on line 51 So, I'll just make my own CSRF token within the module that does not depend on the page name and path.

Anyone? I still can't get this working...

Hi all I have built my own module for processing forms on my site. The module does check to see of the request was forged or not, but I am unable to inset the token name and value into my template. I use Twig for my templates, and this is what I'm calling: <form data-form-ident="contact-form" data-form-token-name="{{ this.session.CSRF.getTokenName() }}" data-form-token-value="{{ this.session.CSRF.getTokenValue() }}"> The output for that is an empty string. Could it perhaps be because I am using Twig? Side note: disabling Twig is not an option as the templates I'm using are very complex - it would be a darn mission to revert to native PHP. (PW 2.4.0)

Nice site indeed I see on http://mbci.mb.ca/who-we-are/administration/, the mailto link for the assistant principal is broken - it's missing the mailto:...

Very nice, and very clean - I like them One thing though - and I see that there are a handful of showcase sites that do this: On http://ciaraphelan.com/, your menu seems to be hardcoded, because the trailing slashes are not in the URIs. So, for every single page request from the navigation menu, there will be a redirect, which adds unnecessary page-load time. It would be best to either add the trailing slashes in that menu, or use a $page loop so that the links are correct. Otherwise, very nice.

The client pushed me to put the site live, which I have now done. Funny thing: it works on production, but not on staging... Weird. Have you seen this happening before? My staging server is a simple XAMPP setup with PHP 5.5. The production server is running 5.4.

Right, so I don't use multi-language, and I have followed the instructions for the module by Pete - but, the module is not working for me, and I need to figure out why. As I use Twig, I cannot use the template, and must use the module. I have to assume that something's broken with the module, because it just doesn't initiate.