Mobile Main Street is a web-based publishing tool built for sharing real-time information from multiple members within a community. Unlike other platforms, we publish directly from community member's Facebook pages, Twitter feeds, or XML feeds. This means there's no need for storytellers and community members to login to post updates – it's all done automatically.

Once you set up your Mobile Main Street instance you add in the community members and their Twitter or Facebook usernames. Mobile Main Street pulls profile information from the community members' social profiles and then adds them to the category you specify.

Mobile Main Street then checks your community members' social feeds every few minutes for updates and automatically publishes these updates to the appropriate category on your page.

As the community leader you have the ability to add and remove people from your community, mute individual posts, and open and close registration. Most importantly, however, the community leader can also invite community members to create a Mobile Main Street account so they can mute any of their own posts and update their own profile information.

See the Github wiki for details.

Interested in contributing code to Mobile Main Street? Great! Just submit a pull request and we'll take care of the rest. Please be detailed about what feature you're improving or bug you're fixing, this helps us get the request approved more quickly.

Want to contribute, but don't know where to start? We'll keep this list update with potential starting points. Currently, we're excited about the following:

• Expanded unit testing
• Integration tests and test server
• Better theming support
• Additional adapters to connect different social networks (Google+, LinkedIn, etc.)
• Schema.org compatible profile pages (See http://schema.org/Organization)
• Reducing load and render times on mobile devices
• Suggestions or improvements to story ranking

If you find a bug please report it using our Github Issues page. Please be detailed and describe steps to reproduce the issue. Screenshots of issues where appropriate are highly recommended.