bodhic

Thank you Martijn. That works. Would similar logic apply if I wanted to add a new div after every third i.e. something like <div class="row">?

<?php foreach($page->schedule_item as $schedule_item) { echo "<article> <div><h2>{$schedule_item->title}</h2>"; echo "{$schedule_item->body}</div> </article>"; } ?> Hello again... I'm posting this question here as it's related to my original question. If I'm using a repeater and I want to have to assign a different class to say... every third item, how would I go about setting that up? Thanks...

Thank you titanium. That worked.

Thanks adrian, but still no luck. I'd like to try one of the cleaner methods, but I'm still feeling in over my head on a lot of this.

Thanks adrian. I gave it a shot but, that just pulls the container page or "Program Classes", not "Class one" etc... I want it to ignore "Program Classes" and just pull it's children.

echo "<ul>"; foreach ($page->children as $child) { echo "<li><a href='{$child->url}'>{$child->title}</a></li>"; } echo "</ul>"; How do I take this and make it so that I can get pull the children of an unpublished page? The site I'm working on is for a fairly large fitness center that offers multiple program/classes. My structuture is something like this: -Program Overview -Program Classes (unpublished to act as a container) -Class One -Class Two -Class Three -Program Instructors (unpublished to act as a container) -Instructor One -Instructor Two -Instructor Three Any insight is always appreciated. I'm still ironing out issues with the transition from ModX.

Nice find apeisa. That certainly makes more sense.

No argument here guys. It is pretty stupid and not a big deal if I don't get it incorporated. Since I use Foundation/SASS I could probably just extend the li class and handle everything via css. I was asking this question more out of curiosity than absolute need. I guess there is one use case where this might make a little more sense. Foundation also comes with a default <label> rule for their navbar. So it might be useful to be able to append something descriptive like this within a dropdown: <ul class="dropdown"> <li><label>Descriptive Label Here</label></li> <li><a href="#">Dropdown Level 2a</a></li> <li><a href="#">Dropdown Level 2b</a></li>

Hello and great module. Overall it's working perfectly, I just have one question. I'd like to set up a structure like this: <li>Nav Item</li> <li class="divider"></li> <li>Nav Item</li> <li class="divider"></li> <li>Nav Item</li> I'm using Foundation4 as my css framework and the "divider" class is the default seperator. Is there a way to append an empty <li> between links? I appologize if this is a stupid question, but I'm new to PW. Other than this, I've found the module very easy to implement. Thanks for any help/insight that you can provide.

Cool. Thanks a lot everyone. You've all given me a lot to consider. The hardest part of transitioning from Modx to PW is getting used to the "openess" of PW templates. Without there being one "best" way to set things up, it's initially a little overwhelming. I'm will give Diogo's approach a try and see what I'm able to do with it. MatthwShenker thank you for the detailed response. Again, this appears to be a really great community and that's encouraging.

Thanks everyone for your replies. You all are great! pwired, I am definitely Link 3 under "Newbies First Starting Questions". lol! I guess I could have been a little more detailed with my question, but I was pretty tired when I wrote it. First. I am definitely using css to layout the page, I'm using Foundation/SASS for the layout which has already been prototyped. The design is a "modular grid" that will feature excerpts about my client's different product offerings. I've attached a "down and dirty" Balsamiq mockup that will give you a rough idea of what I'm trying to do. I need a little more time to go through everyone's responses, but it's looking like either pulling the data from child resources or setting up a repeater (a la migx) might be the best approach. Thank you all again for your replies. This seems like a great community and it could be just the thing to turn me into an "ex-modxer".

Hello ProcessWire community. I'm new to PW and I'm diving in head first on my inaugural project. I have a lot of experience working with ModX and I'm excited to learn something new. I'm just struggling with some initial hurdles in structuring my project. PW is very cool, but also very different from what I'm used to. Anyway, my question is this... I have a design for a homepage that will have multiple conent areas (8 to be exact) and I'm not sure what the best logic is for structuring my template. I see in the basic example site there's a main column with the body copy and another column for sidebar content. That seems reasonable for two content areas, but with 8 and the possibility of adding more in the future it seems like multiple text fields would be a less than elegant solution. Thank you in advance for any insights.