Skip to content

Webmaster

Jump to bottom
Artem Babaian edited this page Oct 13, 2018 · 2 revisions

hackseq web master

Great, so you've decided to be the hackseq webmaster! Most of the work is done ahead of time so the overall time commitment may be higher then other roles (~40 hours / year) but it's much more spread out over the year then some other roles. This role synergizes well with the Graphic Design tasks, ideally you could do both.

Contact Information

  • Artem Babaian - artem.babaian {at} gmail

Skillset

  • Web development (largely squarespace)
  • Graphic design

Mission Critical

  • Keep the hackseq website up to date, A E S T H E T I C and informative.
  • Maintain a highly stylized hackseq brand in all media. Make it look cool.
  • Late February: The hackseq website hosting and domain need to be paid for on squarespace.

Personas

For the website there are four persona (user-cases) to consider. These are generalizations and just get you thinking about who will visit the site.

  1. Alex: The Team Leader: I'm an experienced bioinformatician or biologist. Most likely a graduate student or post-doc. I may hesitant in leading a team if my idea is worthy of a hackseq project (it is, I just need to be encouraged) or if I have the team leader skills to manage people (I do, I just might need support from the organizers). The information important to me would be:

    • What is the scope of a 3-day hackseq project.
    • What are the time commitments required from me, before and during the event?
    • How big/small will my team be?
    • What are some examples of past projects?

  2. Jen: Industry Team Leader: I work in either communications or development at a company and I'd be interested in leading a team. Much the same as a Academic Team Leader. It's important for me to understand how hackseq IP will work, and that I understand everything created at hackseq will be open-source and freely available.

  3. Emre: The Participant: I'm super stoked to develop and learn about bioinformatics. I'm likely to be a student but can come from any walk of life. If I visit the site outside of participant recruitment phase, I want to be added to the mailing list so that you can contact me when recruitment happens. During the participant recruitment phase, I want to have a good understanding of each project so that I can join and meaningfully contribute to a project with my unique skillset.

  4. Venus: Potential Partner/Sponsor: I work in communications or outreach for either an academic or industry setting. I want to support local events and get the chance for meaningful outreach with students. I'd like to know what a hackathon is, how it brings together students who I want to reach and supports the local bio-tech sector. it's incredibly helpful for me to convince my higher-ups to support hackseq if I can show them clear media which demonstrates how hackseq reflects the values of my organization.

Outline of tasks

Pre-Team Lead Recruitment:

Goal: Upkeep of the website.

  • Clean up the website / pages from previous years for a blank start.
  • If this doesn't exist, make the projects descriptions from previous years easily navigable.
  • The 'sponsor' persona will be visiting the page so explain what hackseq is all about, have media showing the size of the event.

Initializing Event

  • Choose a design 'theme' for the year, the idea being that any media should follow that theme. (i.e. in hackseq18 we choose vaporwave/win95, so color palettes matched that)
  • See also: hackseq Style Guide
  • On the front page make the basic information regarding hackseq easily information or create a splash page for this particular event. All personas will visit the page at this time, but traffic will generally be low.

Team Lead Recruitment Phase:

Goal: Gather resources to create 'Projects Page'.

  • Organize the website for 'team leads' and 'sponsor' personas.
  • Access to previous projects as examples, and direction to the Team Lead Application Page
  • In the Team Lead Application Forms you will need to gather the following information:
    • ~250 word abstract about the project written to recruit potential participants
    • An outline of what kind of participants you'd like to join your team.

Participant Recruitment Phase:

Goal: Promote each of the Event Projects to recruit the right participants.

  • Organize the website for 'Participant personas.
  • Have clear links which explain 1) How to sign up for hackseq and 2) What are the projects which are happening so that I can choose the correct project for me.

Pre-event:

Goal: Initialize online resources for hackseq

  • Schedule page should be online as soon as it's finalized
  • Github repo for each project should go online ~2 weeks prior
  • Slack channel for everyone to should go online in the week leading up to the event.

During the event:

Goal: Sit back and relax! Job well done.

glhf

Clone this wiki locally