yellowled

I am aware that this is (probably) not an issue related to PW, it's more likely a general issue in TinyMCE (and seems to be well-known among its developers already). I thought I'd mention it anyway: It is not possible to add images using TinyMCE's "Add image" button at a specific place in an editor's content in IE9. It always gets added at the beginning of the content in the editor, i.e. before the first text paragraph. I haven't tested it, but it probably doesn't work in IE8, either. Yes, I know there are different approaches of handling inserting images into the content which are preferable.

This really isn't harsh at all. Both colors and web font are predefined by the logo, which isn't my work. Frankly, I'm not a fan of the logo myself, but it's what I had to work with here. It's not an ideal situation, but quite common – the client is either unwilling to change the old logo or (like in this case) has just spent money on a new logo. Of course, this design is signed off by the client, they have seen and discussed all iterations of it. And they're quite happy with the results. Bottom line: I can't do anything about the logo or its colors. It is a typical example of client's doing print first, then web. Of course you're right that these colors are not ideal for web, althought they may work in print. I appreciate your notes and will consider them for further iterations. Thanks.

You probably have to set the RewriteBase in the .htaccess in your ProcessWire directory, i.e. RewriteBase /ProcessWire/ The are some examples for RewriteBase in the .htaccess, you can just uncomment and edit one of those.

As usual, this is to some extent related to what the client gave me to work with, i.e. the logo. But any constructive criticism is always appreciated, so I'd really like to hear more details on that. I'm not a big fan of frameworks. I have sort of my own starting point (which I wouldn't call a framework). The problem with predefined media queries is that they never really fit the actual design and content. Almost every design needs its own breaking points at which it needs to be adjusted using media queries – working with the usual standard breaking points (320/480/768/1024px) doesn't always work in all details, and I feel that responsive design needs special attention to details. As for the ProcessWire part, yes, it's been easy to build this with PW. I basically built an HTML prototype (which my usual MO, I never do PSD mockups or something, I just start with the HTML in the browser) and replaced the parts of the content which should be editable or created by modules (most notably the navigation which is handled by Markup Simple Navigation). I'm not even a skilled PHP coder, but with PWs API, it's fun for me. I actually learned quite a lot about PHP templating building this very site, and it has confirmed my impression that PW is going to be my "go-to CMS".

This is not necessary a question which can be answered with one sentence. It depends on the setup of you web server/web host. My web host, i.e. is set up to run using suExec, which means all script languages run with my user's permissions. You might or might not have a similar setup. That being said, as a rule of thumb (in most setups) both should be writeable for the web server user.

Thanks. "Technical college" might be the better translation. It's kind of a bummer the web server doesn't quite hold up to the site – it's hosted on a rather badly configured web host which requires to manually gzip CSS/JS files, among other limitations. The school doesn't want to change web hosts if avoidable because it also hosts all their email accounts (which are quite a lot).

http://www.bs-eutin.de Unfortunately, the site's in German only, so most of you guys won't understand its content. It's a site for a very specific type of school. I'm not sure if this type of school is common outside of Germany – the dictionary mentions the term "trade school". In Germany, apprentices still have to go to school one or two days a week. Also, this school offers some educational programs for people who are not satisfied with their regular school education and want to earn a better degree etc. Anyway, it's HTML5, it's responsive (using Adaptive Images), it uses some jQuery plugins (most notably Responsive slides and Colorbox). The logo was already done before I got the project, it also "dictated" the webfont. Unfortunately, quite a lot of pages are still missing a photo – the school is producing all the photos themselves (which I always prefer over stock photos), so it will take some time to fill the holes here (because the school term just started). This is the first larger project I did with ProcessWire, and it's been a breeze. Like I always say, it's not really a question if something can be done with PW. The question is how it can be done with PW.

One thing I just stumbled upon: I actually prefer to have CSS in /site/templates/css/ and JS in /site/templates/js/, some users might even put both in /site/templates/. Would it be possible for the module to just scan /site/templates/ and directories below for CSS/JS files?

If implemented in the core, it should be an option, not a default, I guess. Or at least, it should be possible to switch back to the "old" behaviour. (You'd be astonished how many people have difficulties performing a double-click.)

Last time I checked (it's been some weeks), this produced huge CSS code, at least for responsive grids. It is still work in progress/beta, so I'm not sure you'd want to use this in production just yet. I am, however, sure that the fine people at Mark Boulton Design have some tricks up their sleeves to make this a powerful tool in the future.

Personally, I don't use CSS frameworks (any more). I base all my projects on the HTML5 Boilerplate, but that's mainly because it gives me a solid starting point, mostly in terms of CSS normalization and .htaccess defaults. I really love it's build script since it takes care of a lot of small optimization tasks. I also have a set of CSS files (actually SCSS) to "enhance" it, i.e. stuff I often or almost always need, but I wouldn't call them a framework, especially because they're very much tailored to the way I work, which might not work for everyone. Those include basic styles for forms, a sensible typographic baseline, some Sass/Compass mixins for some common CSS "tricks" and a very basic fluid grid system. It's really more of a toolbox. The "market" on CSS frameworks has become insanely huge and crowded with a lot of so-called frameworks which cover only a fracture of what a framework should cover as well a some which try to cover everything. (And that back to IE 5.5.) It's really hard to give a recommendation since what they actually cover is so different. Are you looking for "just a grid system"? Do you want something which covers everything one might need in building a site? Do you need support for Sass or Less? Do you want just a CSS Framework or some JS/jQuery widgets included as well? Twitter Bootstrap is very popular these days, unfortunately, a lot of sites built with it tend to look very much alike. Zurb Foundation is pretty similar. YAML is always a nice alternative if you need support for older browser; unfortunately, it's rather big because of the browser support.

Have you tried setting "RewriteBase /" in the .htaccess? I seem to remember this being necessary if moving from a subdirectory to root, but I'm not 100% sure about it.

Did you maybe develop in a subdirectory and transfer to a root directory? Or did your dev site use absolute instead of relative local urls? I guess in both cases the "redirect to home" would in fact be a 404, which would only happen if your template/site doesn't provide a 404 page.

Just my experience from the last couple of weeks, but mostly with PWs API, the question is not if you can do something but how you can do it. The API as well as the whole system's architecture really don't limit the possibilities at all. There might not be an enormous amount of modules for just any task (yet), but there's a beauty to that as well since (again, just my humble opinion) if that's the case, one tends to use pre-built modules instead of building their own solution, which most often makes for a more unique site experience. And if you get stuck building a site on your own, you'll find a lot of solutions already posted here in the forums. Just start playing with the API, I promise you'll love it and very soon get a sense of how much is possible with it.

I never actually used MODx in production, but I don't think I'll ever use it. So far, PW has worked extremely well in 3 or 4 projects, the community has been extremely helpful and nice, and I have yet to see development take a direction I didn't like (and I doubt it ever will).

I already did add that this morning, seems like Ryan already approved my entry.

Subject pretty much says it all: the "more" link at the end of the description of the Markup Cache module points to http://processwire.c...es/markupcache/ which doesn't seem to exist (any longer). Noticed this in PW 2.2.2. Edit: It should probably point to http://processwire.com/talk/topic/7-new-markupcache-module/ instead.

Well, once and if PW attracts a greater user base, chances are someone™ will implement some kind of module or other mechanism to make building templates easier, maybe some kind of system like TemplaVoila or what's-it's-name for TYPO3. There might even grow a market for custom-made or at least pre-built templates, who knows? I absolutely agree that anyone can be bothered to fire up a text editor and follow instructions to copy & paste some lines into a file. It's not that hard. Then again, I have some years of experience in user support in a similar forum for a blog system … trust me, people will complain that this is too hard or something "only you nerds understand" … But there's also the question whether non-expert users do actually care for something like performance optimization. My opinion would be if they don't, their loss. If they do, they're gonna have to roll up their sleeves and get their hands dirty, just like we used to do. Of course we'll advocate them and give pointers and instructions, but no one can expect to be pampered in a support forum where people help out in their free time.

I just gave this a quick spin on my local Apache, works like a charm. (Can't really test it anywhere "live" since I don't have any "unoptimized" PW installations flying around since I usually use the H5BP build script to concat/minify.) Two small thoughts, both of them are completely a matter of taste: It might be a nice idea to emit the generated URL which you paste into your template in an input field instead of as plain text since that's usually a bit easier to get for copy & paste. As far as I know, Minify also has an option to emit a "clean" URL for the combined files, i.e. "style1.css" instead of "styles&f=reset.css,main.css" — which I'd prefer. I know it's silly and not an issue technically, but to me, it just looks wrong. Other than that: Great module to have, Pete. I'm not sure non-expert users will love this as much since they's still have to modify template files, but it sure adds a nice way to make Minify integration a lot easier.

I usually build my sites using the HTML5 Boilerplate as a starting point, including a Sass version of its CSS files, an up-to-date jQuery and some additional stuff I usually need. H5BP also has an additional build script, which takes care of a lot of tasks, including minification and concatenation of CSS and JS files (although I don't really use CSS concatenation since Sass handles that). This also plays very nicely with ProcessWire's templates – a typical CSS reference like <link rel="stylesheet" href="<?php echo $config->urls->templates?>css/style.css"> is accepted by H5BP's build script (ant version) without any modification. The only thing I need to do is add all .inc files containing CSS/JS references (I like to put JS references at the bottom of the page) to the build script's project.properties files. That being said … well, with PW's user base (hopefully) growing, it will attract more "non-expert users", which is by no means a bad thing. But to these users, a module is usually much easier to use than an external PHP script or a build script which requires additional software to be installed on their system. So in the long run, PW might actually benefit from having that kind of module, if only because it makes it even easier to create well-performing sites.

Interesting, but … correct me if I'm wrong, but most font services as well as the fontsquirrel generator don't even use .otf font files any longer. Most of them seem to use the Fontspring syntax now, which usually includes .eot, .woff and .ttf plus (optionally) .svg for older iphones … or do .eot (being embedded OpenType) have the same effect with PostScript or TrueType?

From my experience, that's true for any webfont. TypeKit, Google Webfonts, self-hosted, doesn't really make a difference. What's most striking is that they look okay-ish in IE9.

Thanks, but I got it covered. There are just 5 urls with a %{QUERY_STRING}, that's perfectly okay to write manually rewrite rules for in my book.

Very nice. Cufon is a it of a bummer, but let me guess … corporate font not available as a webfont? Also nice to find out that DAU actually translates. I always thought is was a German-only acronym.

Well, at least the blog system which was used before on this site uses URLs like this (if you don't use mod_rewrite). And they work. Okay, so I'll have to use mod_rewrite for that after all. Thanks, Ryan.