heldercervantes

Yeah, it's become quite image heavy. This was initially published with temporary content (some 3d renders while the place was being restored), and now that the final photos are here and there's so much content, it makes sense to review the optimisation parameters. The map is just another image block they're adding from the CMS.

Thanks for all the feedback guys. I'll certainly be doing some improvements in the afternoon.

That's strange. Can't detect that here. What OS?

Whoa, that's not supposed to happen. Mind telling me what you're browsing with? I hear you on the contrast. The super light font on the menu can be hard to read, but alas, I'm not in charge of design on this one.

I forgot to add this one. Verride Santa Catarina is among the most upscale hotels in Lisbon, set in a historic townhouse in the heart of the city. http://verridesc.pt/ It's a modular design that allows pages to be built using a set of blocks the admin can customise.

Now that you mention it... There's a video block that's missing now, still being produced. That will probably reveal a bit more.

Here's a wee one, single pager, for a Foccacias place here in Porto that I can say is very good: http://rt.com.pt/

Thank you @SamC It does have some problems, I am aware. It's an elephant to load and very experimental, so it's a bit rough. In fact, the engine (whitestormjs) was being developed as this site was implemented, with this site serving as a guinea-pig to discover issues, find missing features and whatnot. That by itself is a bit dangerous. The web is so volatile that instead of polishing too much, I'll probably wait until I have a couple more case-studies to add and cook up a new site with some fresh experimental stuff and a whole new set of problems

I'll certainly remember this thread on my next project. All the time I add fields that make sense to be moved into the settings tab, like "Show in footer menu". Many thanks!

Precisely! Thank you Zeka, you've just saved my life.

I'm implementing something with field rendering. The approach goes through a RepeaterMatrix, there's a PHP file for each type of repeater block, etc. When rendering a given field, in that template's file I need to reference the actual page, to ultimately grab its children. How is that done? I'm finding nothing in the docs.

Fastcomet looks nice. I may give them a try myself. Thanks for the tip.

Not really. The one I use is reliable and provides good support, but it's Portuguese. Last year's CMS Critic awards elected Bluehost (https://www.bluehost.com) as the best provider, and Inmotion (http://www.inmotionhosting.com/) as runner-up. Maybe they're worth checking out.

I've been using shared hosting without any problems. Unless you're developing a big project with very specific needs, you should be fine going that way.

...minus all the clutter

The first thing I do after installing PW is switch to Reno. I see Peter's point but the admin is not for me, it's for the client, and I see them taking Reno much more seriously. When I discovered PW I had an agency that used an in-house CMS. It wasn't very easy to convince the dev team to try PW because they were underwhelmed as well. They were used to the module philosophy where you have a place to manage news, another for events, another for pages and so on. But all it took was one project to get them hooked. I'm hoping the new default theme is here before I start my next project. Fingers crossed.

This must be the most impressive thing I've seen in PW. Hope it was expensive too

Yes, good point. We're discussing this and Ryan can already have somethign up his sleeve. In terms of my availability, it's up and down. Currently my mornings are dedicated to an agency doing frontend dev, and other agencies sporadically call for my help. Right now I have some free time, and expect that at least until the end of year that will continue to be the case.

Went ahead and set it up:

Taking the cue that came up in this thread, I'm taking this first step to evaluate if we have something to go on as to create a new site for our beloved PW. First of all, we'll need a blessing from our godfather Ryan. Then we need to establish a proper team with roles. I'm taking the first step but by no means placing myself as leader of the project. So I propose that whoever wants to contribute, step forward and say what role(s) you can contribute to in this adventure. Myself, having a background in creative direction and frontend development, I can contribute in planning, design, copywriting and frontend dev. To lead the project, I'd tip the hat to one of the veterans everyone knows.

Yes, and personally I'm up to lend a hand. But we need to organise. Maybe by starting a thread dedicated to setting up a team and starting to discuss things.

Arguably nice GUI

Personally I have the impression it's growing at a slow but steady pace. And though slow and steady is much better than fast and sloppy, it's a bit frustrating to see other platforms seeming to get more attention while being notoriously inferior. I like following CMS Critic's Awards. PW has got a bunch of exposure there, but this year it's only nominated for "Best for SMEs" alongside Craft and ModX, both paid platforms. I'm guessing Craft will get that one because it looks polished and very DIY, and PW is too "pro" for that category. Then there's "Best free CMS". PW is not there. You see the usual Joomla and Wordpress there, along with CMS Made Simple. That one just trying out the demo makes me cringe. It's so 2001 that I can't take it seriously. Now I've never used Joomla, but I constantly compare PW with Wordpress and can't comprehend how Wordpress still holds on to such a large chunk of the market. "Best Open Source CMS". CMS Made Simple, ModX, Silverstripe. So I went to see what Silverstripe is all about. Now SS looks to use a somewhat similar approach to PW, and though it looks relatively polished, it doesn't feel as mature to me. So we've got PW in one category this year, and the wrong one. To me that feels like a loss, which will reflect another dip in that Google Trends chart over the next year. The next version will be an important step. Updating the default theme of the CMS is a must. I'm guessing most people now immediately install Reno's theme the second they enter the CMS after installing. So a new version with a new look will attract attention and that will hopefully pull it up a bit more. If we want it to grow faster (an argument can be made whether that would be good or not), it's mostly a matter of getting more people to try it out. After getting the first project running, it's hard not to be hooked. On an end note, I think it's time we start considering a refresh on the website. Just saying.

You're right, thanks for the heads up. I imagined that as a linear sequence, you're getting to know the company and at the end you get to the services but now that you mention it, the transition comes as a surprise and feels unsolicited. I'll have to improve that.

Hello fellow coders. ProcessWire is really easy to jump into. But a few projects in you start to want some version control, look around for what to put or not in .gitignore, want some SCSS magic going on, and it makes sense to make a boilerplate. So I did: https://github.com/heldercervantes/PWBoilerplate Some of the things going on here: src and dist separation, so you do version control on only what matters; scss compilation; js combining; asset monitoring and mirroring. Here it is for you all, in case someone finds it useful. Any comments, suggestions or criticism are appreciated.