martinluff

I'd certainly like a solution along these lines - agree about the usefulness of Matrix (and you can do similar thing in SilverStripe using the DOM module). Seems like ProcessWire is already pretty close if you look at the images field type for example (see the way this works on the home page in the skyscraper demo - where you have the file and a description and can add new 'rows' for additional images). Seems like you could adapt that so you can add other fields to a field like that as well as to a template (in the way you just have description text field) and you'd be there? Of course I realise that's simple to say and more difficult to implement - but looking at how the fields are added in tables in the backend db then seems like the system would lend itself to that relatively easily?

A while back I saw some independent tests that showed keywords in URLs definitely counted in some SE results (Google and Yahoo included). Plus if you read some of the comments from Google themselves then seems to suggest there's some benefit: From Sitepoint: "What Is the URL structure preferred by Google? Google’s Matt Cuts replied: I would recommend long-haired-dogs.html long_haired_dogs.html longhaireddogs.html in that order. If your site is already live on the web, it’s probably not worth going back to change from one method to another, but if you’re just starting a new site, I’d probably choose the URLs in that order of preference. I can only speak for Google; you’ll need to run your own tests to see what works best with Microsoft, Yahoo, and Ask." However, I think Ryan's comments are spot-on regarding the file extension part; i.e. has no effect other than pages already ranked by Google from an old site which include specific file extension Rgds M

Thanks for the response on that Ryan - yes makes a lot of sense and I see what you're getting at... guess I'm still stuck in the mindset of a few other systems

I'd add a +1 for publish/unpublish by date. For example on sites with content like job adverts (and also with other things like events/courses - although in those cases I guess you might want to use more of a dedicated calendar type arrangement) we regularly prepare a number in advance and then set a date for them in the future to go live and then auto-expire on or before the day of the course/event. I guess you could also rig up something in these sorts of cases to simply redirect to general info or overview page as they expire to avoid just getting a 404 after unpublishing if that's a concern?