The ScribbleLive Demos

Iris Training German Live

Eine Zusammenfassung zu ScribbleLive mit Tipps und Links

Das ist ein LiveArticle. Jedes Event verfügt über einen LiveArticle. Dieser ist kein Teil des Blogs, eignet sich aber wunderbar, um das wichtigste übersichtlich ganz oben zu platzieren.

Vorteile gegenüber dem gepinnten Post: kein Zeitstempel + bringt die Dramaturgie des Blogs nicht durcheinander (gepinnte Posts wandern beim Entpinnen ganz oben in den Blog zurück)

LiveArticle
  • erreichbar im Event unter Schreiben>LiveArticle
  • bietet sich an für Einleitungen, Live updates (längere Zwischenupdates) und Zusammenfassungen - die wichtigsten Infos auf einen Blick oder ein Best of des Events
  • steht immer am Kopf/über dem Liveblog (auch über markierten posts), ist also kein Teil des eigentlichen liveblogs/kein post
  • es kann pro event nur ein liveblog verfasst werden, der aktualisiert werden kann
  • funktioniert wie storify: statt der social media sidebar können aus der rechten Spalte die Inhalte des Events eingefügt werden
  • nur im front end sichtbar
  • hat einen embed code und kann auch separat gepostet werden
  • mehr Infos hier

Ein gutes Anwendungsbeispiel von Fast Company zum Apple Watch Launch hier oder auch via FAZ hier.

Options

Font Size
Viewer Comments
Sounds
Translate posts and comments.
Make a comment
  • EXAMPLES: DESIGN

    CUSTOMIZED EMBEDS

    European Commission: SOTEU: a multitab stream with each tab connected to a stream in the backend ("All" syndicating every stream) - see also examples in German and French
    Trade Fair Munich: Expo Real: a customized social wall with a dynamic, auto-rotating slideshow and tweet/photo overlay 
    NPO: Football match: vertical timeline style and post-boxes
    Süddeutsche: #NIRGER: customized avatars, coloured-coded timestamps that turn from red to black once the posts is older than several minutes
    Tottenham Hotspurs: advent calendar: customized background fonts, post borders create a timeless appearance (avatars and timestamps are hidden)
    dpa: ISIS: vertical timeline design
    Puls 4: Sag'sa colourful pinboard style embed with open discussion threads. Each post is a user comment
    Nordbayerischer Kurier: Icehockey: embed following brand guidelines, sponsor included
    Corriere della Sera: Forward, ideas for Italy: A customized embed, pinboard style, that uses internal syndication to filter several topics. 
    ScribbleSoda: Right-handside widget: stripped of avatars, with social share options showing when hovering over the post)
    ARD: Dunkelkammer Psychiatrie und Radio Tatort: Embed fits in neatly with the rest of the page design.
    FIVB: Fan vote: nicely customized polls
    El Observador: horse race: different visualization for different content sources
     

    PINBOARD - TIMELINE - STORYTELLING

    ScribbleDemos: Around the World: using the storytelling template with parallax effects, displayed in a clean longread format - a storytelling guide as a storytelling here
    Formula E: Social Hub: pinboard excellently fitted to the rest of the page's style
    Mittelbayerische: Year in review: 2015 as a pinboard with tabs (one stream per tab in the backend), 2016 as a timeline with tabs
    Telstra Perth: Fashion Festival: The same event as a pinboard and timeline
    MacLeans: Key moments election debate: standard timeline embed
    Bayer CropScience: Future of Farming: a whitelabel pinboard collecting social posts - eliminate "board" in the URL to get the classic stream design or replace it with "timeline" to get the horizontal design
    dpa: Photos of the day: a customized pinboard with hover and zoom in effects
    La Voix du Nord: Paris attacks: embed template as an obituary wall
    Sportsnet
    Honda Indy Toronto: A social wall with automated tweets and inline ads
    CNN: Remembering loved ones: CNN used the pinboard for an obituaries wall.
    Football League via Reading FC: My club, my town: a fan hub page, good example for the pinboard's filtering capabilities
    Reuters: Central Banks and Iran-Saudi relations: whitelabel timeline
    Reuters: Paris Fashion Week whitelabel pinboard
    Juventus Turin: fanlove pinboard (image and text visible) and anniversary visual pinboard (text only visible via hovering over the post)
    Der Westen: New Year's Eve Cologne: a timeline added as an interactive element to an article
    La Stampa: We love Greece: readers sending in photos of their memories of Greece
    Canadian Media Cooperation: Project 97: great integration into a dedicated website

    CUSTOM-MADE VISUALIZATIONS

    Honeycomb: Fast Company: social posts displayed in a honeycomb structure with enlarge-option
    Storytelling: Berliner Morgenpost: longread ad design with parallax effect
    GeolocationScribbleUser generated content can be displayed on map from the places of origin where the images got uploaded

     

    API

    Mittelbayerische: Card Stacks: left-to-right-navigation, created like a stream but displayed like a slideshow with text and image elements alike
    Ouest France: Tour de France: vertical timeline style integration with icons for content source, customized dropdown-polls and share options
    CBC: Election Center: liveblog in the middle with key events set on the left and live video stream minimized on the right handside
    Berliner Morgenpost: Berlin attacks: vertical timeline design, matching style sheet, load more button and 
    Berlingske: Business Live: vertical timeline keeping readers on top with the latest business news between 7am and 6pm, direct email access to contributors
    Euronews: Berlin attacks:  clean SDK implementation connected to user's progress within the article (reading bar adjusts to whether user hits the 'load more' button)
    Chalksocial: Football social: API-built pinboard with different designs for each content type and automated monetization
    Le Monde: Loi Macron: LiveArticle bulletpoints, show updates, button, mobile tabs, tagging, etc...
    DR Byen:  Mexico: Filter options, key events, scrolling video player, nice sharing options
    Express: Football: Avatars, time stamps, etc changed
    Neue Osnabrücker Zeitung: FIFA: bullet point design, pop up ads on images, Google-indexable posts
    DN: Investor: Financial news blog with individual post links when posts get shared or clicked on
    TV2 Norway: Live Center: main stream connected to key posts on the left, containers on the right for different Scribble elements like polls, social media stream or chats
    DR Byen: Elections: an interactive map, internal syndication connects the different streams of each candidate with each other and the map. If the user clicks on one candidate, he gets shown his/her specific updates only with a location of each post
    Spiegel Online: Der Morgen: a concept blog focusing on commuters, creates a go-to-place for users to get quick updates. API focusing on the basic SL functionalities, highlighted timestamps 
    Global News: Royals: A vertical timeline design
    Comment ()
  • Replies

    The new Content Studio Replies feature makes it easy for users to publish a response to a reader comment, image, post or media item. It's a great feature for Q&A sessions since it allows writers to directly answer submitted questions, and then publish both the question and answer together into the event - in a visually threaded way. Multiple contributors can also create panel discussions by replying to the same item at one time. Public Replies allow viewers to comment directly on a published post. This feature encourages audience engagement through conversation and can be used to power online discussion. 

    Why We Built Replies

    While Engage previously offered a Discussions feature that enabled audience members to comment on a post, and allowed back-end users to reply directly to a reader comment - there were several limitations that reduced the effectiveness. Our new Replies features removes these barriers, adds greater flexibility and with the addition of new options it also expands the use case application! Below are some of the improvements Replies addresses:

    Improve Workflow / Increase Flexibility / Eliminate Tech Dept / Improve UX

    • enable users to publish a threaded response to an unpublished comment or post from the back-end, and then publish both together into the Stream
    • improve Q&A collaboration: multiple contributors can create panel discussions by replying to the same item at one time
    • separate back-end replies (which will always be available) from front-end public replies (which are optional) to allow users full flexibility
    • enable users to edit a reply or public reply to correct or clarify
    • allow users to apply styling, links and add images to their replies
    • enable the ability to reply on a public reply directly from the Mod Hub
    • Replies endpoint is flexible and dependable
    • eliminate character restrictions
    • improve front-end threading design
    • improve back-end UX for responding to posts
    • load additional public replies inline (rather then taking a user to another page)
     
     
    Enabling Replies

    Replies is included in your Engage experience for free as it replaces existing Discussions. Replies is available on request but there a few things to consider before enabling:

    • Content Studio

    You must be using Content Studio in order to use Replies. Public Replies (submitted from the front-end) will not appear in the Standard interface. If you are still using both interfaces (or you aren't sure) then activating it won't negatively impact existing Discussion data - so there is no downside. However, you won't be able to benefit from the enhancements in Replies without Content Studio! 

    • API/custom embeds

    If you are using the Scribble API you will need to integrate with the new Replies endpoint (to replace Discussions in your content experiences) before using Replies. To ensure API users have the time to update their integrations we have ensured you has control over which system you use (Discussions or Replies) by building in options at the Account and Stream level - see details below. It's important to note that the Replies API offers major improvements over the existing Discussions API options. 

    If you are using a customized embed, you might have to apply some CSS stylings changes to your template. 

    To enable Replies, send a request to the Support Team via support@scribblelive.com asking them to enable the 'Replies Setting'.

     
    Stream Settings

    Once the Replies Setting is enabled it will expose a stream level option on the Set-up > Stream page. This option allows you to choose between Discussions and Replies for each Stream. Only one can be enabled at a time.

    • Replies: If "Replies" is ON this will expose Replies in the back-end in Content Studio
    • Discussions: If "Discussions" is ON this will expose Discussions in Standard / Content Studio 
    Replies is the default for all NEW Streams. Old/existing streams already using Discussions will still default to Discussions.
    Toggling between Discussions / Replies will change the options and associated content available on the back-end and front-end (for Public Replies) but it will not result in a loss of data. (For example if you turn Replies on for a stream that previously had discussions, all discussion posts will be hidden from view but they will not be deleted).
     
    Public Replies

    Public Reply is a post level comment (similar to a comment on a facebook post) submitted by a viewer from the front-end (via the embed, whitelabel or original pinboard). 

    If the toggle (above) is set to 'Replies' then this will enable back-end users to reply to posts from Content Studio. To allow viewers to publicly Reply to a post on the front-end you will need to turn on the separate "Public Replies" option.

    Note: This functionality differs from Discussions - which linked both the front-end AND back-end together as one option. This meant that if you didn't want audience members to discuss a post, then SL users also couldn't comment on a comment from the back-end; which obviously is less then ideal for Q&A's. Therefore with 'Replies' we have separated the options, to allow for greater flexibility.

    • Public Replies: 
      • If ON allow viewers to publicly Reply to a post from the front-end content experience (a Reply icon and text box appears).
      • If OFF viewers are not able to reply to a post.
      • If an event is over or you no longer want to accept new Public Replies then you can either manually turn OFF Public Replies or close the stream. This will hide the comment submission box. Published Replies will continue to display.
    • Moderation: 
      • If ON then all Public Replies will appear in the Mod Hub and require manual curation. 
      • If OFF then Public Replies will be automatically published (See Managing Public Replies below)
    • Open by Default: 
      • If ON then Reply boxes are visible in the front-end so viewers do not have to click an icon to comment.
      • If OFF then viewers will have to click a reply icon to open the reply box before commenting.
    Replying from Content Studio
     
    To Reply to a moderated post from Content Studio click on the reply icon below a post in the Moderation Hub.

    A replies text box will open allowing a user to enter a comment. When done, click the "Save" button to save the reply. A reply is not published until the original post is; allowing users to reply to a post in advance of publishing, or allow multiple contributors to reply.

    • Once published both items will be threaded together visually in the content experience, making it easy for viewers to follow along.
    • Unlike Discussions, there are no character limits for Replies, so users can type long replies without the fear of their content being cut off
    • To ensure users have enough space the Replies text box scrolls and can be expanded as needed using the drag bar at the bottom right corner
    • Multiple contributors can reply to the same post
    • Tip! Use the 'Save to Mod Hub' button to post a comment directly into the Moderation Hub where it can be seen by other contributors, and then replied to as needed. This is a great workflow for posing a question to a Panelist with Mod Hub access.

    To Reply to a published post from Content Studio click on the reply icon below a post in the back-end Stream view.

    When done, click the "Save" button to publish the reply. Use this workflow if you want to add additional context to a published post, or for Guest Writers.

    Here is a handy diagram for Guest Writers or other users who need a 1, 2, 3 overview:

     
     
    Post Type Support

    Replies can be added to various post types from the Mod Hub (or back-end Stream) - allowing this feature to extend beyond traditional Q&A’s.

    Replies can be added to the following Posts:

    • RTE Posts
    • Reader comments
    • Replies (inc. Public Replies)
    • Slideshows
    • Polls
    • Uploads (Images, Video, Audio, PDFs)
    • Instagram Posts
    • Facebook Posts
    • YouTube Posts
    • SDK Posts

    Limitations: Tweets are currently an exception due to the Twitter display guidelines. ScribbleLive's product team has reached to our Twitter contact to seek permission to add this in the future.

    Editing Replies

    Replies include built in styling and content options (this was not previously available with Discussions).  Now you can bold the text and add an inline link to your Reply. 

    Content Studio users can also easily add images by clicking the image upload icon.

    Links and images are useful for driving audience members to related content, landing pages or specific advertiser pages. Images can also be made clickable!

    Editing a Reply 
    Make a typo or want to add more information?

    Replies can be easily edited or deleted from the Mod Hub or back-end Stream.
     
    Verified Replies

    Back-end users will have their Replies marked with a verified symbol in Content Studio - the well-known blue checkmark. This makes it easy to differentiate between a Reply added from Content Studio and one added by a viewer (as a Public Reply). Useful if working with other contributors!

     
    Public Replies

    A Public Reply is a post level comment submitted by a viewer from the front-end (via the embed, whitelabel or original pinboard). Public Replies are always associated with an existing published post.

    • Replies (like Discussions) are available on the Embed, Whitelabel and Original Pinboard. They are not part of Storytelling or Visual Pinboards.
    • If Public Replies are enabled (see 'Stream Settings') front-end viewers will be able to add a comment to each published post. A reply icon and a comment box will appear at the post level.
    • If 'Open by Default' is ON then the Reply comment box will be visible under all posts by default. If OFF then viewers will have to first click the reply icon before viewing the comment box. Open by default can help drive more audience interaction, as it is more obvious.
    In order to comment, viewers will be prompted to first login. (Social Logins / anonymous login options work the same as with Discussions)

    If Moderation is ON:

    • After submitting their comment viewers will see a "Thanks for your comment! It's in moderation" message.
    • The Public Replies will appear in the Content Studio Moderation Hub and will require manual publishing. See Managing Public Replies for more info.

    If Moderation is OFF:

      • After submitting their comment viewers will see a "Thanks for your comment! It's in moderation" message.
      • The comment will auto-publish once it clears the automated spam / word filters (typically takes a second or two)
    Viewing Previous/More Replies

    Viewers never have to leave the page to view additional Replies.

    • By Default we display the 5 most recent replies (this is not currently configurable per stream)
    • Replies appear in the order published, with subsequent replies added inline below.
    • If more then 5 Replies are available a "View previous replies" button appears: OnClick - This loads 5 more replies inline.

     
    Managing Public Replies

    Moderated Public Replies appear in the Moderation Hub where they can be quickly reviewed and then published (or directly replied to!).

    Editing: If there is a typo (or a word you want to omit) but it's otherwise a great comment then you can quickly edit the Public Reply right from the Mod Hub before publishing; just like you can do with Reader Comments!

    Filtering: The channel badge updates when a new Public Reply is received (as is true with Reader Comments). To view only the unmoderated Public Replies in the Mod Hub, simply apply the 'Public Replies' filter.
     

    Replying: You can now reply right from the Mod Hub! Simply click the reply icon, just like you would do for any post, and add the reply. This offers an improved workflow from Discussions which required you to first publish the discussion post and then find it in the back-end stream before you could add a related comment.

    For Content Studio users we added an @author feature that automatically adds the name of the owner of the original post. This allows an editor to more easily direct a response to a specific comment.

    Showing Related Posts: 

    All Public Replies include a 'Show related post' feature that allows for a quick inline preview.

    This makes it easy to know which moderated Replies belong to which Posts prior to publishing.
     
    API / SDK Users

    Replies are supported by the (new) API and the SDK. 

    • API / SDK clients will need to integrate with the new Replies endpoint (to replace Discussions in their content experiences) before using Replies.
    • To ensure API users have the time to update their integrations we have ensured the client has control over which system they use (Discussions or Replies) by building in options at the Client and Stream level - see 'Enabling Replies' section above. 
    Comment ()
  • Scribble bietet eine Standard-AMP-Integration

    Comment ()
  • Discover Hub SDK

    ​SL clients can now integrate 3rd party content into the Discover Hub via a sidebar SDK so that editors can search, curate and publish this content directly from Content Studio.
    This means you can now basically add any source that is of value to your daily content production into the ScribbleLive backend. This includes internal archives, e.g. image, video or text archives as well as external sources like Giphy, for example. 
     
     
    SDK Integration Directions

    Developers can find the full Git Hub Sidebar SDK documentation here: https://github.com/scribblelive/sidebar-sdk

    • You will create a page which returns a page with HTML structure shown in the example HTML page - see github
    • This page will be shown in the Discover Hub in the right side bar of Content Studio. 
    • This page can be preceded by any login and/or search functionality.
    • IMPORTANT: The page needs to be secure, e.g. hosted on HTTPS, since web browsers will not allow non secure content to be loaded from our secure site.

    Set-up: Admin > Global Settings 

    • Once the HTML page is created - set-up occurs under the Admin > Global Settings (Developer Settings) section
    • Under sidebar iframe: Enter a name for the iframe and a URL
    • Multiple SDK connections are allowed
    Existing SDK integrations

    Since the SDK sidebar set up page is shared between Standard and Content Studio - existing SDK connections will be automatically available in Content Studio. However developers will need to add:

    • Send to Moderation - to add the content to the Moderation Hub
    • Send to RTE - to add the content item to the Rich Text Editor
     
    How It Works In Content Studio
     
    • If an SDK integration exists, then any user with access to the Discover Hub can view the SDK content
    • OnClick "..." (in the Discover Hub) an SDK integration menu will appear 
    • Selecting an integration will show the related content within an iframe view. This view can be preceded by any login and/or search functionality as dictated by the SDK implementation
    • A user can Publish the SDK content to a Live Stream or alternatively send the content to the Mod Hub or into the text box
    • On Publish content will render as expected based on provided HTML structure

     
    Comment ()
  • SLIDESHOWS

    Content Studio slideshows now include support for new content types (like video) and a fresh new user experience that makes it easier to create, edit and publish slideshows. 

    Creating a slideshow: The new Slideshow feature is available from the Create > Slideshow drop down.

    Adding content: Once Create > Slideshow has been selected the slideshow creation interface will appear. To add content users can either:

    • Click the Upload button and upload images or videos from their device. Bulk upload is supported.
    • Dragging supported content from the Discover or Mod Hub
    • If a user attempts to drag in a content type that is not supported a warning will appear 
    Content types supported: Images, Videos, Tweets, Instagram, Facebook, YouTube

    Adding Captions: Captions can be added to any native image and video slides. For single uploads a caption prompt will appear on upload. For bulk uploads an asset can be edited directly from the slideshow creation view. 

    Reordering Content: Once content has been added to a Slideshow it can easily be reordered by dragging and dropping the slides.

    Publishing: Slideshows can either be published directly or added to the Mod Hub. Once in the Mod Hub, slideshows can be viewed (any collaborator with access can navigate through the slideshow, edit or publish). 
     
    Standalone: Just like other posts, a slideshow can be embedded as a standalone piece of content anywhere on your website. This is a great way to feature slideshows on digital properties outside of a Scribble stream. 

    Editing after Publishing: Slideshows can also be edited after publishing. To edit simply click "Edit" under the "..." menu. This will launch the Slideshow Editing modal. Changes will appear on the front-end without requiring a refresh from your viewers. If you want to edit a slideshow which has been added to the Mod Hub, the editing console will open beside the Slideshow (since there is less space, and a user may need to drag in other content already in the Mod Hub - see image below)

    Please note: If you add a slideshow as part of a longer post, you can NOT currently edit it from the editor - BUT you could delete and insert a new slideshow OR update the original (if it still exists in the Mod Hub).
     
    Frontend display: Slideshows will display on all visualizations like embed, pinboard, timeline, storytelling, whitelabels, except the visual pinboard and not yet in Articles. Slideshows are also supported in the new API
    Comment ()
  • T&C-Box: Teilnahmebedingungen und Nutzungsrechte

    Für Userinhalte können Teilnahmebedingungen, Nutzungsrechte oder sonstige Hinweise nun vor dem Upload angezeigt werden. Nutzer müssen diesen dann erst per Opt-In-Häkchen zustimmen, um Inhalte hochzuladen.


    Administratoren können dieses Feature im backend unter Globale Einstellungen>Rights Management aktivieren und den entsprechenden Text einfügen.
     Der Text erscheint automatisch im frontend aller Streams, die den User-Upload aktiviert haben.
    Comment ()
  • MANUELLES SCOREBOARD

    Im Stream unter Scoreboards ist ab sofort neben dem automatischen "Live" auch die Option "Manuell" verfügbar. Vorlagen existieren derzeit für die Sportarten Fußball, Eishockey, American Football und Basketball.

    Erstellung:
    • Nachdem ihr eine Vorlage ausgesucht habt, könnt ihr das Scoreboard mit einem Klick in die jeweiligen Felder bearbeiten. 
    • Überflüssige Felder können durch Löschen des Textes versteckt werden. 
    • Mit einem Klick auf "Jetzt Veröffentlichen" erscheint das Scoreboard im frontend im v7 embed, Whitelabel und mobil. 
    • Das Scoreboard kann über js-code auch einzeln eingebettet werden. 
    • Pro Stream kann ein manuelles Scoreboard für ein Spiel erstellt werden.

    Aktualisierung:
    • Zurück im Stream erscheint das Scoreboard nun über den Posts und unter der Schreibbox. Via "Anzeigetafel Überarbeiten" können im laufenden Spielbetrieb Ergebnisse angepasst und Notizen hinzugefügt werden. Mit einem Klick auf "Update" werden die Änderungen gespeichert und erscheinen automatisch auch im frontend.
    • Wird der Zwischenstand in der Mitte geändert, passen sich die äußeren Ergebnisfelder (Gesamt) automatisch an. 
    • Im Front- wie im backend kann die Scoreboard-Box auch minimiert werden.

    Den Helpdesk-Artikel zum manuellen Scoreboard findet ihr hier
    Comment ()
  • POSTS EINFÜGEN UND VERSCHIEBEN

    1. Neue Posts zwischen zwei bereits existierende Posts einfügen

    So geht's:
    • Über den Timer könnt ihr neu verfasste Posts auch nachträglich zwischen zwei bereits veröffentlichte Posts in den Stream einfügen. Derzeit ist eine Rückdatierung bis 1.1.1970 möglich. Klickt auf die Uhr und wählt einfach das entsprechende Datum aus. 


    • Damit die Rückdatierung leichter fällt, wird der Zeitstempel ab sofort bis auf die Sekunde genau angezeigt.  So kann auch die Reihenfolge von Posts, die innerhalb einer Minute veröffentlicht wurden, geändert werden.  


    • Sobald der Post veröffentlicht ist, erscheint er im Embed, Whitelabel und Pinboard automatisch auf der angegebenen Position.


    2. Posts verschieben

    So geht's:
    • Mit dem Timer lassen sich auch bereits veröffentlichte Posts an neuer Stelle einordnen. Um einen Post zu verschieben, klickt auf 'Bearbeiten' im oberen rechten Eck des Posts und wählt das entsprechende neue Erscheinungsdatum aus. 
    • Mit dem Setzen des Häkchens könnt ihr gleichzeitig auch den Zusatz "Bearbeitet von" ausblenden, der standardmäßig erscheint, wenn ein User den Post eines anderen Users bearbeitet. 
    • Nach Klicken auf den 'Speichern'-button ordnet sich der Post im Embed, Whitelabel und Pinboard automatisch an der neuen Stelle ein. Bei Timelines muss die Seite einmal aktualisiert werden.

    Warum ist dieses Feature wichtig:
    Mit der Neusortierung von Posts habt ihr nun die komplette Kontrolle über die inhaltliche Abfolge. 
    Dies kann beispielsweise wichtig sein für ....
    • Breaking-News-Events, bei denen im Verlauf Details verfügbar sind, mit denen ihr bereits bestehende Beiträge anreichern wollt, anstatt die Posts zu einem Aspekt verstreut zu veröffentlichen. 
    • Streams, bei denen mehrere Redakteure - einige im Newsroom, einige on-site -   zusammenwirken und ihre Beiträge ohne Moderation posten. Ein Post von Redakteur A, der vielleicht nach dem Post von Redakteur B mehr Sinn ergeben würde, kann so einfach umgestellt werden.  
    • Zeitleisten zu historischen Themen oder Scrollytellings. Der Redakteur kann so zunächst mal all seine Beträge verfassen, ohne penibel auf den Zeitstempel achten zu müssen. Die einzelnen Posts können dann im Zweifelsfall im Nachhinein neu geordnet, vergessene Ereignisse nachgetragen werden. 
    Comment ()
  • ScribbleLive Content Elements


    Streams
    via Embed: script or iframe
    Example: selection
    via Whitelabel: Subdomain-URL
    Example: Schwäbische     Sport1
    Example: selection

    Pinboard
    via Embed: script 
    Example: La Stampa
    Example: CNN

    Timeline
    via Embed: script 
    Example: Monsanto
    Example: Telstra

    New Designs (e.g. Highlights or Scrollytelling)
    via Embed: script (Event-ID has to be changed for each event)
    Example: key posts    geolocation

    Single Posts (content atoms)
    via Embed: script or iframe
    Example: Hollywood Reporter  

    Article: 
    via Embed: script
    Example: J-Source
    Example: Newscom.au (part of stream)  Nordwest-Zeitung (stand-alone)

    LiveArticle
    via Embed: script
    Example: Mashable
    via Whitelabel: on top of a stream
    Example: F.A.Z.
    Example: Le Monde ("Les faits")

    Scoreboard
    via Embed: either as stream header or as stand-alone
    via Whitelabel: as stream header
    Comment ()
  • SCRIBBLELIVE API

    1. Unsere Developer database ist ein guter Start
    2. Version 2 der API
    3. CSS Doku mit Code-Schnipseln
    4. Unsere github site mit allen open source codes
    5. Unsere neue Client SDK
    6. Infos zu unserer API library
    7. Infos zur Nutzung der API Sandbox
    Comment ()
  •  

    EXAMPLES: CONTENT

    BR: Siko15: Made good use of their broadcast material by including audio and video in the blog. During the conference, they had a livestream via TopHTML box on top of the blog.

    Boston.com: Kennedy assassination reenacted: A great idea to re-tell a historical event "live" as it happened minute-by-minute. CBC did a similar project with the Queen's Coronation. Has educational value and attracts different user groups. Also a good idea to ask users for their memories on this moment in history.

    t-online: Promi-Mode: A blog solely based on polls. Creates a go-to-place and aimed at a certain audience. High user engagement. Recurring events are really important to attract a loyal audience.

    SZ: Energiechat: A great crossmedia project. After the parliamentary elections, Süddeutsche let their readers vote on a poll, letting the audience select the 5 most important topics that should be part of the political agenda. The poll's results were then discussed in 5 chats with an editor, an expert and a "user expert" each. The latter were found via a call to action where SZ invited their users to tell them about their experiences. The results of the chats were used for further research and articles in the paper.

    Nordwest-Zeitung: OB-Wahl: A good intro with a survey among citizen's on their expectations, a photo of the interview scene and an intro video of the candiate. Baak (CDU) actually won the mayor seat and wa so fond of the interaction with citizens via live chat that he now use Scribble on his website to hold regular townhalls.

    dpa via SWR: Oettinger: A bilingual chat with EU-Commissioner Oettinger. dpa's clients that syndicated the chat asked their readers days before the event to send in questions via a specific hashtag. Those were collected in a raw feed by automatizing the #. During the chat, the editors and Oettinger could then pick and choose. 

    HR/ARTE/Rheingau Musikfestival: Concert: A good example on how you can develop a 2h event into an interesting two-week journey. In a collaboration with ARTE and the Rheingau Festival (that also put the blog on its website) HR went behind-the-scenes and showed users how an event like this gets organized, they interviewed the musicians etc. 

    Heart: Fifty Shades of Grey: An audio quiz based on content atoms that were just copied into Heart's CMS. 

    Chicago Tribune: Instagram the CIty: A beautiful user generated content stream that creates a loyal audience and is attractive to various audiences. Every week the Tribune sets a theme to which they ask user to contribute photos via instagram. At the end of the week, they  choose a winner whose photo gets pinned on top. German newspaper Stimme.de created a similar project on the topic light.

    Independent: war reporter Syria: A good crossmedia project on Syria. A series on Syria written by the Indy's reporter gets crosslinked in a post and therefore re-used very well as readers who might have missed it in the paper can now see it online. As "advertisement" and added value to his coverage, the Independent had a live Q&A with their reporter, letting him talk about his personal experiences.

    CNN: App manual: An innovative way to explain your new App to your readers.

    shz: Khaled in Kabul: A photo blog by a young German journalist with Afghan roots who went on a six-months-trip to document everyday life in Afghanistan.

    Le Soir: Live surgery: A live broadcast of a heart surgery was accompanied by a commentary blog where users could ask questions and editors were explaining the meedical procedure and giving useful facts about the human body. Educational value.
     
    shz: Alles außer Fußball: Another lovely longform storytelling blog that sheds light on Brazilian's lives outside the football stadiums. 
    Comment ()
Powered by ScribbleLive Content Marketing Software Platform