elabx

I am pulling content through ajax to display a grid of images, but, the initial set of images that load when starting the site are selectable through a page field. (Each grid item is a page that works only as container). So, in my $config->ajax I have something like this: $selector ='sort=title,template=featured-service|caso-exito, start=' . (int)$input->post->pagination . ', limit=6'; $ajaxProducts = $pages->find($selector); Now, is there a way I can filter with not() PageArray method using data from said page field??

Looks very nice! Love the drawings over the lines. That´s also my strategy to output one page sites, iterate children and just $page->render($params), what a bliss! Just a doubt, how do you handle the "/home/children" url path? I mean, even if there is now link to that actual url, is it recommended to remove it or redirect to home with a kind of auto scroll to the section?

I have the vague impression that database migrations are better supported in other types of frameworks/languages (Rails/Ruby)? Or is Processwire simply not intended to have this type of implementation? Or am I misinterpreting something here? I can only guess from my experience, that database sync is not trivial. It just sparks my curiosity that currently there are two threads asking about this, and also have read about a lot of people rather using static CMS due the "databaseless" way these apps work.

Agree, the API is unbeatable. I haven't tried every CMS but at least the ones I have tried, everytime it was time for "Hey Mr.CMS, could you please get me this content from over there?". Either there was no clear answer or a solution that wasn't really up to my liking. For example, in Perch, there is perch_custom_content that returns an array with the data which I instantly started hating. Call me lazy, I just don't like how you have to iterate over array within array. You could imagine my shock when I saw Page and PageArray objects working with chained methods and the beautiful one liners you can do with PW. The closest I have experienced to PW somewhere else is with Kirby's own $pages and $page variables that also work much like PW's I think. But, what eventually moved me away from Kirby was discovering PW page and its page tree that just looked like the answer to all my data organization/displaying/retrieving problems. Had never really though about this. My first site with Processwire had to had an ajax and cached Instagram feed. It was implemented horribly, with the libraries in template dir and a php file for ajax right outside site folder, but IT JUST WORKED. No new things to learn, no weird tricks, just plain PHP working as it is intended. I think that's very helpful for people still in the process of learning backend techonolgies, but that can be proficient doing the front end. In Perch they also have a kind of template tags, which I was never really convinced of using.

The only thing I have found in the forums is this post comparing Perch and Processwire. Though from that list we can tick live preview/drafts Edit: Also found this topics with interesting discussions regarding Perch and other CMSs. https://processwire.com/talk/topic/2936-processwire-v-perch/ https://processwire.com/talk/topic/1433-if-you-had-to-use-another-system https://processwire.com/talk/topic/2554-other-cmss I would add that my opinion about Perch in particular goes along with the line of thought in this post:

Great update! I love the modal edit, it is just such a great addition!! Makes using the tree view really smooth!

Thanks a lot Matthew!! I have done a few things with D3.js and it's amazing what can be done, just browsing the examples page is really great! For example, I am a BIG fan of this guy and his work, be sure to check it out.

I...don't use SVG... Could anyone point out to resources of how to properly use SVG? I have read that there are a number of ways of embedding SVG, fallback stuff, etc. Is the IMG tag as tooth-paste mentions, the most practical approach??

I agree with that loading the page edit through ajax could be a great improvement, a user sent me a module once that basically accomplished this and it is wonderful, I keep it in all of my PW installs. It just misses to update the tree without reloading. I have been working on Shopify, and this "smoothness" in going from one part of the site to the other is very well accomplished in their interface.

I didn't even know PHP could actually look like that. First time I was like, "what the heck with all those arrows?".

Check this example by Ryan himself, I think this form is as simple as it gets, pretty much in a regular PHP way, but using PW API to make it all a lot nicer. This other post by Soma has insight on how to create a Page and save it. You just need to put the data from your form into the fields.

I am always used to plan something ahead in Chrome. If I want to add something, I just write the HTML markup with the correct id or class in the file, and in Chrome I start fiddling with the CSS directly. I will have to check the developer mode completely. For the IDE, I'm very happy editing with Emacs.

How about substr?

I have to say I agree with pwired, what he is exposing is exactly what I got as a first impression of the overall site. Nonetheless, I like the other design feats, color choice and typography and of course imagery all looking nice to me.

This is cleared by the answer written by Tom. I will elaborate on his answer just trying to include the HTML you wrote a few posts back, I hope it makes it more clear. I'm not exactly sure the syntax of the nested dropwdowns is correct, hope you get the idea. <?php $results = $pages->get("/")->children("template=events|articles"); //$result is one of your "content types", in this example, it could be Articles or Events page object. ?> <?php foreach ($results as $result): ?> <li class="dropdown"> <a href="" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-haspopup="true" aria-expanded="false"><?php echo $result->title //This would echo either "Article" or "Events" ?> <span class="caret"></span> </a> <ul class="dropdown-menu"> <?php foreach($result->children as $user):?> <li><a href='<?php echo $user->url ?>'><?php echo $user->title ?></a> <?php foreach($user->children as $item): //This would be an article or event in itself?> <li><a href='<?php echo $user->url ?>'><?php echo $user->title ?></a> <?php endforeach; ?> </li> <?php endforeach;?> </ul> </li> <?php endforeach; ?> This could be included anywhere in any template and render the same, because $pages (whatch out for that plural!) variable that let's retrieve any page no matter where you are on the tree. The $pages->get() retrieves one page, in this case the root page, and the next method "children", returns the PageArray whose contained pages matches the selector. The only thing I don't like about this is that I would need to specify the selector's parameters in case I add more "content types". But that's more of a topic on how you would plan your website.