Inform: The website will let everyone know what Visions is and how to get involved in a more assessable way.
Entice: The website has to be informative, but it also has to look good at the same time. The aesthetic has to make people want to be apart of Visions6.
Archive: Having a Website will also allow for a online archive of Visions past so that everyone can see/understand Visions in terms of what its history.
2. Who is the customer?
The customer is anyone and everyone that needs/wants to be connected to Visions. This includes filmmakers, film enthusiasts, film students, sponsors, and pretty much anyone really. The core of our customer base will specifically be filmmakers 18-25 who live 2-4 hours within Wilmington.
3. What are the deliverables of the project?
The final product of this project will be a fully functional website.
4. What is the budget?
The website provider Squarespace costs 18$/month plus the amount needed to keep the website domain.
5. How long will it take?
I have predicted that it will take about a month to get the website up to a launching point, just in time for the Call For Entries starting date. It will about another month to transfer previous Visions Conferences and other information such as staff bios, FAQs, ect. It will take until March for final touches to be made to the website such as the Schedule and Film lists.
6. What specific skills are needed?
Website Design: The person making the website will have to be/become familiar with the design structure of SquareSpace.
Asthetic: It is also important that the website reflects V6 and is consistent with the overall theme and design of V6.
7. What special resources are needed?
The website maker will need access to the Visions 5 website so that they can transfer information. They will also need to compile other aspects needed for the website such as schedule information and staff photos/bios.
8. Who is working the project? What is each person's job?
I, Michelle Glahn, am handling the websites creation and design. Other information for the website will be gathered from other team members (ie. Sponsorship Info from Adrienne).
9. What is the schedule?
The plan is to launch a function version of the website by Call for Entries, so that submission and other basic info can be accessed by those interested in the conference. As more information becomes decided and relevant, it will be added to the website over the span of time before the festival (ie. we cannot determine the schedule until we have decided on films; we cannot post the film list until all films have been submitted).
10. What are the risks? (Small vs. large impact, likely vs. unlikely)
Small Large
- website is difficult to navigate, harming festival attendance/message clarity
- not very likely because we will actively check on website to make sure its functioning well
- website is hard to update quickly due to mass amount of information needing updating
- this risk is definitely possible, but I will ask for help from my team or any team with breathing room to assist in updating the website in order to avoid this issue
11. How will you communicate with your team?
I am in constant communication with my team via a group text. However, we also have Google Calendar, Trello, and Facebook for reaching out and making my team knows their tasks.
12. How will you determine if the project is successful?
I will determine if this project is successful if festival-goers are easily able to use the website (we could look into sending out a survey after the conference). I will also consider it a success if its artistic design is consistent with the entire theme of Visions6. I would also consider how many hits the website received and compare that with years previous to see if Visions presence has continued to grow.
No comments:
Post a Comment