Adam Kiss

Clients usually love PW, exactly because of the reasons we stated. The worst type of clients, the almost tech-savvy ones, usually like the videos/idea of CMS, where you push 8 buttons and have everything set… then you show them the admin screens and they flee in panic. And when it comes to clients who are willing to compromise on the quality, just so they can use some technology… Well, I try to catch this early on, and just end the relationship, then and there.

Just FYI, I have super-rough Proof of concept for something like this, but its YAML based (and may need a week or more for a real Proof of Concept) --- Just read your original statement more thoroughly, and realized I'm doing a different approach, so no clash there

Hah! http://www.google.com/trends/explore#q=processwire%2C%20%22Nico%20Knoll%22%2C%20Adam%20Kiss&cmpt=q I bet it's something else, though.

Agree with Antti --- Also testing ipb iphone app

1.) He's using Joomla. He can't understand this. 2.) It's not about the number of features. Actually, the less, the better- are you really using all of them? 75% of them? 50% of them? 3.) Years of testing… Right. (come on. If anything has 100% of code years-tested, it's probably outdated) 4.) Want to do it different way than your precious module? Yea, fuck you. [This is 95% applicable for WP/drupal as well) --- With building on huge CMS + modules, you end up doing a lot of compromises, which I'm not willing to do. And those are also the bad compromises, the ones users see (unlike e.g. Rails, which makes do stuff his way, but output and experience are in your own hands) --- Ultimately, I'm not selling my clients my ability to stick modules together. I sell the best possible website (in terms of Bussiness Goals and UX) I can create.

either do it with module, or any other way possible with PW. And by that I mean, that PW will probably provide you with something like user management, but the rest will have to be handled by you (unless there already is module for something like 'read more' or such, which is entirely possible).

Hey encho, welcome to the forums. Categories, tags: no problem subscribers-only articles: certainly not a problem, even though this will contain some custom programming PDF downloads: doable, even though you'll have to provide this functionality by yourself (either by some CLI programs, or sending data to some service) Hope this helps.

Why is this not released already to hack on???

reading through this, fron the UX standpoint, your best option might be to create admin module, that will be in the main navi, like 'add person'. when you open it, it shows you firstname lastname fields, and when you submit that, a new page is created, with name and title created programatically. for the edit/delete actions, nothing changes (and you seem to have figured those out)

I thought that the '+Add item' is for adding a new repeater item without saving the page?

Just a note: these relative links seems to work for me: <a href=".">Parent</a> <a href="./child">Child</a> The parent isn't ideal though.

We absolutely need something for db migrations / versioning db with git or such, if anyone wants to throw money at Ryan

This is fantastic! Hah, it seems that people are doing a lot of stuff I wanted to do, "once". This will save me a lot of time, thanks!

@Sevafr2 this is actually good implementation [= doesn't break back button], bookmarked, thanks

+1 for 'looks like a folder', totally my opinion, although I was never able to come up with this simple reason I don't like trailing slashes. (on that matter, this is just a note. I still prefer no trailing slashes, but don't really care enough to be vocal about it)

Basically, have this available from outside under URL, and run CRON job on it every day, be it from the box itself or other hosting you have. No need for LazyCron, that's Netcarver having not enough coffee.

I'd say that thing is everything here is relative; They use Drupal, because they (the developers) probably invested huge amount of time into learning all the ins and outs and quirks of that system. Also, Drupal allows to do things fast…, but relatively compared to how long it takes to untrained person. And then, it really is fast afterall. That being said, there are two different ways I think about this whole 'Drupal can do big things': Some companies thinkg 'big' when they talk about hundreds of pages, which, when IA is done well, isn't really that much (even might be easy to navigate) Big part of these Drupal sites are membership sites, which I admittedly can't really imagine that easily being built on PW Regarding membership sites: Yeah, have registered members isn't really a problem. But having real membership/social site is a different thing, and Drupal has this already… take http://openatrium.com/ for instance. That said, I despise drupal, I think it's a behemoth, it's ugly, the HTML is horrible and if you need to debug/change the HTML, you can straight up kill yourself (since there is like 12 entry points where modules can change something, and not all of them are equal).

Firstly, I am not against any help we can get to get this baby shipped and tweak along. Secondly, I don't wish to take much credit at all, since due to my mistakes along the way it is currently in this sorry state it is (and by that, I mean "v1" not shipped still, and "v2" prepared already). We've gained a lot of traction along the way, but we lost a lot as well (lately). So anything to get the ball rolling again would be great.

@CMScritic: is this vote system based on IP? I visited the site (presumably on shared connection) and already seen votes casted from here.

start the cheerleading then: OEM version, $399: "I'm a developer and I make an open-source product (CMS, service, etc)." Seems that they changed the pricing a bit, previously it was covered by the $199 license. Edit: Perch do have it little easier… price for them is only $199… and their CMS is paid.

@Marco, @teppo: There are systems, where you actually do more than 'just' manage content in the administration: review orders, check for contact form submissions, etc. Also, there are systems/work settings, where you have multiple editors, and one chief editor. Understand: if there are things you do with your administration MORE then 'just' administer content, it's possible some kind of dashboard will be better solution than root == pages. Also, (with regards to more typical workflow), if I update some page just once/twice a year, I might like to see if there are any updates upfront, for instance.

Little OT: don't they provide some kind of geo load balancing?

Congrats! Any purchases yet?

Well for some ladies, everyone is gullible. I actually think it's good, that we have someone like mindplay: going through the 'low-level' stuff and questioning it, noone ever got better without questioning himself;

Forehead. I forgot to add forehead, now it's completely different joke. Dammit