Posted On March 9th, 2011 Author Kyle Racki
Filed Under Business, 22
Back by popular demand, I am happy to present you with the second edition of the ExpressionEngine client guide. It is an attractive PDF instruction manual that developers can deliver to their clients as a handy reference for basic administrator functions of EE.
The original ExpressionEngine client guide was extremely popular, so I’ve decided to update it with new screenshots and information applicable to ExpressionEngine 2, released in 2010. In addition to supplying the PDF with Headspace branding, there is also the InDesign CS4 file (and CS3 Interchange) with linked images, so you can rebrand it till your heart’s content. I couldn’t include the font files for obvious legal reasons, but it uses mostly Helvetica Neue anyways.
I’ve included references to third party add-ons that I regularly use in almost all of the EE sites that I build. Some of these included Structure, Freeform and SEO Lite to name a few.
Download the ExpressionEngine 2.1 Client Guide
EE2 PDF Guide | ReBrandable InDesign CS4 Files
Screenshots
Table of Contents
What is ExpressionEngine? 3
-
Overview of ExpressionEngine
Logging in 4
-
How ExpressionEngine works 4
-
Your login information 4
-
The control panel home page 4
-
YOUR LOGIN INFO 4
Creating and Editing Content 5
-
Publishing Entries 5
-
Editing Existing Entries 5
-
Deleting Entries 6
-
Structure Pages 7
Entry View 8
-
Titles 8
-
URL Title 8
-
Custom Fields 8
-
Content Editor 8
-
Content Editor 9
-
Placing images and PDF files in their own custom field 10
-
Placing images and PDF files within text fields 11
-
Multi-relationships 12
-
Tags 12
-
Date 13
-
Structure Pages 13
-
Revisions 14
-
Options 14
-
Categories 15
-
SEO Lite 16
Comments 17
-
Viewing 17
-
Editing 17
-
Deleting 17
-
Banning 17
Multi-lingual sites 18
-
Phrases 18
-
Custom Fields 18
File Manager 19
-
Directories 19
-
Viewing Files (Sorting) 19
-
Editing (Crop, Resize, Rotate) 20
Form Entries 21
-
Entries 21
-
Email Templates 21
Editing your account 22
-
Changing account details 22
-
Customizing your control panel 22
User and Member Access 23
-
Viewing and Editing Members 23
-
Registering new members 23
-
Activating Pending members 23
-
Editing Profiles, changing group 24
-
Banning members 24
Backup and Upgrades 25
-
Backing up your site 25
-
Updating to the latest version 25
-
Development and design changes 25
Under the hood 26
-
Templates 26
-
Modules, Extensions, Plugins 26
-
Other developers 26
Posted On January 9th, 2011 Author Kyle Racki
Filed Under Business, 4
I once heard that it’s not young carpenters who accidentally chop off their own fingers, it’s the ones who have been doing it for 20 years. They’ve gotten far too comfortable wielding spinning metal blades.
One of the ways individuals and companies often try to differentiate themselves is with experience. “I’ve got 15 years experience.” “Well, I’ve got 18 years experience!” In general prospective clients and employers value experience more highly than anything else, almost always willing to pay more money to the person with the most experience. But is this really the most valuable trait you should look for?
The funny thing is, when it comes to anything web related, experience is a completely null commodity that gets confused with some sort of winning attribute. Let’s face it, everyone except children have been using the internet for the complete 15 or so years it’s been mainstream.
But more to the point, if you are a web designer, developer or in any other way a web professional - having 15 years experience is not incredibly impressive. The internet sucked back then. The internet will always suck when referred to in past tense because technology improves at a breakneck speed. So really, even websites that won prestigious awards when they launched 5 years ago are a joke by today’s standards. And wicked awesome sites that launch today will suck 5 years from now because the sites of tomorrow will be doing far more impressive things with technology.
This isn’t like music, film or even video games, which are a completely artistic endeavor and can be great no matter when they were made. Citizen Kane, The Beatles and The Legend of Zelda are all amazing in their own right, even though they were made long ago relative to their medium. Great websites, except for the rare few, are business vehicles in some way. They may deliver their functionality in an artistic or creative way, but they still are there to serve a purpose other than art.
What that means for web professionals is that if you want to be considered the best in your craft, you need to be constantly learning. You can’t put self-education on the back burner because you’re too busy working on paid client projects; The fact is you won’t be busy in the future if you aren’t learning now.
This means that we are always in a state of feeling like a dinosaur - it’s our job to. Even if your skills are on par with what’s being done today, there’s always some new technology right around the corner that others are discussing. We should always have at least one topic in our given field that we know we need to follow via a blog or book.
The problem with experience is that it gives professionals a false sense of security. The amount of years you’ve been doing something occurs naturally as the Earth moves around the Sun. You have 11 years of experience because another year passed and you haven’t changed careers. It’s like running downhill. But to stay good at something - that requires more. You can have 15 years of being a crappy web designer, or 3 years of being an amazing one. Which would you pick?
In a past job, someone remarked, “I’ve been doing this since you were in junior high school!” My reaction back then was an unspoken “Who cares”, and it still is. The question is; How long have you been doing it well, and are you still doing it well? The latter one is the only one that matters. Mark Zuckerberg was 19 when he launched Facebook, he’s 26 now. Suffice to say, experience in his case is irrelevant.
It’s easy for me to get a big head and think that because I have been working as a design professional for over 7 years that I am some sort of guru. But all it takes is a look outside at all the people in the world who are truly shaping the web with technology and practices I have no clue about, and it brings me back down to reality. Guru is a very relative term.
At the very least, I want to be sure that even 2, 5, 10 years from now, I will never look down on someone with less experience. If I don’t keep my knowledge fresh, they will be running circles around me. So If you are someone who hires web professionals, don’t be impressed with the number of years on their card. Be impressed with what they can do now and hire based on that.
Posted On December 30th, 2010 Author Amy Wheaton
Filed Under Business, 2
Anyone who knows me well knows that I’m obsessive about timelines, not just at work, but in my personal life too. I set deadlines for everything from my gym schedule to cleaning our house. Bordering on crazy? Maybe – but my work experience has taught me the value of time management, and this is the system that works best to make sure I get everything done.
One of the biggest problems that can arise working on any creative project, online or otherwise, is when people don’t recognize of the value of time. The end deadline is looming – website launch, campaign in market, or gala event scheduled - yet milestones are missed. Everybody starts getting anxious. In the case of an online project, the developer can’t start working on the website back end because the design isn’t approved. Everybody’s work is delayed. Before you know it the project is off the rails, team members are on edge, and the site launches late. The project wraps up, and everyone’s left with a bitter taste in their mouth. How can this be prevented?
It’s easy to stay on track with a little bit of effort and a few tricks. Here are some simple ways to ensure your project goes out the door on time:
Set a realistic end date.
It seems obvious, but often clients will push to have their site launched by Date X without thinking about realistic turnaround times. It’s almost always better to wait and launch later with a good product than to cut corners to meet an unrealistic deadline. Anything worth doing is worth doing well – and to do anything well takes time!
Really review your timeline.
Overestimate on everything. I once read an article that said you should add a 50% contingency to every task – for example, if you’re expecting something will take two days, expect it to take three.
Build in buffers.
Anticipate that feedback is never going to be instant. Look at your responsibilities and their assigned dates and ask yourself if you can commit to this time frame. If you have any doubts, speak up! Better to adjust the timeframe before you get started than to miss milestones and throw the project out of whack midway through. No one will fault you for building in extra time!
Communicate.
If a red flag arises speak up immediately so the problem can be addressed before it snowballs out of control. Say you’re suddenly swamped and you aren’t going to have time to pull content together until next week – as long as you communicate that to the rest of the team, everybody’s aware of the situation and not wondering where in the world your content is. They may be able to move on to another area of the project and keep things on the rails overall. And even if everything is on track, make sure the team is aware of it – regular status reports on any project are helpful and reassure your team that things are rolling out as they should and that everyone is doing a good job.
Keep track of all responsibilities, using whatever system works for you.
At Headspace we use Basecamp project management software, which is great because it makes everyone accountable to a project and keeps the entire team updated on progress. For my appointments I use a good old-fashioned day planner, and I write down meetings, conference calls, and deadlines. As antiquated as it sounds I hate electronic calendars, and I usually ignore alerts that pop up, so for me they’re completely ineffective. Figure out what works for you and use it.
Give yourself fake deadlines.
I know that creative teams hate getting ‘fake deadlines’ from account people so I never assign them. However, fake deadlines work for me! If I need to have a block of copy written by the end of the day, I’ll try to have it done by noon. That way, if something does come up that’s unavoidable, I have extra time built in to get it done.
Build in lots of time for testing.
At Headspace we have started incorporating more time on our interactive projects for quality control and testing pre-launch and it makes a big difference in our clients’ satisfaction. Again, anything worth doing is worth doing well. It’s easy to underestimate testing time but this is one of the most crucial phases of a project. There are inevitably going to be bugs and errors with any website – better for your internal team to find them than your client!
Any other ideas for ways to keep a project on track and delivered on time? Feel free to share.
Posted On October 29th, 2010 Author Amy Wheaton
Filed Under Business, 6
As I rushed to get a design proposal out the door on time recently (why are these things always a rush, no matter how much lead time we have?) I was stopped short by an intimidating list of mandatory to-dos, listed under a bolded, ominous warning that “Failing to complete the following may result in your proposal being rejected”.
Well, um, OK. I guess I better comply, since we’ve just spent 30-plus hours of otherwise billable time getting this beast together and it would be a shame to lose out on this contract because I didn’t print the RFP number ABOVE the RFP name on the cover page. Or photocopy our business registry information double-sided. Or have page three of each of the 19 identical bound booklets signed, in black ink, by someone who is qualified to sign on behalf of our company – but DON’T sign the original copy, which, by the way, needs to be unbound and calligraphied on ecru (NOT WHITE) onion-skin paper and delivered on the horn of a virginal male unicorn at precisely 4:00 P.M. on Friday, October 22, AND NOT A SECOND LATER!!
I don’t think preparing and submitting RFPs will ever be fun. Don’t get me wrong. I don’t think the process is supposed to be fun. Potential clients need to know that you’re willing to put in time, effort, and precision on responses to their RFPs to show that you’re serious about working with them. With this comes a degree of challenge – locating the most appropriate work samples, ensuring your proposal is tailored specifically to their individual requirements, proofreading it again – and again – and again. RFP does not stand for “Ridiculously Fun Project”. Really f-ing painful? That might be more accurate.
The purpose of an RFP is to evaluate an agency or a firm on its ability to work with and on behalf of your organization. Whether it’s specific to strategy, design, account management, or a full suite of services, it’s a company’s chance to check out your expertise, your references, samples of your work, and the qualifications of your employees and determine which agency is best for their needs. It’s an opportunity to see how well a firm can answer your questions and respond to your unique objectives.
Fair enough – but why the need to make agencies jump through hoops, write out the gazillion-digit RFP number again and again and again, sign here and here and here, and so on to prove they can do great work? Worse still, the RFP documents that list their mandatory requirements on different pages, causing no shortage of angst as the unlucky account person (me) riffles through a novella of background info and appendices to make sure everything has been done correctly.
There are some RFP documents we receive that are just beautiful. I may actually clap and bounce up and down when I see them. They’re clearly laid out, with the mandatory requirements all in one place, straightforward questions, and contact info prominently marked. My secret inner dork actually enjoys completing these proposals – I could even go out on a limb and says that they are, indeed, ‘ridiculously fun projects’. (Then again, making lists is one of my spare-time hobbies, so my definition of fun may not be akin to that of a “sane and well-balanced person”.)
Before you send out your request for proposals, give it a review. If your requirements are responded to correctly, will you have the information you need to review sufficient samples of an agency’s past work, their unique approach to your project, and their team’s credentials in relation to your project? Are you determining that they are indeed a legitimate and established company without requiring fingerprints, criminal checks, and blood type of all team members? If so, you’re on the right track. Would you pull your own hair out by the handfuls if you had to respond to the same document? If not, go ahead and hit send. (Send it to us, actually. I love ridiculously fun projects).
Previous Page Next Page