heldercervantes

The fact that I got all this input overnight is in itself a good argument. I intentionally omitted what I already did in the meeting to defend PW, and it's nice to see other people mentioning the same things: Told my personal experience, not being a backend coder, I have built my personal site completely from scratch and didn't get stuck even once; After my experience, brought PW to my engineering department, asked them to build one of our client's site with PW and got such good input that it's now our dev platform for small to medium projects (cases such as Volvo's CRM we use our own platform); Showed him hands on how easy it is to make changes to my own website, added a field to my portfolio section, customized it and had it output on the frontend (under 5mins); Demonstrated that PW doesn't make any assumptions whatsoever as to what you're going to build, being a blog, products catalogue, news magazine, etc; Mentioned that it's been around for 7 years (is it?) with regular updates and we have a new major update coming this week; Explained the learning curve: any programmer that picks up PW will be building a website the next day. Still, great extra arguments here. I owe you guys a beer!

Comunity unite! Today I tried to convince a "quite high profile client" to have a new site built with ProcessWire. He's not completely convinced. This is a well known, nation-wide brand with a big audience. They've invited a few agencies to show them what they've got, requiring an open-source platform "such as Wordpress or Drupal". We've of course introduced them to the wonderful world of PW but, since they've never heard of it they weren't quite comfortable and insisted on either the W or the D. It's a basic known vs unknown dilemma. Their main concerns: Support / Community - finding other devs in case my company shuts down Security - don't want to get hacked Guarantees - as in they feel comfortable that WordPress and Drupal won't go anywhere and keep getting updates, but what about PW? So help a brother out: If you had to answer "Why should I buy as website built with ProcessWire instead of Drupal or Wordpress?", what would you say? Thanks, HC

Thanks guys! I'll go for regular users then.

It's thanks to posts like this that PW is so easy to learn. Great one here! I'm stuck trying to use this with FieldtypeMapMarker. Any ideas?

Hi all. So after my first experience with PW on my personal site I want to try something bigger in scope. I'm experimenting with a system that will allow users to register themselves, and then will let them create and edit pages. This will all happen in the front-end in a custom user area, not in the back-end. So my question is: would it be best to register these users as regular users, or should I create them as pages and manage them as such? This second approach strikes me as safer, keeping the real admin area out of the equation, but I'd like to hear the thoughts of someone more experienced in PW. Thanks.

Great find! I'll probably use it somewhere soon.

Volvo's solution is custom-built from scratch. At YAP we have our own CMS platform that we've been building and improving over the years. There's a smaller project that I convinced our coders to try out PW and see how it compares to using our own platform. It will be interesting to see how that goes. Oh and thanks for the tip. I just added myself to the directory.

It's quite simple. I have a "portfolio" page, and a bunch of child pages for each project. Then on the template I just did a foreach cycle to repeat a block of HTML for each project: <?php $projects = $pages->get('/portfolio/'); foreach($projects->children as $project) { echo "<div id=\"{$project->name}\" class=\"page\">"; echo "<h3 class=\"projectTitle\"><span>".$project->monster_label."</span></h3>"; ... } ?> In my site I have to do this on 2 separate locations. One for the slideshow and another further down for the actual content. I have a separate page type for the about block, with its own fields.

@adrianmak, yes it is. I used swiper for the slideshow and built my own way to turn it into a menu of sorts. That way I was able to have deeplinking and make it behave like a multipage sans-pageloads. I also used lazy image loader so all the big images in each project would load only when needed.

Sure. Let me know when you're back in town

Love the idea of the intro phrase doubling as a menu. Nice work

Networking time! Temos que combinar uma cerveja

Thanks for the remarks. I have to say that working with ProcessWire was nothing short of spectacular. I'm mainly a frontend guy, and the API's simplicity is just perfect for me. Got the site running using only php echos and foreach statements, literally coding it amidst conversations with friends and half looking at my screen. So simple and logic. Plus the barebones + modules approach to the CMS ensures a super clean and streamlined product. No posts module that you don't need, no unnecessary fields, just zero clutter.

Sure will. Thanks for the tip

Hi guys. This is my first project with PW, my personal site and portfolio. Check it out: http://www.heldercervantes.com This is an almost clean PW installation, with only the file type repeater module for all my repeating needs Had an awesome time with PW and will definitely explore it further on future projects.

Hi guys. I'm trying to setup a tab in processwire to list all pages under a specific page. I have a "portfolio" page and under it I create pages for each project. This new tab ideally would just display a page list starting from the portfolio parent. What's the best way to do this? I would also like to add another tab that would jump straight to editing a profile page. Thanks for your help.