Beehive as a CMS/Web server

We have a lot of groups using BeehiveOnline and one of them has been using it in a way you might find interesting.

BeehiveOnline (BOL), being the only approved secure collaboration tool for external use, has attracted many different LOBS and GBUs to use it for effective communicationsand they have sometimes subcontracted the development to specialist groups. One of them is the "Brand and Creative" group who coincidentally sit immediately beside is in the Reading office. They were asked by the Support organisation to build websites, actually microsites, to support major customers. They realised that the site required 2 way traffic and had to be able to be managed by internal and external staff as necessary from a web interface.

So why would Beehive be useful to them you may ask?

Well, you may be surprised but the system actually fits this task amazingly well and the functionality can be fulfilled fairly easily by several components within the Beehive Workspace. The main ones are the Wiki page system and the Content area.

Wiki Page MicroSite

The Wiki page allows the embedding of HTML content within the page and the content - graphics etc. can be stored in the Documents area of the same Workspace - so has the ability to chain together the pages to make a coherent website. This can be a simple embedding of an html component like a table or the more complex embedding of complete web sites with complex navigation.

The caveat here is that the syntax of the web site has to be correct or the page will not render - If you are using something like Dreamweaver to create the content make surethings like DIV tags are closed and everything matches before you save the content

As an aside there is a fix available which is shown below, The key is to realise that the versions of a Wiki page are accessible from the URL by adding @1, @2 etc. to the end.:

2) Click on the "History" tab
3) Check the box of the latest version which still works and click the "Restore" button at the top

So if you use a Wiki page you can direct the users to the web age/Micro-site by sending them the Wiki page link.

To access the Wiki page, they will either have to be a member of the Workspace or the entire workspace would have to be set as Public via the checkbox available on the Setting area of the Workspace.

Library Area MicroSite

We have another approach that can offer some extra features that the Wiki may not be able to provide which relies on a setting we have for the WorkspacesService. There is a flag set at a system level to render html files as web pages and not to download them like other files on clicking them in the browser. This allows web pages to be stored in the documents area and, if they are accessed, to make them display as web pages and if constructed correctly - as a web site microsite.

One extra piece that make the use of the Library area a better solution is that if the file is named "index.html" it will be the opened if the folder is accesssed in the same why that a web server will render the index.html page on accessing it with no target in mind. I say using the Library area and not the Documents or Public Documents folder as these are just folders and can be renamed as required - or removed. Note: The Public Folder has the access settings to allow any loggedin user of the Beehive system to access the content if supplied with the necessary URL so it may be better to rename this folder as recreating the access controls can be tricky.

The Library area can therefore be used more flexibly than the Wiki area as the Library/Public Documents area is accessible with having to set the complete Workspace to be open.

A typical URL could be:

and if I have an index.html file in the mywebsite directory it will pop-up the web page and not show the content of the folder - this may be an issue so it may be sensible to insert a link to a document which will show the folder structure to allow access.