Joss

Hi Daerias Here is a generic tutorial explaining how to add ANY framework to ProcessWire - it is remarkably easy, indeed, there really is no proper need for my profile at all! http://processwire.com/docs/tutorials/installing-a-css-framework/ Joss

Yes, I know with one friend's eCommerce site, I moved him over to full SSL (rather than just the cart) and there was no obvious hit on performance at all, even though he was on a shared server. The two main things about it are probably just the cost (which is not huge, but yet another cost all the same) and the annoyance of remembering to renew the certificate. Also, some hosts seem to have a frighteningly complicated procedure you have to go to get it up and running - a real minefield for the small website owner who is possibly trying to do it all themselves.

Wow, still going? I remember playing with it a few years ago when they were first experimenting with extjs - looked interesting, if cumbersome.

Love it Read the site, looked interesting. Clicked on the join the CAcert Community link, and.... The site's security certificate is not trusted! You attempted to reach www.cacert.org, but the server presented a certificate issued by an entity that is not trusted by your computer's operating system. This may mean that the server has generated its own security credentials, which Chrome cannot rely on for identity information, or an attacker may be trying to intercept your communications.

http://www.bbc.co.uk/news/technology-28687513 Or, so say Google..... (Apologies to Noddy Holder and Jim Lea from Slade.)

The word "Enterprise" gets used, abused and misused widely, and it is no help to anyone. To many developers/coders out there, Enterprise means it can scale up happily. But to the business community, Enterprise means it has a support structure in place that is able to relate to the large organisation, that it has a stable, long term support version and so on. I think if you release a business/enterprise version of anything, you must be in a position to speak to non-technical, business decision makers and be able to answer their needs I know from a cousin who is a decision maker in a large public company, that when they go for the Enterprise version of anything, it is not that they expect more bells and whistles than the community version, but they expect to be treated very differently. PW is not currently in the position to do that, unless someone can work out how to clone Ryan for free.

Well, one blogger. And he/she doesn't get much in the way of comments - but nice of them to pick it up

Yeah, I am just trying to avoid listing the damned things!

On mine, I am going to try and replicate links if I can so I don't actually have to do any redirects. But it might take a little adventure with URL segments, I suspect ...

Oh, I like violet! On the blog side of things, since you migrated, what have you done about re-routing incoming links to blog posts on the old WP installation? I need to migrate a couple of my old ones, and that is something I was thinking about. Nice, clean site, though!

I still think that if a complex profile were to be created that had theming, widgets, other expected fair, then it should be on its own site with its own support. It would be "built" on ProcessWire, but it would no longer be the core PW. Likewise, if a full blown e-commerce system was built on PW (now, that would make far more sense as a project), then that too should be on its own site with its own support structure. There is a bit of me that says that to create a themable version of PW seems more to be fulfilling the idea of attracting WP type users, than does it achieve anything huge. I am part way writing a tutorial to help WP and Joomla designers and developers to make the transition to PW. It is not a technical "how to" but more about how you need to change you way of planning and working and thinking. In the process, it strikes me that there are already lots of perfectly good "out-of-the-box" pop-up type CMS solutions out there. As I write the tutorial and explain the strengths, they tend to be more about the fact that is hasn't got a theme or template engine, that it does not rely on bespoke plugins to create functionality and so on. Its core strength is that unlike WordPress which is really an AMS (Article Management System), ProcessWire is a true Content management System - you create content with it and then you manage it. Separately you work out how to display it. Importantly, if you discard the current default profile and, instead, install it with a blank profile, its strengths are much more obvious, The default profile with sample pages and some images, misleads you into thinking it is something like the rest of the AMSs out there. When you have nothing except a title field, an admin.php and a home.php (no html of course, just a single $page->title call on its own), then its nature as a true CMS is clear. To paraphrase old MS marketing: "Welcome to PW. What content would you like to manage today?"

I can see that a theming system would be popular, but I don't think it would be a Godsend - a lot of developers simply would not use it as it would not fit with their way of working. I would be one of those - I am really enjoying not having to bend someone else's theme to my will but being able to start from scratch (or work on top of a framework of my choice) using basic HTML and CSS knowledge. But that is not to argue against themes - they have their place too. And yes, this probably ought to be split off to another topic!

I know I have said this before, but actually I find the default profile misleading. It hints towards AMS (article management systems) like Joomla and WP with a title field and large content area, whereas the true strength of ProcessWire is in the fact that you can start with no fields and then go which ever direction you like. This is why, for me personally, I would love the default to actually be a clean, blank install and then have a "Demo profile" as an optional download, which would replace the current default profile. When choosing which to download (or install, however it is finally managed) a little more emphasis could be placed on the fact there are other profiles available which may give you different starting points, like the one you are talking about here. This also may reduce the artificial comparisons between PW and Drumlapress and help PW to stand out more on its own.

I think you would probably want to take it further than just themes, so that it is closer to the functionality of Joomla or WP out of the box. But I have to say that this would hold no interest for me - it is not what I came to ProcessWire looking for.

Dazzyweb Yes, I have mentioned this before, that a version of processwire could be built that is "themeable" or anything elseable. Including JQuery plugins for dancing girls or what every is the current favourites on Drumlapress. However, I feel this should be a completely separate project (basically a profile project) that is maintained separately and so does not confuse the brand values of the core ProcessWire project.

Apeisa and Totoff are quite right - it is a different audience. Though I would put in the rider that the ProcessWire API does so much heavy lifting with such short phrases that it makes it amazingly simple to learn, even for novices (or old has-beens like me!) While it also leaves enough in the PHP realm and html realm not to force markup and construction on you that you then spend half the night trying to override. (A big Joomla sin, that one) A good, well balanced, tool box.

Hi Jeff The first thing is about the young bit. Ryan first developed PW as a commercial system quite some years ago (he can give you the history if you are interested). He then made it open source in more recent years. Consequently, the core of ProcessWire (the Wire bit, if you like) is very stable and very developed. However, quite a few of the users on this forum are very experienced developers and coders, and this has helped speed up the development. I should point out, though, that this has not been at a break neck speed; Ryan is very much in control here and development is carefully undertaken. There are many differences between systems like PW and others like WP. The main difference between PW and WP is about the design philosophy. ProcessWire does not have any templating engine or system, it simply has a templates directory where you do most of your playing. The default install does have files in there, but to be honest, you could chuck most of them away (with the exception of admin.php) if you wanted to. Most of us do. So, if I want to design a site using, for instance, the Bootstrap CSS Framework, I simply shove it into the Templates directory as I would if it were going to be a static site. I can now create my file structure as I would normally. Perhaps a header and footer file, for instance. Maybe call these into a main template that I am using for a bunch of pages as I would do any other PHP structured website by using includes. Once I have done that, I just need to add the PW API to retrieve the information. Okay, so there is a little more to it than that, but the point is that anyone who has used Bootstrap would look at the templates and recognise just about everything that is going on there. That is incredibly powerful - it makes it accessible to many different levels of designers and developers very quickly. And that is important too - to a greater extent these are people trying to make a living; they need a system that works for them and does not force them down a particular route. More structured CMSs like WordPress need you to work in their way with their methods. That is great if that is what you want, but if you need to break out of that, you either have to get very imaginative or hope someone has done "a plugin for that." There is no doubt that you can get a fully featured WP site up faster than a PW site - but the PW site will be a lot more specific and tailored to the brief, and for most of us, that is far more important.

I have just put a long post up to answer some of his points - in a gentle way. At the end of the day, ProcessWire IS a system for website development - that is its strength and what makes it better for serious business websites than WordPress. In itself it is not, and probably should not be, a drumlapress clone. I would not want it to be as that is why I have moved away from those kinds of CMS. Of course, it is perfectly possible to build a Drumlapress type CMS using PW as the backend, and maybe that ought to be done, but that is a different thing and would be addressing a different market. The interesting point is, of course, that though PW is a development package, rather than an plug-and-play, instantly themable, push-button, solution, it is amazingly easy to learn! Even for complete non-developers. But you really have to want to. If you don't then probably PW is not for you.

There are a few here: http://www.freshdesignweb.com/fullscreen-jquery-slider.html Really, any responsive slideshow can be used in the background - it is just a case of positioning your content over the top

I think PW could do this - it would be a lot of work but the result would fit your needs exactly. The trouble with the sort of site you describe is that it is difficult to find a one-size-fits-all solution that does not mean some heavy duty compromises somewhere. If you do want a site that has huge multiple needs, you may want to look at Liferay. It is a java solution that allows multiple communities, each with their own sites (public and/or private), commerce, multiple domains, full business logic, and a ton of other stuff. It is a true portal solution. However, it is pretty scary! (And huge! The install is more than a gig). There is both a paid-for EE version and a community version - the latter is more bleeding edge and is amazingly well supported through the forums. The chaps there are much like those on here - go out of their way for people. It is very customizable, but I would strongly advise getting a Liferay geek on board if you are going to use it - it will save you a lot of messing around. My prefered solution, if you have the time and manpower, would be to go very bespoke using PW as a starting point.

I mean, does it need to have transitions and effects, thumbnails (obviously), html content ... that sort of thing

Reems, if you were to specify exactly what you need the functionality to do on the page (without thinking about the script you are trying to use), what would it be?

Arjen, they don't seem to offer that option for the thumbnail strip - just the main images, for some odd reason.

Sorry, I tried to read this in an Alan Partridge style voice and it came out very strange!

Loads of them listed on Google, search for JQuery Background Slide Show The main problem with using a folder based system is that you are completely stuck with it on the page you want - one version only. With any other system, you can create a different slideshow on every page if you want, or even several on each page, all easily customised from the back end.