Pelecon has some secret weapons. Our social media team of Oliver Quinlan, Edd Bolton and Jason Truscott have been hard at work behind the scenes creating a host of social media platforms to promote the pre-conference discussions and raise awareness of the event.
We set up a Pelecon Twitter account which is a regular broadcast channel for all the latest news and views on the conference as we draw closer to the day. The account already has in excess of 200 followers, and is growing its reach daily.
Our Pelecon blog already hosts links to abstracts of all of the accepted papers for the conference this year, and an open invitation for anyone to post comments and questions to any of the speakers at the event. We want to encourage dialogue before the conference starts. The Pelecon blog will also feature regular posts from the team, including interviews with speakers, news and other updates as the conference progresses.
The Pelecon YouTube channel features videos of previous talks given by our invited conference speakers, and other associated content related to the event.
We have a Pelecon Lanyrd site where you can see all those attending, and where those who cannot attend can track the conference as it progresses.
The Pelecon Flickr site hosts images of previous conferences, and has a facility for delegates to add further content from their own personal photo collections related to the conference.
There is even a Pelecon official Facebook event page (but we won't talk too much about that...) and a LinkedIn page too!
The official hashtag for the conference is #pelc12 which is already being used in the run-up to the event. There are also session specific hashtags such as #TMpelecon which will be used during the Pelecon Teachmeet.
We think we have the social media angle well covered for the conference, but if you think we are missing a trick, I would like to hear from you.
Create, connect, collaborate by Steve Wheeler is licensed under a Creative Commons Attribution 3.0 Unported License.
Based on a work at steve-wheeler.blogspot.com.
No comments:
Post a Comment