neildaemond

I think this is an effective design for a dentist! Makes me think he's very neat, tidy, and professional. lol, he can't change the impression his name gives people, but having a nice website can't hurt at all!

I like how you made the blog for him, and especially that he's actually using it.

Oh, I forgot to mention one thing: If you guys are curious, you can test the uploading form until the end. The inserted data will be discarded if there's no video upload.

edit: very nice site @panictree

phew~ I was curious and clicked through using gibberish, pressing that final 'next' button inadvertently...

But I have to say about the site... I LIKE IT!

A simplistic and corporate site for a newly started, but very experienced, insurance brokerage.

This is just a very basic starting point. The site will evolve as the company matures and grows.

Was my first time using grids (semantic.gs) and LESS, unfortunately its not yet responsive.

ccw-global.com

I wanted to see if it is bad that both mydomain.com and mydomain.com/ return a 200. I did a bit of research and saw this on the google blogs (http://googlewebmastercentral.blogspot.hk/2010/04/to-slash-or-not-to-slash.html):

"If both slash and non-trailing-slash versions contain the same content and each returns 200, you can:

- ...

- Rest assured that for your root URL specifically, http://example.com is equivalent to http://example.com/ and can’t be redirected even if you’re Chuck Norris."

and according to sections 6.2.3. in rfc3986 (http://tools.ietf.org/html/rfc3986), which defines how uri syntax works, the following are the same:

http://example.com

http://example.com/

http://example.com:/

http://example.com:80/

So, I'm happy with the default behavior of PW since its consitent with slashes on the pages. The root url doesnt matter if it has a slash or not.

hmm.. just tried http://www.seoconsul...m/tools/headers

going to mydomain.com or mydomain.com/ both returned a 200

going to mydomain.com/about-us returned 301

going to mydomain.com/about-us/ returned 200

.... if you hacked the core to remove the trailing slash, would the results be reversed?

so maybe just being consistant is important? It seems that its more common to have the trailing slash then not, however~

edit (more thoughts):

if both mydomain.com and mydomain.com/ return a 200 code, is that a bad thing because that means there is two pages with duplicate content? My guess is that its better to have one redirect to the other, no?

Today an SEO expert told me to make all the urls have a trailing slash. With a bit of research, I found out that NOT having a trailing slash is a BAD THING for seo in general. Supposedly a trailing slash will give a 200 return code and no trailing slash will return a 301. I haven't confirmed if this is the case for PW, however.

This blog post talked more about it.

I'm finding this as well with clients who have started out by making their own sites with wordpress, or joomla. They are talking to you now because they can't get those systems to do what they want. They think that you can easily just modify current bloated sites but, we all know how UGLY that is because its not just the styling they want, its that they want their plugin to work differently. I'm sorry, but I can't make that third party code do that.

I try to emphasis that the features these 'click-to-install' modules/plugins have aren't useful to everyone and that with each feature they added, they made it harder for existing features to be adjusted. Usually, the more out of the box features, the less flexible. It will do what it advertises, but just that and its a mistake to try and make it do anything else if you aren't familiar enough with it. "it's Open Source" they say... well maybe, but probably with poor documentation and coding style, otherwise I (or any of the other "wordpress" developers you already talked to) would be able to modify it no problem.

I've noticed some horrible workflows for people who use multiple modules and plugins... import this, export that... yada yada. I tell them straight up that all they should have to do is add a page, give it a name (which is the url) and fill in the blanks. Anything more and they are taking time away from their own business processes.

So, if you are able to specify the client needs well, then after DIY you will be able to give your client something much more efficient and effective.

I'm still wondering about PW site profiles and am curious as to how it will effect things.

cool, I've never considered this ken burns effect before... looks pretty nice.

Hey, the art is better than anything I could draw~ But it DOES give me a bit of a clip art feel, perhaps photography would be more effective? Works well as icons though.

I think its good you help write copy... I'm just starting out, and copy is where project flow really suffers a lot of variance depending on the client~ I'm looking to better that process

Also, I noticed a little typo:

"who has been in the advertising, marketing and media world for thrity five years"

well, don't worry if your php is minimal, with PW you can get pretty far with just knowing how to:

1) set variables:

$variable = whatever;

2) echo:

echo "any text, but usually html like <div> stuff in my div </div>";

echo $page->body;

3) using foreach:

foreach ($pagearray as $oneofthepages) {

echo "<div>{$oneofthepages->body}</div>";

}

just those with the api will do great things for you, my friend

I have mini version of the contact form which will be on most pages, and instead of putting the processing logic on every page, I thought I'd just post to the contact page and process it once there.

for some reason my contact page isn't receiving it. I probably just have a bug in there~

I read it before but, now I can't remember. How do you post to pages other than the current ( other than using action="./" )

do you post to the template? or page? I'm trying something like:

action="./othertemplate.php" and it gives me page not found.

If you just empty the fields inside the repeater and save, then the repeater item is still there. Press the little trashcan in the top right of the repeater item and the whole item should get deleted.

I emptied the fields and saved the other day and then blank items were still on my page~ until i deleted the item with that trash can.

if logo is an image field, then by default it is an array of images. In the field settings (details), you can change the max number of images from 0 (unlimited) to 1, and this will make your 'logo' field into a single image instead of an array. For the array, you'd have to grab the first image by:

$logo = $page->logo->first();

or you can get a resized version with:

$logothumb = $page->logo->first()->width(100);

or

$logothumb = $page->logo->first()->height(100);

-> 100 being the pixel size

Then, to output that logo, you can do something like:

echo "<img src='{$logothumb->url}' />";

If you set your image field to max 1 image, then you can skip the first() step and just use:

$logothumb = $page->logo->width(100);

and maybe even just do it all at once with:

echo "<img src='{$page->logo->url}' />";

or

<img src="<?php echo $page->logo->url ?>" />

see more info here:

http://processwire.com/api/fieldtypes/images/

I took the queries used in skeleton css I also took their base for normalization and to fix the typography.

Their limits seem to be nice but, I still have to figure out how to properly modify the css within them though~ I'm hoping that using LESS I can adjust some variables and that can have the proper effect on the page~ havn't gotten to that point yet though, haha

I found this thread a bit ago and was like "oh, css framework? whats that? LESS scss? what?..."

I spent the next few days getting blown away with thoughts of being uber productive from then on, after installing and testing the full customizable verisons of bootstrap and foundation. I was conviced that foundation was going to make my life a breeze ( i too favored the orbit script, and the modern style). However, I was doing a very specific and custom design and I jsut couldn't mold it to do what I wanted to. the scss code behind it really is huge, and its only easy to change the basic options. I scrapped the whole thing and rewrote it. plus I was waiting quite long each iteration to let compass recompile.

I think the bulkier tools have their place with utility sites and web applications, but for a site focused on company identity, it seems too cookie-cutter for my liking. I resorted to using LESS with semantic.gs grid system. Its a very basic grid system, but allows me to control thing more with css, instead of too many classes in my xhtml.

I think I like having more control over my tools, and thats why I like PW. Its kind of like the new lego... sure the starwars models look cool but, those giant peices used in a ship will only ever make another ship.

What if every time PW made a change to the database schema, afterwards it asks if you want to record that change. Then PW could ask you to add this change to a 'batch' or create a new batch to add to.

while each batch would represent all the changes made in the new site version, on the server each 'batch' could be a folder containing the php scripts which implement the same database schema changes, in the same order (by date/time).

run those scripts on the production site and you should be caught up.

[edit: well, I guess the content won't be caught up. But at least things like fields and modules and stuff. Page content would still need to be added to the live site. maybe a 'save and record' button when editing a page? ]

would something like that be implementable?

I can't understand the language but, I really like the google map header idea! I just had to click it and shake the world around a bit

The fact that such a discussion can take place here so naturally is one of the many reasons I find ProcessWire so good. What you are all discussing here is what one could call "good general practices" for deploying any site. However, in other CMSs, when you ask such a question, you get the general information then you have to go further and say, "OK, now how do I do this in [name] CMS?" With ProcessWire, what I really like is that the answer is simply the answer, and not "Here's how you need to do it in ProcessWire."

This principle seems to extend all the way through ProcessWire -- from templates to JQuery, and more. It's one of the principles that I find very appealing about the system

The Processwire community is indeed very awesome. I wouldn't be as inclined to ask this kind of question any other place, but I know that here I would get reasonable and helpful suggestions.

Processwire seems to attract these kind of respectful and helpful developers. I guess it's easy to help out when the system isn't driving you mad. I love the fact that the more I learn about web development in general, then better at Processwire I get, and vice versa. They go hand in hand, and that IMO is what makes a great CMS/CMF.

I have been thinking a lot about building our own "starting profile" (we kind of have one already, but that is not well build). Something more "out of the box" for our clients. That thinking also has some merits - especially if there are lots of sites and multiple people working (also on different areas, like customer support, developing, sales etc). More feature packed default site is easier to demo and sell, easier to maintain if there is lots of similar sites, easier to provide support (technical and helpdesk), easier to write instructions etc... What I am doing (hopefully this year) is to build site profile where would be the most common needs baked in already. What that would mean in our case (we build websites for Finnish associations) are:

• News section
  
• Events section
  
• Contact section
  
• Few different "basic-page" layouts
  
• Blog (maybe)
  
• FAQ-section (maybe)
  
• Tiny "intranet" section (maybe)
  
• Frontpage highlights
  
• Few editor roles
  
• Some useful modules already installed (redirects, adminbar, link helpers, admin helpers)
  
• Using more robust template approach
  
• Responsive by default
  

I hope that it won't take too long that we start to see more and more community driven "starting profiles" like Ryan's Blog profile. There could be things like General CMS profile (kind of what I am doing - although not sure if it will be general enough to share it) and E-commerce site (kind of what here is coming) etc..

Even your first starting profile is already helpful to me, saves me the time of ripping all the fields and templates out before I start a fresh project. Profiles with what you listed will be nothing short of amazing.

I've been away from PW a bit, and am pretty excited to give 2.2 a whirl~ especially the user system.

I hope that I can help out more in the future as I am now using it quite heavily in my business. I'm going to do a more in depth study of the php behind it before I start making modules or profiles. As I work through it, I think I may see stuff which could use further documentation. If I do, how could I help out with that?

First of all, don't worry too much, you will normally find all the problems after launching

haha, yes.. I probably will.. sigh~

But, thanks a million, you guys covered all of my check list and added the following good points to it~ The redirects, user testing, validator, yslow, and pingdom are especially good ones. That xml sitemap module has to be one of my favourites.

and, if it's a port of an existing site to PW then Antti's Redirect Module (http://modules.proce...cess-redirects/) saves loads of time.

Then it's a matter of checking that all your <title> and meta description are all populated with appropriate info, and I also make sure that the html validates. A few small things add up to a significant advantage.

And, if you're in any doubt, a bit of user testing. A handful of users is enough to make a significant difference - http://www.useit.com...x/20000319.html.

Here are some of the things I try to do before launch :

- Check the page titles and meta descriptions. Install the Google webmaster tools to get more useful advice on how to optimise the site for search engines

https://www.google.c...ebmasters/tools

- If this is the an update of an existing site, setup redirects for old pages to new pages - you can check what old links are currently indexed by Google and start with the top ones. The redirect plugin is great for managing this (http://modules.proce...cess-redirects/).

- Check and update the 404 error page

- Check that all your forms are working and being delivered to email recipients (not stuck in spam).

- Check what print layout looks like (or make print style sheet)

- Check for broken links and correct redirects. http://validator.w3.org/checklink

- Performance testing - you might want to check for any big performance issues. ySlow is a nice tool for checking and provides some good tips that might be useful for speeding up the site. Don't be too disheartened by the results, not even the big sites get top marks.

http://developer.yahoo.com/yslow/

- Setup monitoring so you know the site is up and running - I really like pingdom.com - https://www.pingdom.com/

Then I like to say a little website launch prayer… "dear internet gods, I know things will go wrong but please let the issues be small and easy to fix. amen."

Thanks to Processwire, I've gotten the confidence to start charging people for my web development and have recently started a web dev business.

Although I'm not too artistic, the flexibility of PW allows me to accomodate the design of any artist I am working with and the API gives me to power to do the fun backend stuff.

Anyways, before I deploy some sites for production, I wanted to ask the more experienced developers out there what kind of steps they take at the end of a project to make their sites 'production ready'.

For example, do you guys combine all your js and css files? do you change any Processwire configurations?

Hearing any tips from you all would be of great help to me.

Thanks in advance

Very nice design. Thanks for showing me ecwid as well, I should definitely give it a try~

ok, I'm so sorry for wasting your time... it is a really simple setting.

my new pages made by inputfield were put under the parent 'tags'.. so in the admin tree, I just needed to click tags > edit > children... then there is a sort setting there.

I never knew that setting existed, another win for PW usability.

Thanks Ryan~!

I use this feature to makes tags on my site. However, now that I have more tags, these checkboxes are listed in chronological order and become hard to find. It would be nice if they were in alphabetical, or if I were able to choose how they were sorted.

maybe PW 2.3 could add a feature to sort all child pages when listed in the admin (when there are many it becomes hard to move them all around one by one).

Its nice to know there will be some interest... it will also be my pleasure.

But, seriously don't expect anything very soon or too frequent~