{"action":"created","issue":{"url":"https://api.github.com/repos/content-strategy-forum/csf-website/issues/14","labels_url":"https://api.github.com/repos/content-strategy-forum/csf-website/issues/14/labels{/name}","comments_url":"https://api.github.com/repos/content-strategy-forum/csf-website/issues/14/comments","events_url":"https://api.github.com/repos/content-strategy-forum/csf-website/issues/14/events","html_url":"https://github.com/content-strategy-forum/csf-website/issues/14","id":124630252,"number":14,"title":"Conference User Experience Improvement Recommendations","user":{"login":"andrewnhem","id":8039239,"avatar_url":"https://avatars.githubusercontent.com/u/8039239?v=3","gravatar_id":"","url":"https://api.github.com/users/andrewnhem","html_url":"https://github.com/andrewnhem","followers_url":"https://api.github.com/users/andrewnhem/followers","following_url":"https://api.github.com/users/andrewnhem/following{/other_user}","gists_url":"https://api.github.com/users/andrewnhem/gists{/gist_id}","starred_url":"https://api.github.com/users/andrewnhem/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/andrewnhem/subscriptions","organizations_url":"https://api.github.com/users/andrewnhem/orgs","repos_url":"https://api.github.com/users/andrewnhem/repos","events_url":"https://api.github.com/users/andrewnhem/events{/privacy}","received_events_url":"https://api.github.com/users/andrewnhem/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2016-01-03T05:34:33Z","updated_at":"2016-01-20T05:37:04Z","closed_at":null,"body":"Conference Experience Improvement Recommendations\r\n===\r\n\r\nObjectives\r\n---\r\n\r\n1. Improve conference page experience using existing patterns from popular, successful websites.\r\n2. Deliver information to solve for key page objectives: satisfying attendee, speaker, organizer, and sponsor needs.\r\n3. Recommend repeatable structure for other parts of the site.\r\n\r\nRouting Conference Information Quicker\r\n---\r\nThere's a lot of great information on the existing site. But, there's a lot we can do to improve delivery and routing the right people to the right information.\r\n\r\nConfab does this well on their conference site. There are paths for main site actions. We can emulate this pattern, but solve for our own users while giving them a little more context.\r\n\r\nAs found in Destry's brief, there are primary and secondary information needs for each. We can solve the primary needs within this main user routing block.\r\n\r\nE.g. Attendees: \"How can I learn about what's coming up?\"\r\n*\"Ah, I'll click here to find out more.\"*\r\n\r\nMVP: Add CTA Routing Block, Long-Form Scroll Experience\r\n---\r\nLet's see this block with more context.\r\n\r\nNote that images, media, copy, etc. are for placement only. There are specific messaging objectives within the main brief that still need to be met. This model just gives a general direction of how to improve the flow and accessibility of information.\r\n\r\n![csf-conference-ux](https://cloud.githubusercontent.com/assets/8039239/12077360/d97ffb14-b194-11e5-9dfe-b0c993dabcf3.png)\r\n\r\nHere's an example flow of an interim conference page layout. As we update and expand on longer sections, such as content for Sponsors and Organizers, we can create separate sub-pages for those conference needs. There doesn't seem to be any real con to having a long-form scrolling page for conference information, assuming we make it easy to navigate.\r\n\r\n**LAYOUT**\r\n\r\nWe can explore a single-column layout for main pages to improve focus on content, much like the brand/style guide employs. This would mean exploring other ways to feature the current sidebar content.\r\n\r\n![csf-conference-ux-single](https://cloud.githubusercontent.com/assets/8039239/12077434/18226dae-b198-11e5-9b66-aa499a3a5c57.png)\r\n\r\nPrevious Conferences are stellar reference pages and should have more prominence within the main navigation if we choose to run a single-column layout. See `Food for Thought: Nested Navigation` for more detail.\r\n\r\nWe can repeat key content blocks, like previous conference media and sign up-type actions throughout, as we lose out on the prominence of the second column.\r\n\r\n**INCORPORATING MORE MEDIA**\r\n\r\n![csf-conference-speakers](https://cloud.githubusercontent.com/assets/8039239/12077435/226a9c6e-b198-11e5-88d8-5abe59f438dc.png)\r\n\r\nSprinkling the \"greatest hits\" of CSF where contextual can add some richness to the overall information. Visitors can access archived conference content currently, but after a few clicks and page visits elsewhere. Instead, let's curate the best CSF moments and use them earlier in the experience.\r\n\r\n**INCORPORATING VOLUNTEER AND ATTENDEE QUOTES/FEEDBACK**\r\n![csf-conference-organizers](https://cloud.githubusercontent.com/assets/8039239/12077438/2e3809d2-b198-11e5-91d0-17d90b42d4e4.png)\r\n\r\nCreating a quote/callout block to contrast the main conference content body can be a great way to add some social proof to the site experience. The way each of these quotes begin past conference media pages is great. Borrowing from this pattern on the main conference site can help add peer validation to the CSF cause.\r\n\r\n\r\nFood for Thought\r\n---\r\n**NESTED NAVIGATION**\r\n\r\nIf we adopt this structure for the conference page, it would be convenient for users to be able to see these sub-sections immediately within the main navigation. Nesting the [Attend, Speak, Organize, Sponsor] sections within the Conference top-level nav item adds to the usability and accessibility of site information.\r\n\r\n![csf-conference-nav-nested](https://cloud.githubusercontent.com/assets/8039239/12077439/370185f2-b198-11e5-989f-9426732e386b.png)\r\n\r\nThis pattern can be repeated for other parts of the site, e.g. Articles by Highest-Level Categories.\r\n\r\n**MORE SOCIAL PROOF**\r\n\r\nIn the history of CSF events, there have been many solid speakers and participants. It would be great, with permission, to feature more of their words and faces on the conference site to show that CSF conferences feature real folks who live, breathe, and bleed content.\r\n\r\n![fluent-example](https://cloud.githubusercontent.com/assets/8039239/12077440/3ef52124-b198-11e5-84e2-71ed05cd3c2e.png)\r\n\r\nO'Reilly's FluentConf page does a great job of this in a non-fluffy way. I think there's a nice balance to strike here between how Fluent features their lineups and the over-the-top name-dropping of a Content Marketing Institute event.\r\n\r\n**CAPTURING INTEREST BY FORM**\r\n\r\nCapturing email to gauge interest and frequently inform the community about events and upcoming articles can be a great addition to this section. This would mean investing to some type of newsletter service or app.\r\n\r\n![csf-conference-form](https://cloud.githubusercontent.com/assets/8039239/12077441/4a701c34-b198-11e5-8543-81174e99dd4c.png)\r\n\r\nIf anything, capturing the list can help bolster event attendance if a conference were to be organized.\r\n\r\nWe can implement a simple form (email, submit) within main body, where contextual. I would avoid anything that makes this look like some kind of heavier, for-profit marketing attempt: pop-outs, modals, etc. Natural is better.\r\n\r\n\r\nNEXT STEPS\r\n---\r\n* Vet and discuss this recommendation.\r\n* Discuss how to revise and revamp existing Conference content.\r\n* Prototype proposed content model/page structure.\r\n* Study org, speaker, and sponsor details to fully render and realize pages.\r\n* Create, iterate, improve."},"comment":{"url":"https://api.github.com/repos/content-strategy-forum/csf-website/issues/comments/173093800","html_url":"https://github.com/content-strategy-forum/csf-website/issues/14#issuecomment-173093800","issue_url":"https://api.github.com/repos/content-strategy-forum/csf-website/issues/14","id":173093800,"user":{"login":"andrewnhem","id":8039239,"avatar_url":"https://avatars.githubusercontent.com/u/8039239?v=3","gravatar_id":"","url":"https://api.github.com/users/andrewnhem","html_url":"https://github.com/andrewnhem","followers_url":"https://api.github.com/users/andrewnhem/followers","following_url":"https://api.github.com/users/andrewnhem/following{/other_user}","gists_url":"https://api.github.com/users/andrewnhem/gists{/gist_id}","starred_url":"https://api.github.com/users/andrewnhem/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/andrewnhem/subscriptions","organizations_url":"https://api.github.com/users/andrewnhem/orgs","repos_url":"https://api.github.com/users/andrewnhem/repos","events_url":"https://api.github.com/users/andrewnhem/events{/privacy}","received_events_url":"https://api.github.com/users/andrewnhem/received_events","type":"User","site_admin":false},"created_at":"2016-01-20T05:37:04Z","updated_at":"2016-01-20T05:37:04Z","body":"Done! Sorry for the lateness. :)\n\nOn Tue, Jan 12, 2016 at 10:10 AM, The Scrutinizer <notifications@github.com>\nwrote:\n\n> @andrewnhem <https://github.com/andrewnhem> ? ;)\n>\n> —\n> Reply to this email directly or view it on GitHub\n> <https://github.com/content-strategy-forum/csf-website/issues/14#issuecomment-170998439>\n> .\n>\n\n\n\n-- \nAndrew Nhem\nContent Strategist\nhttp://andrewnhem.com\nandrewnhem@gmail.com\n"}}