This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
public:tellmaps_social_media_rework [2014/10/29 10:51] honzik |
public:tellmaps_social_media_rework [2014/10/29 11:05] (current) honzik [Studio] |
||
---|---|---|---|
Line 4: | Line 4: | ||
{{:public:social_media_rework.png|}} | {{:public:social_media_rework.png|}} | ||
+ | |||
+ | ===== List of properties ===== | ||
+ | |||
+ | These properties are shared in almost all social networks. | ||
+ | |||
+ | * **title** - will show as shared content snippet title | ||
+ | * **description** - will show as shared content description | ||
+ | * **images** - will show as shared content snippet image(s) - one image or more to choose from | ||
+ | |||
+ | This property is twitter only: | ||
+ | |||
+ | * **twitter message** - will only show as the content of a new tweet, probably appended with a short-URL to the tellmap automatically. | ||
+ | |||
+ | ===== Implementation - backend requirements ===== | ||
+ | |||
+ | ==== Studio ==== | ||
+ | |||
+ | the data structure of content set to / returned by the "socialmediaeditor" plugin will change this way: | ||
+ | |||
+ | <code javascript> | ||
+ | { | ||
+ | en: { | ||
+ | title: false, // BOOL false indicates property is not used | ||
+ | description: "some example content", | ||
+ | images: [ "http://some-example-url/image.jpg", "http://some-example-url/image2.jpg" ], | ||
+ | twitter_message: "Some message here" | ||
+ | } | ||
+ | } | ||
+ | </code> | ||
+ | |||
+ | ==== Front-end ==== | ||
+ | |||
+ | According to [[public:tellmaps_social_networks|this document]], it will be needed to create only one "social media share" server-side version of the tellmap. Using the OG properties correctly, this should work greatly in all available social networks. | ||
+ | |||