Magner Dealer Website Design

Administrative Details - Our Client

Name of Client: Magner Corporation of America
Contacts: Diane Taylor, CEO; Doug Magee, CFO

Location and Maintenance

This site will reside on the Atlas Hosting server with the current Magner website, www.magner.com. Kristen Taylor will maintain this website.

Purpose and Goals

The intended audience of this site (which will be password protected) is the dealers of Magner Corporation of America. The purpose of this site will be to provide Magner's dealers with a comprehensive source of information. This website will allow dealers to easily place orders and access important information about the machines they sell. It will also allow Magner to get feedback from the dealers via the comment form. In addition, the dealers will be able to keep up to date on all current training sessions available as well as be aware of important trade shows that Magner is participating in.

Content

Overall Design: Because we are linking to another page that is already complete we have to make sure that our page meshes well with the existing one. We will be working closely with the client throughout the design process to be sure that the sites we have created look exactly as they want, so there may be changes to the overall design while we are working on the site.

Page Layout: The overall layout design will be similar, with the Magner logo at the top of every page and a list of links (as buttons) down the left side of the page. (see www.magner.com to get more of an idea of how we want the site to look. The major difference between the existing layout and the layout we want to create is that our page should take up the entire screen, whereas the existing page is confined in the middle.) We will use CSS to create the layout of our page.

Color Scheme: In regards to the color scheme, all of the text will be black and the headers will be green. Unvisited links should be black and visited links should be dark green. Bold and italics will be used throughout the pages as necessary.

Home Page: The home page (index.html) is the first page that will be accessed once the dealer logs into the site. This page will have a welcome message with a little information about the website and its uses as well as room to put links for new promotions, messages, etc. that will be updated regularly. The "Welcome" header at the top of the page will be an animated graphic.

Links on Left: The links will be the same list down the left side of every page. They will be featured as buttons with green background and white writing that turn into white with green writing upon rollover. (These should be very similar to the buttons on the www.magner.com website.) The links will be in the following order:

  1. Current Promotions (promotions.html)
  2. Place an Order (orderform.html)
  3. Sales Support (salessupport.html)
  4. Service Support (servicesupport.html)
  5. Training Schedule (training.html)
  6. Trade Show Schedule (tradeshow.html)
  7. Comments (commentform.html)
  8. Dealer Home (index.html)
  9. Magner Home (http://www.magner.com)

Navigational Structure: Using the list of links above, our site will have somewhat of a clique structure for navigation. However, some pages (such as brochures.html) are not listed on the left of each page, but rather are accessed through a page listed on the left, so it is not completely a clique structure, but more of a clique with some sub-trees.

Goal: Allow dealers to place orders. In order to meet this goal, we will create an order form (orderform.html) for the dealers to use. The form will include the following inputs:

The form should create an e-mail to be sent to bdonahue@magner.com that includes all of the above information in an easily readable format.

Goal: Allow the dealers to submit comments. In order to meet this goal, we will create a comment form (commentform.html) with the following inputs:

The form should create an e-mail to be sent to both bdonahue@magner.com and dmagee@magner.com that includes all of the above information in an easily readable format.

Goal: Allow the dealers to view and download PDF files of brochures, both for printing in house and for e-mailing. The brochure files will all be located on one web page (brochures.html) and organized by machine type. Whenever possible, each brochure will be available in both print-quality and web-quality sizes. (This is not indicated in the plans with the file names below as we don't yet know which brochures will be available in both formats). All brochure files will be uploaded from the Magner server onto Puma into the correct file. The page will display a thumbnail of the machine with a list of links to the available brochures.

Goal: Allow the dealers to access generic proposals. To meet this goal we will create a web page (proposals.html) with links to generic proposal formats, organized by machine types. These proposals will be in word document format so that the dealers will be able to download and edit them.

Goal: Allow the dealers to access PowerPoint presentations designed to help them present the machines to the customers. In order to meet this goal we will create a web page (presentations.html) with links to the current presentations available. At this time there is only one presentation, a general one for all the self-service machines, but over time the client will create more and would like to add them to this page.

Note: We will create a web page (salessupport.html) with links to the proposal, brochure, presentation, and training and trade show schedule web pages so that the site can be more easily navigated.

Goal: Allow the dealers to view service-related documents. From this webpage (manuals.html) they will be able to download service, set-up, parts, and user manuals for many of the products they carry. Quick Reference guides, planning and installation guides, up to date Tech Tips, and various checklists will also be available for several of the machines. The documents will all be located on one web page and will be organized by machine type. A thumbnail of each machine will be on the page, along with the name of the machine and a list of links to all of the service-related documents available for that machine. All of the documents will be in PDF format and will be uploaded from the Magner server onto Puma into the correct file folder. The links to Tech Tips (for each machine) will be a link to another webpage with a listing, by date, of all the Tech Tips files for that machine.

Note: We will create a web page (servicesupport.html) with links to the training schedule and service-related document webpages so that the site can be more easily navigated.

Goal: Provide the dealers with schedules for upcoming trade shows. In order to meet this goal, we will create a web page (tradeshow.html) that lists all the upcoming trade shows as well as pertinent details (location, booth number, etc.).

Goal: Provide the dealers with a schedule for sales and service training. To meet this goal, we will create a webpage (training.html) with a list of upcoming sales and service trainings as well as the details for each training session (location, time, rsvp instructions, etc). This page will also include instructions on how to request that a training session be offered.

Goal: Provide certain dealers with access to price lists. Only some dealers will be able to access these files, as pricing is very confidential and many dealers have different, special pricing. There are three wholesale price lists: Magner, MAGII, and Self-Service; some dealers will not be able to access any, some will be able to access only one, and some will have access to two or more. Accessibility to these files will probably be limited using .htaccess files; however, after talking with Jennifer and Stella it became clear that we cannot determine this, nor can we include them in our file list, since we do not know what kind of server the site will be hosted on.

Plan

The files will be organized using the following folder structure and file names. The client is in the process of obtaining all of the files that we need from them so that we can rename and organize them ASAP. However, they do not have complete control over the timeline because they have to work with the designers of the brochures, the different machine manufacturers, etc. (Also, the list is not complete since lists of some of the files are still being compiled - for example, we do not know which machines have TechTips available at this time, nor are we sure which brochures will be available for which machines (as discussed above). Also, we are not able to make the files to protect the site and limit access to certain files within it because we do not know what kind of server the site will be hosted on. Kristen will contact the server administrator at AtlasHosting sometime before 12/4 so that we will have more information on this before we are done with the coding and we can do anything else necessary to ensure that the transition from puma to their server will go well. All changes to the file structure and name will be listed in our changes document.) Once we obtain the files we will have to convert them to PDF's, resize images, etc. as necessary. The html files that we have to create are also listed below; in parenthesis after each file that we have to create is a set of initials (either KT or JC) and a date, indicating the person responsible for each file and the date it should be completed by.


			index.html (JS,11/27) 

			magnerdealer.css (KT, 11/13; will be modified by both partners as necessary)

			orderform/
				orderform.html (KT, 11/27)
			
			comment/
				commentform.html (JC, 11/27)

			salessupport/
				salessupport.html (KT, 11/13 ) 			

			brochures/
				brochure.html (KT, 11/14)
				selfservice/
					709brochure.pdf
					726brochure.pdf
					524brochure.pdf
					
				magner/
					305brochure.pdf
					35-3brochure.pdf
					35brochure.pdf
					75brochure.pdf
					920brochure.pdf
					930brochure.pdf
				magII/
					100brochure.pdf
					110brochure.pdf
					20brochure.pdf
					20TMbrochure.pdf
					4in1brochure.pdf
					915brochure.pdf
			proposals/
				proposals.html (KT, 11/14)
				selfservice/
					709proposal.doc
					726proposal.doc
					524proposal.doc
					501proposal.doc
					514proposal.doc
					AdQueproposal.doc
				magner/
					305proposal.doc
					35-3proposal.doc
					35proposal.doc
					75proposal.doc
				magII/				
					100proposal.doc
					110proposal.doc	
					20proposal.doc
					20TMproposal.doc
					915proposal.doc
			presentations/
				presentations.html (KT, 11/21)
				selfservice/
					selfservicepresentation.ppt 

			pricelists/
				pricelists.html (KT, 11/21)
				selfservice/
					selfservicepricelist.pdf
				magner/
					magnerpricelist.pdf
				magII/
					magIIpricelist.pdf
				
			servicesupport/
				servicesupport.html (JC, 11/14)			

			manuals/
				manuals.html (JC, 11/15)
				selfservice/
					709/
						709setup.pdf
						709user.pdf
						709parts.pdf
						709quickref.pdf
						709planandinst.pdf
						709instchecklist.pdf
					
					726/
						726setup.pdf
						726user.pdf
						726parts.pdf
						726quickref.pdf
						726planandinst.pdf
						726instchecklist.pdf
				
					524/
						524setup.pdf
						524user.pdf
						524parts.pdf
						524quickref.pdf
						524planandinst.pdf
						524instchecklist.pdf
					
					501/
						501setup.pdf
						501user.pdf
						501parts.pdf
						501quickref.pdf
						501planandinst.pdf
						501instchecklist.pdf
					
					514/
						514setup.pdf
						514user.pdf
						514parts.pdf
						514quickref.pdf
					
					5800/
						5800setup.pdf
						5800user.pdf
						5800parts.pdf
						5800quickref.pdf
				magner/
					305/
						305setup.pdf
						305user.pdf
						305parts.pdf
						305quickref.pdf
					35-3/
						35-3servpart.pdf
						35-5operator.pdf
					35/
						35servpart.pdf
						35operator.pdf
					75/
						75servpart.pdf
						75operator.pdf
				magII/
					100/
						100servpart.pdf
						100operator.pdf
					110/
						110servpart.pdf
						110operator.pdf
					20/
						20servpart.pdf
						20operator.pdf
					20TM/
						20TMservpart.pdf
						20TMoperator.pdf
					4in1/
						4in1parts.pdf
					915/
						915servpart.pdf
						915user.pdf
				techtips/
					selfservice/	
						709techtips.html (KT, 11/21-all techtips)
						726techtips.html (KT)
						524techtips.html (KT)
						501techtips.html (KT)
						514techtips.html (KT)
						5800techtips.html (KT)
						AdQuetechtips.html (KT)
					magner/
						305techtips.html (JC, 11/21-all techtips)
						35-3techtips.html (JC)
						35techtips.html (JC)
						75techtips.html (JC)
						920techtips.html (JC)
						930techtips.html (JC)
					magII/	
						100techtips.html (JC)
						110techtips.html (JC)
						20techtips.html	 (JC)
						20TMtechtips.html (JC)
						4in1techtips.html (JC)
						915techtips.html (JC)
				schedule/
					training.html (JC, 11/29)
					tradeshow.html (KT, 11/29)
						
			thumbnails/
					709pic.jpg
					726pic.jpg
					524pic.jpg
					501pic.jpg
					514pic.jpg
					5800pic.jpg
					305pic.jpg
					35-3pic.jpg
					35pic.jpg
					75pic.jpg
					100pic.jpg
					110pic.jpg
					20pic.jpg
					20TMpic.jpg
					4in1pic.jpg
					915pic.jpg
					920pic.jpg
					AdQuepic.jpg
			

Minimum Requirements

Each of us will fulfill the minimum requirements as follows:

Kristen

  1. An animated graphic file, movie, sound, or an imagemap.

    This requirement will be fulfilled with a short movie regarding a machine on the website. At this time we do not have any more details about the short movie or where it should be located on the site.

  2. Two distinct JavaScript applications.

    This requirement will be fulfilled with (1) the form validation for the order form and (2) the creation of the rollovers for the link bar down the left of all the pages.

Jessica
  1. An animated graphic file, movie, sound, or an imagemap.

    This requirement will be fulfilled with an animation of the "Welcome" header on index.html.

  2. Two distinct JavaScript applications.

    This requirement will be fulfilled with (1) the form validation for the comment form and (2) the date and time display on index.html.

Created by: Kristen Taylor
Date Created: November 6, 2006