(ˢᵒᶜⁱᵉᵗʸlog)
(ˢᵒᶜⁱᵉᵗʸserver)
(ˢᵒᶜⁱᵉᵗʸtask)
Chandler
REST
angular.js
coding-for-fun
cordova
css
hackerspace
installation
javascript
mockups
multi-language
nReduce
pike
publishing
retreat
sTeam
stylesheets
user-interface
virtual hosting
xiamen

(ˢᵒᶜⁱᵉᵗʸlog) is a simple stylesheet to create a weblog like presentation of sTeam content.
It is based on a heavely modified version of the internal public stylesheet and includes some helper functions from uni-pb style package.
The stylesheets are created by Chen Shi Jun and packaged by Martin Bähr

Features/Limitations

  • It currently handles only simple text files and does not allow adding comments.
  • Entries are displayed using the description as a title.
  • The menu is created from the Areas/Rooms
  • A Room named Topics is shown as a tag cloud with each Room inside listed as a topic in a size depending on the number of articles in the topic.

TODO list

  • Minor brush-ups on the style
  • Add a function to easely create new entries with links to topics.
  • Add support for Gates in the menu.
  • Support for comments
Author :mbaehr   |   size :1104Bytes   |   Publish Date :Dec/11/11/17:15   |   to Top

(ˢᵒᶜⁱᵉᵗʸlog) has been updated with various improvements and fixes:

  • Forms to create, upload and edit articles
  • Tabs to switch to the public view
  • Login and rss links
  • In the internal(admin) view, entries are displayed with description and topics.

The current version depends on the publishing and vhosting changes described in the previous post but future versions will hopefully support the old style as well

Author :mbaehr   |   size :553Bytes   |   Publish Date :Dec/26/11/18:38   |   to Top

One of sTeams features is link objects. That is objects that point to other objects. (ˢᵒᶜⁱᵉᵗʸlog) uses link objects to build topical logs. Each topic links to articles related to that topic.

sTeam link objects are not transparent. When you access a link object it needs to be handled specifically to extract the object (in our case the article) it points to.

Handling link objects separately has the advantage however that the target article can be adapted to the location of the link object.

One case where this matters is if an article contains relative urls. If the article /a/hello includes an image src="logo.png", then the browser will load the image from /a/logo.png. Now if /b/world is a link object for /a/hello it would try to include the image from /b/logo.png. Obviously, that won't work, so when presenting the article though the link object we need to parse it and replace relative urls so that they all point to items in relation to the location of /a/hello

The rss feed has also been improved to handle link objects, but in difference to above, here the link object is simply transparently replaced with the original object. Because the feed is accessed in a different context from the whole site, the link location is less relevant. Also if an article is linked from multiple feeds, all feeds will show the same object, thus allowing the feedreader to notice duplicates.

Author :mbaehr   |   size :1531Bytes   |   Publish Date :Jan/10/12/17:44   |   to Top