Wondering what the process is for getting an OPLIN Website Kit? Details, below:

1. Phone conference. The process starts with a phone conference, generally between OPLIN and one or perhaps two contact people (see How to Make Your Website Kit Process Easier for more information about Website Kit liaisons).  We will send you a list of questions to consider beforehand. We'll discuss what you like (or don't like) about your current site, and what you'd like in a new one. You'll be asked to choose a design template. We'll also make recommendations based on your needs and goals.  
2. Cost estimate.  After the phone conference, OPLIN will send you an itemized cost estimate for your project, based on what was discussed in the initial phone conference.  You'll be asked to review and to note any changes. 
3. Contract.  Once we have a finalized cost estimate, your library will be sent an official contract. When we have received the signed copy, work on your new Website Kit will be in earnest.
4. Site architecture.  We'll put together a site architecture, which will  map out the hierarchy of your content, based on the phone conference and on the site's existing content.  We'll then ask you to make revisions (such as removing pages no longer used or re-arranging the order of any pages).  OPLIN will review your proposed changes for any potential usability issues. Once we have something we're all happy with, you'll sign an Architecture Approval form. Keep in mind that any changes requested to this architecture,  after signing,  will incur additional charges, with a minimum charge of $150.00.
5. Design. Based on the specifications laid out in the phone conference and the approved site architecture, OPLIN creates a design prototype (mockup) of your library's site, using your chosen template.  We allow up to three drafts; that means that, after the original version, you'll have two (2)  more drafts available for tweaks or changes.
6. Construction.  This is when OPLIN actually builds your site. 
7. Review. When the site build is nearly complete, we'll send you a link to it on a test server to look at, and ask you to fill out an approval form for various design elements. Any issues should be noted at that time.
8. Training. When  all design regions are fixed and approved, we'll schedule training for you and/or your designated staff. The training will cover how to input various types of content, as well as any administrative functions native to the site. Training typically takes approximately two (2) hours; we allow up to three (3) as part of your project. 
9. Launch. Launch occurs when you tell us that all necessary content has been migrated to the new site.  OPLIN will will work with your library to manage any DNS changes for domains related to your website.

How to Make Your Webkit Process Easier

1. Ditch “design by committee.” As tempting as it is to have a team of some sort, in our experience, this almost always leads to either delays and/or disasters. You can never make everyone happy! Feel free to gather your staff’s input prior to your first phone call with Laura, but we strongly recommend that only 1-2 (MAYBE 3) people from your library should be involved in the actual phone conference. Because it is difficult to please everyone, typical Web Kit projects that are managed by committees tend not to only run longer, but can be more expensive because of constant revisions. To save your library time and money, designate 1-2 people to be in charge of the process and who can step in to make a decision as needed.
    
2. Remind your staff/board who the site is for. In our experience, library staff or board members don't always recognize that the primary (and only) audience for a public website is the public! Attempts to include resources specifically for the reference desk or to organize content just so it’s easier for the staff will generally be opposed by OPLIN. Remind your staff, when seeking input, that patrons not only come first, but are the entire audience for your new site.
    
3. Filter the input from your staff. If you are collecting suggestions from your staff, please filter the list (or have your designated liason/leader do so) to just those things that are things you would actually consider. For example, if a staff person suggests that the site should primarily be orange and the library’s branding scheme is primarily blue, remove this from the list. It will save a great deal of time for everyone involved.
    
4. Changes to an approved site architecture will cost money.  The site architecture is typically the first step in planning your new Webkit. Once your library has signed off on that, any changes will incur additional charges, at the custom work rate.  Keep this in mind when you are looking at the first design draft; changes to the top level navigation or side blocks, for instance, after the approval was already signed, will increase your library's cost.  This is why it is important to make sure you're happy with the architecture, before you sign it.
    
5. Remember that your library gets three (3)  design drafts—total. Although this is almost always mentioned in the initial call with OPLIN (and is on our website, too), it’s worth mentioning again. As part of the standard Website Kit, your library gets 3 design drafts—total. Beyond that, the custom rate is charged per hour of work. Asking for a sample website in your color scheme will be counted as one of the drafts, as will any tweaks requiring the creation of a new image. If you’re not sure what will be counted, please ask! We’d much rather save you the money.
    
6. Don’t use print copies of the design drafts to make decisions.   When you get a design prototype from OPLIN, it can be very tempting to print it out to show to other staff. However, most printers automatically scale things to fit the paper. This means that you will not see it in the same way you will see it on a computer monitor. Be sure to pull up the .jpg OPLIN sends you in a browser so you can see it on your monitor!
    
7. Understand that part of OPLIN’s job is to educate. We focus strongly on current best practices in usability and accessibility, as well as site navigation and site design. If we veto something, we’ll always explain WHY and often provide you with third-party resources where you can learn more about current standards.  
    

The OPLIN Webkts depend on a standardized software installation and design template that allows us to keep the cost low. We do offer limited customization, but some changes "break" our standardized model. For example:

• Changes that require modifications to a Drupal module or the Drupal code;
• Changes that require any special server configuration;
• Changes that require custom scripting that accesses web resources outside of OPLIN's control;
• Requests for designs beyond the templates that OPLIN provides.

When a library customer requests such changes, we suggest that it consult with an outside vendor.  OPLIN is not able to accommodate these types of development needs.

Webkit Manual

Welcome Packet