[ 
http://jira.magnolia-cms.com/browse/DOCU-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Antti Hietala updated DOCU-178:
-------------------------------

        Summary: Adding social media to your site  (was: Adding Blog Use Case)
       Assignee: Samuel Staehelin  (was: Suzanne Deprez)
    Description: 
Provide an overview of social media features you can add to a Magnolia site. 
Blog is only one of them.

Social media features:

* Collaboration: Public user registration with PUR module. Collaboration with 
Forum and Commenting modules. Embedding an external poll.
* Blogs: Blog module
* Microblogs: Twitter integration with Frisbee or Twigs modules 
* Image sharing: Flickr integration with Frisbee or Twigs. Adding editorial 
Flickr images with a custom DAM handler (Teresa's blog post).
* Social bookmarking: Default STK bookmarklets and how to customize them. 
ShareThis and AddThis with Frisbee module.
* Social networking: Facebook like, share and commenting with Frisbee or Twigs
* Geographical location: Google Maps with Frisbee or Twigs
* Syndication: RSS feed generation and aggregation, microformats with Twigs
* Advanced social media mashups: VPRO's Pinkpop festival website uses Magnolia 
CMS, CouchDB and Camel. The site harvests pictures and video uploaded by 
festival goers from the Internet and serves the harvested media back to viewers 
in a single, browsable repository. Link to the 
[presentation|http://www.magnolia-cms.com/community/magnolia-conference/archive/2010/program/presentation-day/pinkpop.html]
 VPRO gave at the 2010 Magnolia Conference.

For each social media feature:
* Explain its goal, typical uses and benefits. For example, the goal of 
publishing an RSS feed is to syndicate recently updated content in a standard 
format.
* Link to existing documentation about the feature. The feature may be provided 
by Magnolia core, STK or a module. If the linked-to documentation does not 
explain how to add the feature, correct the issue in the target document rather 
than here. The purpose of this use case document is to provide an overview to 
possible social media options, not detailed installation procedures for each 
individual feature.
* Include screenshots and examples. Use existing shots such as 
[stkCombinedFeed|http://documentation.magnolia-cms.com/reference/paragraph/teasers.html#STKCombinedFeedList]
 when possible.

Create the use case document in {{/use-cases/social-media}}.

  was:
Create a use case that will provide information and documentation needed in 
order to add a blog.

Documentation for the Blog module is (or will be) split between the Module 
documentation and wiki 
(http://wiki.magnolia-cms.com/display/DEV/STK+Blog+Template).

This use case would also fill out the list of possibilities in the proposed 
Social Communication section in the use cases structure.

A skeleton of this use case is provided at 
http://wiki.magnolia-cms.com/display/DOCU/Adding+a+blog.

    Component/s: content

Changed ticket scope to cover all social media, not only the Blog module.

> Adding social media to your site
> --------------------------------
>
>                 Key: DOCU-178
>                 URL: http://jira.magnolia-cms.com/browse/DOCU-178
>             Project: Documentation
>          Issue Type: Sub-task
>      Security Level: Public
>          Components: content
>            Reporter: Suzanne Deprez
>            Assignee: Samuel Staehelin
>
> Provide an overview of social media features you can add to a Magnolia site. 
> Blog is only one of them.
> Social media features:
> * Collaboration: Public user registration with PUR module. Collaboration with 
> Forum and Commenting modules. Embedding an external poll.
> * Blogs: Blog module
> * Microblogs: Twitter integration with Frisbee or Twigs modules 
> * Image sharing: Flickr integration with Frisbee or Twigs. Adding editorial 
> Flickr images with a custom DAM handler (Teresa's blog post).
> * Social bookmarking: Default STK bookmarklets and how to customize them. 
> ShareThis and AddThis with Frisbee module.
> * Social networking: Facebook like, share and commenting with Frisbee or Twigs
> * Geographical location: Google Maps with Frisbee or Twigs
> * Syndication: RSS feed generation and aggregation, microformats with Twigs
> * Advanced social media mashups: VPRO's Pinkpop festival website uses 
> Magnolia CMS, CouchDB and Camel. The site harvests pictures and video 
> uploaded by festival goers from the Internet and serves the harvested media 
> back to viewers in a single, browsable repository. Link to the 
> [presentation|http://www.magnolia-cms.com/community/magnolia-conference/archive/2010/program/presentation-day/pinkpop.html]
>  VPRO gave at the 2010 Magnolia Conference.
> For each social media feature:
> * Explain its goal, typical uses and benefits. For example, the goal of 
> publishing an RSS feed is to syndicate recently updated content in a standard 
> format.
> * Link to existing documentation about the feature. The feature may be 
> provided by Magnolia core, STK or a module. If the linked-to documentation 
> does not explain how to add the feature, correct the issue in the target 
> document rather than here. The purpose of this use case document is to 
> provide an overview to possible social media options, not detailed 
> installation procedures for each individual feature.
> * Include screenshots and examples. Use existing shots such as 
> [stkCombinedFeed|http://documentation.magnolia-cms.com/reference/paragraph/teasers.html#STKCombinedFeedList]
>  when possible.
> Create the use case document in {{/use-cases/social-media}}.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to