TWD Information Architecture

Here are efforts to document the IA for website building efforts.

Start efforts to design it as an eventual usergroups.io attempt?

Tulsa Web Devs initial IA meeting goals

Apply the jobs to be done philosophy. Jobs

Carlos framework Awareness -> Consideration -> Decision

Would like to perform a lot of dump and sort to discover different things about our needs.

Discovery

• Users
• Context
• Content

What do we need to offer via our website Figure out what has been confusing to new members How to communicate with fellow web-devs

What are our user’s needs? Ask them, or do a dump/sort what information are they after for these needs? identify information gaps

What information does TWD want to share

Current site visits breakdown

Homepage Next meeting Projects

Personas:

• Regular attendee

  • Context
    • Time
    • Where

• Future member

  • Experienced developer
  • New developer
  • Developer "recruiter" (agency, entrepreneur, et. al.)
  • Non-dev techie

• Sponsors

  • Potential
  • Current

Google Analytics:

Traffic sources:

• 25% direct
• 25% search
• 50% long tail

Ideas

Shared resources repository information?

Carlos noticed people have questions about the differences between our hack night, i2c, code for Tulsa meetings.

Code for Tulsa gets ideas for projects, this could happen at your next national event. People want to give suggestions.

Identifying the different types of meetings.

Verbiage

Meetings = Attend

Content types

Meeting posts

RSVP links

Content Ideas

Identify what you are on the developer spectrum.

What can I do for TWD?