Joss

I drove a DeLorean once - it was like trying to navigate an aerodynamic bucket. And yes, Soma does seem to work on an "I will read your mind first and then I will tell you what you are going to think" sort of principle. He should be writing on the wiki .... (hint)

Many, many years ago there used to be a UK sitcom about two old tailors called "Never mind the quality, feel the width!" A perfect adage, as far as I am concerned.

Hi FuturShoc It is not really attaching an image to the page, just upload it using the image field that you have included in your template. Because this is as much of a framework as a CMS, tools like images dont come with templates by default, you have to add the capability. Obviously, it only takes a few seconds, but it also means if you don't want to include images, you don't have to. By the way, you can upload more than one image with the image field and you can also just call that directly into the template. So, if you wanted a Main Image in your article, but don't want the user to mess up how it appears in the text, you can sort out how it is laid out at the template level. If you do that, you may want to remove the image button from the TinyMCE field you have created so they cannot add an image to the text. (Go to the field, edit, input tab and you will see the configuration area) In the template file that you associate with the template you will not need to call the image field since the image address will be part of your TinyMCE output as normal. It is very much like using the Wordpress image system, to be honest. You can even select an image from another page if you wish. Note: there is also a very good thumnails module that allows you to preset loads of thumbnails and so on. It does not associate with TinyMCE so is perfect for images that you are directly calling into your template. You can then add all the JQUery you want to mess around with them on your page

And I have emailed back to Ryan an even longer article version of what he wrote to me .... but I will spare you all that for the moment (Just in case I got it really, really wrong...)

HI and Welcome FuturShoc Adding an image to a TinyMCE field requires an additional image Field. On your template, add the Body Field (which is already set up with TinyMCE) and the image field which already exists. Go to page and add a new page, selecting your template. On the ..... Oh, blast - dave got there first!!! Well, just to finish, when you click on the image button on TinyMCE it will open a custom insert image popup which will list any image you have uploaded with the image field. Choose one of them and you will be able to resize it and choose its alignment. As DaveP says, you just then need to make sure you have the right CSS. If you are just starting out, try the Panet project but also, you may want to have a go at this much more detailed tutorial: http://wiki.processw...ebsite_Tutorial Good luck, and keep asking questions!

Hmm, I am being likened to Sports Personality of The Year? If you saw my current shape you would realise how incredibly inappropriate that is! (And anyway, Ryan has been messing up the count by just hitting Like for absolutely everything in a desperate attempt to wade through it all.... )

Just supporting the idea of isPublished() as I think it adds value.* Talking of which.... @boudaryfunctions I think what is likely to happen is that there will be very detailed and powerful online documentation, a solid and related API (all free to use) and separately a book that will be more aimed at less experienced users. Something like that. In addition - all help is needed on the Wiki as a really good starting place for the moment to get things down somewhere! Joss (*I have noted that it is now mandatory to make some reference to the original post... however cursory that might be)

I would also be interested in hearing how various people got into this and ended up making a living. I have been in the media world for 35 years in various guises, and although I was instrumental in some early cutting edge sites (news and community), it is only very recently that I have seriously considered making the whole web design process officially part of my business. However, learning how to use ProcessWire, tarting up some Photoshop skills and generally sharpening my copy wirting quills is not the same as actually walking into a company and saying, "Hi, I can build your next site for you!" Joss

Strangely, they are still mostly Soma .....

Done most of the bits on the Tutorial, apart from the code issues - added a reply to your comments. Edit: And done the other ones too!

I Would like to throw a huge, hefty spanner into the works here! (Just for fun) If you split PW into two piles, in one pile you have the Site directory. Here is, or will be, your CMS. PW gives you a starter, but once you get into it, you are going to build your own content management structure in there on top of the base. In the other pile is the WIRE directory. However, this is NOT a CMS, or perhaps even a CMF .... I have a suspicion that it is really a CME - a Content Management ENGINE! Joss PS: I have this great want to rename the SITE directory to PROCESS ... just to round off the gag.

@panictree There is an underlying problem with so many of the alternatives and that is the use of the term CMS. As time has moved on and some, like Ryan, but many others too, have looked at web applications as tools that can achieve more than just allowing someone to edit something. Consequently, the term CMS has come into its own - it is not just about a news article, it is about managing and manipulating all kinds of content. However, some systems, and I put Joomla and Wordpress into this category, are basically just AMSs - Article Management Systems - that are bent and broken to make them work in other ways as well. As time moves on, this is going to prove to be more and more of a limitation and if they don't break free of that model, their usefulness, especially for businesses, will dry up.

Review and like done on Alternativo thingy. Also, here is one blog post about EE that maybe worth commenting on: http://420creative.com/blog/entry/ellislab-expressionengine-what-the-hell-is-going-on

Matthew Scheneker told me about it. So ask him.

Yeah, doesn't really feel the done thing. However, I am sure people will be talking about it on their own sites - go and comment on their blogs!

If someone wants to write an article about how to make the move from EE to PW, I will gladly edit it and give it some spin. It can go on the Wiki as a useful article and then you can all put it on your blogs everywhere! I am not talking about how to move an actual site, but rather if you do this on EE, this is how to achieve the same thing in PW .... that sort of thing. Joss

Ah right, I see what you mean. I will catch up eventually, honest!

When Matthew and I were trying to do stuff with Seblod/Joomla, I created a front end admin system for content management (not other functions). They way I did it was simply to make sure you can work a route through things. So you would have a nice button saying NEW+ with a drop down so you could select a new what, and another buttons saying MANAGE which would take you to a list of things to manage with some filters and column sorting. It was not great, but you couldn't get lost because that was all there was. To translate that into PW, that would mean the NEW+ buttons would have (for those with permissions) New Template, New Field, New User and then New Whatever which is added by the admin and is specific to the site. The only thing after that is once you have created your NEW thing, you can easily Duplicate, Delete, Close, Create another identical New Thing or go for lunch, just with one click. Another nice little drop down perhaps. Without changing the existing layout at all, it would just speed things up a little. Not hugely, but just enough perhaps. Joss

I was thinking about the back end. I tend to work from the idea that the admin should be the place you can use thoroughly unless you want to create a specific experience where you may use the front end or create a complete new admin system or what ever. Maybe Ryan can create a hook in the normal admin menu so that it can be customised either with processes like this, or even manually for people that want to put specific things in it.

Er not totally sure With articles in progress, shove something in the Discussion on the wiki - but let me know or I will miss it. For new stuff, put it in here or emails or something .... Sorry, not wonderfully helpful! Joss

In broadcasting we did everything we could to avoid leaving the visitor hanging when our data source dried up (the engineer got his kipper tie stuck in the VT, for instance). Not getting that right and ending up shoving a test card in the viewers face was a near sack-able offence. In a perfect world, a visitor should get an apology and a static site to play with - perhaps a cached version of part of the site or something. At least enough so they can still read about your world, even if they cannot interact with it. Sort of a 404 on steroids that is not reliant on the database. And of course, a nice output for the poor admin somewhere .... Joss

Actually, that works even for the developers, who by the time they have finished the site have completely forgotten the bit they did at the beginning ... Most sites are never going to be so complex, but some will, and being able to guide a user through a search/browse process in such a way as it speeds them right up will benefit both the untechy user and the dev who is lost in their own genius creation... Talking of which: Soma, I have a module idea for you that sort of relates to this: Basically, It is the ability to create a drop down on the admin bar to which you can add links to the "new" link of parent pages. So, if you have a page which is the parent of your news articles, a link to its "new" link can be made and named "News Article." So, rather than scroll through your ever growing list of pages, you can just hit the button. Possibly an addition to the template - a check box or something that adds it to the menu? Sorry, haven't thought this out fully. Joss

Just as a general thought about UIs generally (rather than this one in particular) there seems to be a problem with them being what I would call enterprise ready. Basically, doing things like cross linking between articles where you may have thousands of them, or digging out an images that was on a page several hundred back, or just searching for information from one page to copy into another. I am not totally sure what the solution is that addresses that issue and is also neat and easy for the site with just 20 pages in it. One thing I do know is that clients hate it when they get confronted with a search - great, if you know exactly what you are looking for, not so hot if you can only just remember .... (not that I am old or anything.) These are problems that have plagued just about every system I have worked with, with the possible exception of a couple of Crays .... Joss

Nice! Could do with a nice square logo for that sort of thing - I am sure one appeared very, very briefly on the Wiki one day then vanished again...

One of the little difficulties in recycling fields is with the Textarea/TinyMCE field. Settings for the TInyMCE configuration are at the field level, so if you want slightly different configurations between uses, then you will have to create different fields. In the end, it is a question of finding a balance between efficiency and organisation, and quite where that balance point lies is completely up to you! Joss