Website: Difference between revisions
No edit summary |
No edit summary |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
== Basic Department Description == | |||
Basic Department Description | |||
* Build, maintain and update the website and web presence of the convention for that year | * Build, maintain and update the website and web presence of the convention for that year | ||
| Line 28: | Line 5: | ||
* Staff Email is [[[email protected]]] & [[[email protected]]] (These are the forward facing “job” emails that get posted to the public and forward emails to your personal VF email. Your personal VF email is what you log in to and use to read and respond to emails.) | * Staff Email is [[[email protected]]] & [[[email protected]]] (These are the forward facing “job” emails that get posted to the public and forward emails to your personal VF email. Your personal VF email is what you log in to and use to read and respond to emails.) | ||
Yearly Responsibilities | == Yearly Responsibilities == | ||
* Sunday of the previous convention either the new or old lead should archive the previous website to the appropriate folder (example vancoufur.org/2016) and a splash page with the new theme should be put up in its place until the new website can be developed. | * Sunday of the previous convention either the new or old lead should archive the previous website to the appropriate folder (example vancoufur.org/2016) and a splash page with the new theme should be put up in its place until the new website can be developed. | ||
| Line 41: | Line 17: | ||
* MAKE SURE TO SAVE OUT A ZIP/COPY OF THE VANCOUFUR PUBLIC FOLDERS IN THE FTP AS A BACKUP. While the server usually has its own backups, this is a preventative measure in case something screws up. (The entire public folder, including older years, etc.) | * MAKE SURE TO SAVE OUT A ZIP/COPY OF THE VANCOUFUR PUBLIC FOLDERS IN THE FTP AS A BACKUP. While the server usually has its own backups, this is a preventative measure in case something screws up. (The entire public folder, including older years, etc.) | ||
Convention Website NEEDS | == Convention Website NEEDS == | ||
=== Design site to include === | |||
* Twitter feed | * Twitter feed | ||
| Line 50: | Line 25: | ||
* Countdown timer | * Countdown timer | ||
* MAKE SURE DATES ARE IN MULTIPLE SPOTS | * MAKE SURE DATES ARE IN MULTIPLE SPOTS | ||
* Html title code | * Html title code | ||
* Banner or header image | * Banner or header image | ||
* On home,hotel,reg pages! | * On home,hotel,reg pages! | ||
=== Needed Webite Pages === | |||
* [[Please read the Website Checklist]] (Contains Content and page checklists, procedures and more!)<sup>[[[a]]]</sup> | * [[Please read the Website Checklist]] (Contains Content and page checklists, procedures and more!)<sup>[[[a]]]</sup> | ||
Your Department on the Website/in the Conbook | == Your Department on the Website/in the Conbook == | ||
* Make sure departments give you accurate information when the submit it to you. | * Make sure departments give you accurate information when the submit it to you. | ||
* Any text the departments send to you should be audited and formatted to be interesting, easy to read and Search engine compliant | * Any text the departments send to you should be audited and formatted to be interesting, easy to read and Search engine compliant | ||
6 Months before con, what do you need to have done? | == 6 Months before con, what do you need to have done? == | ||
* All departments should have their opening times, you should have closed the first batch of registration prices and the website should fully developed. | * All departments should have their opening times, you should have closed the first batch of registration prices and the website should fully developed. | ||
* All pages should be populated with information. If you have no content for a page, disable it from the navigation | * All pages should be populated with information. If you have no content for a page, disable it from the navigation | ||
3 Months before con, what do you need to have done? | == 3 Months before con, what do you need to have done? == | ||
* All content should be up to date or archived | * All content should be up to date or archived | ||
| Line 78: | Line 49: | ||
* You should start building a schedule for your team. -You will need to have someone available during the con incase the site goes down or needs immediate updates (like a splash page of the new years website for sunday, if available) or to provide/update the reg system/CM theme with the help if IT team on sunday for next years pre-reg. (Use the Master Schedule for the year! Programming lead sets this up every year and it houses our event schedule as well as the work/team schedules for at con departments.) | * You should start building a schedule for your team. -You will need to have someone available during the con incase the site goes down or needs immediate updates (like a splash page of the new years website for sunday, if available) or to provide/update the reg system/CM theme with the help if IT team on sunday for next years pre-reg. (Use the Master Schedule for the year! Programming lead sets this up every year and it houses our event schedule as well as the work/team schedules for at con departments.) | ||
1 Month before con, what do you need to have done? | == 1 Month before con, what do you need to have done? == | ||
* Registration should be closed and the link to the registration kiosk should be removed or commented out on the website. (This is depending on when Reg closes) | * Registration should be closed and the link to the registration kiosk should be removed or commented out on the website. (This is depending on when Reg closes) | ||
| Line 86: | Line 56: | ||
* The schedule should have its own page and should be posted to the website or be ready to post at this time. We usually use Sched.org so it is usually simply an embed code. | * The schedule should have its own page and should be posted to the website or be ready to post at this time. We usually use Sched.org so it is usually simply an embed code. | ||
After the Convention/Before the Firing Party | == After the Convention/Before the Firing Party == | ||
* Make sure all your volunteers (and yourself) got inputted into the system for their hours. | * Make sure all your volunteers (and yourself) got inputted into the system for their hours. | ||
| Line 96: | Line 65: | ||
If VancouFur owes you money for department spending, PLEASE PLEASE send your reciepts to [[[email protected]]] & [[[email protected]]] and then fill out [[https://goo.gl/forms/I9u1EEhAFNAaJfIQ2]] <br> | If VancouFur owes you money for department spending, PLEASE PLEASE send your reciepts to [[[email protected]]] & [[[email protected]]] and then fill out [[https://goo.gl/forms/I9u1EEhAFNAaJfIQ2]] <br> | ||
== Break down of contacts == | |||
Break down of contacts | |||
* Website should be in contact with every department to make sure that any info that is needed to be on the website is accurate. | * Website should be in contact with every department to make sure that any info that is needed to be on the website is accurate. | ||
| Line 104: | Line 71: | ||
* Website executive is the Marketing exec. [email protected] | * Website executive is the Marketing exec. [email protected] | ||
Department Inventory and Ordering Resources | == Department Inventory and Ordering Resources == | ||
* Only needed if we need to buy hardware for the website or possibly premium themes for wordpress or drupal (if we use them) | * Only needed if we need to buy hardware for the website or possibly premium themes for wordpress or drupal (if we use them) | ||
Do | == Do's and Don'ts of the Department == | ||
* Make requested updates promptly and within 24 hours. A second is a great asset to help with this and halves the load. | * Make requested updates promptly and within 24 hours. A second is a great asset to help with this and halves the load. | ||
| Line 123: | Line 88: | ||
* What would you suggest to be done for the future years of your department that aren't already in motion? | * What would you suggest to be done for the future years of your department that aren't already in motion? | ||
Other Resources | == Other Resources == | ||
* Codecanyon.net Place to buy premium themes and plugins for Wordpress and drupal | * Codecanyon.net Place to buy premium themes and plugins for Wordpress and drupal | ||
| Line 130: | Line 94: | ||
* Google analytics - you get a lot of very good data from there on visitors and traffic. Remember to log in once a month to check traffic and make solutions if traffic dips | * Google analytics - you get a lot of very good data from there on visitors and traffic. Remember to log in once a month to check traffic and make solutions if traffic dips | ||
PLEASE REMEMBER | == PLEASE REMEMBER == | ||
* Always respond to emails/contacts, even if it is just to say “I recieved your email and will get back to you soon!” / “I don't know the answer but I am looking into it for you!” | * Always respond to emails/contacts, even if it is just to say “I recieved your email and will get back to you soon!” / “I don't know the answer but I am looking into it for you!” | ||
| Line 143: | Line 106: | ||
* Make sure you know who your Executive is! They are there to help you and oversee the branch of departments you are in. Contact [[[email protected]]] / [[[email protected]]] to check or check the contact page on the website! You can also use the [[contact sheet]] for the year | * Make sure you know who your Executive is! They are there to help you and oversee the branch of departments you are in. Contact [[[email protected]]] / [[[email protected]]] to check or check the contact page on the website! You can also use the [[contact sheet]] for the year | ||
[[Category:Media]] <!-- Branch --> | [[Category:Media]] <!-- Branch --> | ||
[[Category:Department]] <!-- | [[Category:Department]] | ||
[[Category:Draft]] <!-- Remove once this page has been edited and cleaned up --> | |||