Skip to content
This repository

Views for plonesocial.microblog status updates and other user activities in Plone

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 docs
Octocat-spinner-32 plonesocial
Octocat-spinner-32 .gitignore
Octocat-spinner-32 .travis.yml
Octocat-spinner-32 CHANGES.rst
Octocat-spinner-32 CONTRIBUTORS.rst
Octocat-spinner-32 MANIFEST.in
Octocat-spinner-32 Makefile
Octocat-spinner-32 README.rst
Octocat-spinner-32 bootstrap.py
Octocat-spinner-32 buildout.cfg
Octocat-spinner-32 setup.py
README.rst
https://secure.travis-ci.org/cosent/plonesocial.activitystream.png

Introduction

Plonesocial.activitystream is part of the plonesocial suite.

This package, plonesocial.activitystream, provides a building block for Plone integrators who want to create a custom social business solution in Plone.

If you're an end-user looking for a pre-integrated solution, you should install plonesocial.suite instead.

Credits

Cosent

This package is maintained by Cosent.

plonesocial.activitystream

Plonesocial.activitystream provides a standalone @@stream view on the SiteRoot. If you have installed plonesocial.network as well, and hit @@stream/network it will show only updates of people you're following.

A navigation bar is provided which detects the presence of plonesocial.network, as well as local workspaces that provide a local microblog, and displays nagivation options suitable for the context.

Plonesocial.activitystream also provides an "Activity Portal" view for the SiteRoot. The Activity Portal view renders a portletmanager viewlet in which you can add an "Activity Stream" portlet (and also a "Microblog" portlet if you installed plonesocial.microblog. This may look like a complex construct but it provides integrators with easy customization flex points, and it provides content managers with maximal control over what is rendered where, and in which sequence. Moreover by using a portlet for rendering, content managers can set various rendering options. You can re-use the viewlet, or the portlet, as you see fit using ZCML overrides. YMMV.

The core rendering component, which is used by all views, is the stream_provider content provider. Extracting the display logic to a separate content provider promotes re-use. activitystream_provider fetches plonesocial.microblog updates, if microblog is installed. It merges those with content creations and plone.app.discussion replies fetched from ZCatalog. If plonesocial.network is installed, it will filter the activity stream by "following" subscription.

To enable loose coupling, plonesocial.activitystream does not depend on plonesocial.microblog or plonesocial.network. Instead, it probes if those components are installed and available, or not. Depending on the availability of those other plonesocial components, plonesocial.activitystream adapts its behavior.

Plonesocial.activitystream looks nicer if you also install plonesocial.theme.

Roadmap

An extensive roadmap for the plonesocial suite is available on github.

Something went wrong with that request. Please try again.