onjegolders

Thanks!

It's funny, I didn't expect such a negative reaction from people to the menu. I totally hear what you're all saying, but it's sort of surprised me. It's interesting, because I wonder if it's a "developer" type reaction. I mean, would the reaction would be the same if you were just going onto the site as a normal person, browsing the site in a normal fashion. I think when you're in "developer mode" checking out a site, if you're anything like me, you're sort of jumping back and forward from page to page, seeing how things work, checking stuff out, using the menu probably way more than you normally would. Do you know what I mean?

I think the average site visit is *click* to where I want to go, then read on that page for a while. *click* to another page. Read etc. Whereas, I'm almost certain all of you guys didn't bother to check any text and just clicked around to see how things look. I know that's what I do when I'm checking out a site design. The text might as well be Lorem Ipsum and I'd never even notice, ha ha!

@onjegolders | BTW, just checked out Milktop... very slick... I like it! (although, I didn't read any text )

Fair point. I think it's a common people and like Pete says you don't have to please everyone! I certainly don't dislike it, it's just a conscious decision as a designer that you're putting an extra click between page changes. Sometimes it's the right choice too.

Great looking site, I agree with Diogo though about having the navigation hidden on inner pages can be a bit annoying. I suppose if it appeared on hover rather than click it may be a nice compromise. Really nice work though.

And welcome to the community

ProcessFish

  

Thanks for the tip re. Url and Path History.

I've updated the URL yet the link above is till broken even though Path History is installed.

I't's a great CMS. I meant to be further into my learning but am having too much fun with PW right now.

Craft has some very nice features when it comes to editing content. Although I can't imagine an API as strong and flexible as ProcessWire's I think it's good to keep tabs on the better features if some of the better alternative CMS. It has a pretty nice interface.

I think all this discussion is very valuable, but everyone knows my opinion by now. I will try to resume it with an allegory.

When you were at school, I'm sure you had to read some classical books for your native language class and probably bought those small resumes. The purpose of those resumes was to put things in context and explain some trickier parts AFTER you read the book, but some of my coleagues colleagues (not me  ) read only the resume and not the book. Some had average results, and some had bad results, but none had a good result. Maybe if those resumes wouldn't exist, they would be forced to read the book and have good results, of course they might not read the book at all and have all bad results, but that would be their own fault right? The point is: we can of course try to make things easier for new users, and some can be really useful and important, but we should be careful not to make things look easier than they are by hiding the complexity under the carpet.

Just don't ask Diogo about browser back buttons!

Obviously if it's for a bit of fun then I think anything goes but if we're being serious here about using it as a promotional tool, I would try and focus on the voice being friendly and bright.

blad, André's English is not too british at all

Haha!

I'm happy to help out, I have quite an "English" voice but if you need something sillier maybe consider Joss

Actually a lot of these product videos are done in very upbeat American accents, probably better at selling than a British one

EDIT: Do all these product intros have the SAME jingle??

Can you see any pattern to which ones are at the top? Are they the correct template from your API call?

If you go to your template->family->sort settings for children, is there anything set in there which may be overriding your API sort?

EDIT: Sorry just saw this "Parent is set to manual drag-and-drop."

Can you share the selector you are using to display these pages on the homepage?

Eg: $pages->find("")

Hi Vxda,

Can you share what selector you are using in your template?

Perhaps an example will help us to understand, not entirely surely I'm grasping what's happening...

I think we need to team up Blad with Joss...

Subtitles by Willy C

Sensational

I'm actually not against the idea. It can make a lot of sense if it is giving a customer a happy outcome for their budget however there always seems to be some almighty compromise.

These templates often look lovely and shiny and then the minute you open them up in a code editor your day goes quickly downhill

I prefer to work with talented designers like Erika (http://www.ed-works.com) amongst others.

Where budget becomes tight I try and at least see if we can come up with a design "concept" in that time without fully fleshing it out.

No, that website tutorial is already way too much text about html and adding styles and philosophy.

On the other side there is the api cheatsheet which is great for developers, but for a non coding beginner too condensed and even a bit scary.   

I mean something like an extended version of the api cheatsheet, and also with more complicated snippets and their output.

So that even a noob can look at a piece of code and immediately see what it does by looking at its manifested html output.

And everything on one page, just like twitters bootstrap docs:

php ....

the html output

php ....

the html output

and so on.

Thomas it's very hard to please everyone. I also found this difficult when I started using PW.

The main reason why there are no clear examples of the best way to do something is that there are so many ways. It is both a strength and a weakness. It is essentially PHP that is being used and that is where most people who have learned to use PW have found their "snippets" or examples of how to do things.

The tutorials are improving with the help of people in the community though. Soma has a list of some more complicated gists here https://gist.github.com/somatonic

Something like when you click on "more" on the cheatsheet items -> ie. http://cheatsheet.processwire.com/pages/built-in-methods-reference/pages-find-selector/ ?

The cheatsheet is outstanding and the extended functionality is great.

May be a nice feature in the future to have a few examples underneath on the extended part (a bit like php.net, but better of course )

Completely agree with Joss.

Also as another point, and I've been thinking about doing this.

There's nothing preventing the creation of various modules that do make certain assumptions.

A blog module could install templates, fields and even a basic stylsheet that could incorporate a blog into an existing site. There is definitely more room for these "bundles". Perhaps the reason there aren't more of them is that the majority of PW users prefer to make everything from scratch.

But these bundles shouldn't harm that existing community as long as they are addons. 

PS: 

Did you get a makeover Joss?

Maybe the OP is right about one thing, it is good to know who you are and what you are and I think clearly if there "has" to be a choice, then ProcessWire would be a tool for web developers rather than a plug and play system. 

Could it be both? Possibly, and as more profiles come about, the community will grow but I don't think we will ever see Ryan deviating from his beliefs and they have got him an awful long way towards what is probably the best PHP content framework on the market.

The other point is, as Diogo says, there are an awful lot more systems out there that appeal to the OP's market than Processwire and although that isn't necessarily a reason to shun that market, I'm pretty happy with where the system is at the moment and direction its headed.

Although I do see the value in being able to "see" the reference two-ways in the admin. Might be nice for a backend user to see it from either angle.

Hi Reno,

The thinking here is that the editor will only really be touching content for the journal. In the past I have done like you said and created front-end forms but in this case, I thought why not take advantage of PW's very robust forms.

I think the workflow is quite nice. They have a login button, they login get redirected back to the journal where they can edit / add posts that also get processed with PW.

It saves me building the forms and validation and it saves the editor having to poke around and choose parents and templates.

(It makes sense in this scenario but I don't think I would use it apart from this "blog" scenario)

Hi Blad,

I have in the past, created two-way relationships like this however, have you considered just having it one-way and using the API to find the reverse?

As an example

<?php

// get all clients properties
// assumes a $client variable

$properties = $client->properties;

// get all clients who have access to a property
// assumes a $property variable

$clients = $pages->find("template=client, properties=$property");

?>

It depends on whether you really need it to show both ways in the admin, or you just want to be able to display both directions somewhere on the frontend.

If you really do need it to show both ways in the admin, you can create a simple module that creates the reverse relationship when you update a certain page.

Tiny typo on the roles page:

Simply assigning the page-edit permission here does NOT give permission.

Just picking up this old thread. I don't think Evan's solution is applicable anymore but Soma's still seems to work, albeit with the caveats he already spoke about - that every call to admin goes to the new URL.

Just wondering if there is a new hook that will enable a simple module to redirect a user after a login (in my case, back to the front-end).

In the meantime I'll keep trying all the combinations

Good point Reno, thanks!