Getting started - using Sense/Net
The following diagram gives you an overview of the main concepts of Sense/Net ECMS. These components are only a taste of the many possibilities you get when you start building a site on this platform.
Demo siteinstalling Sense/Net and browsing the installed site in a browser you are presented with a demo page (http://localhost ) containing links to features that are ready to try! Some features require you to log in - you can use the default admin / admin username / password combination. The demo site links two bigger content management demo pages:
- the Dynamic content demo presenting you an all-in-one imaginary news demo site
- and the Workspaces demo introducing the workspace concept of Sense/Net organizing different content related to each other under workspaces.
Beside the two bigger demo pages a couple of built-in features are also ready to try. Just mentioning a couple of the presented features Content demo, Event calendar, Gallery, Menu, Search, User management are available. Take your time and explore the demo site to get a picture of what Sense/Net is capable of! You will find basic information about the features and usage in the yellow info boxes on the pages. If you get stuck somewhere come back to this page and continue reading articles you find below.
Content can be created and edited through administrative surfaces of the portal. Read on to see how to manage and present content and how to define custom Content Types!
Sites can be created and edited through administrative surfaces of the portal too. Read the following article to see how to create build a new Sense/Net Site from scratch!
Lists and libraries
You can find several pre-defined lists in the default Sense/Net Content Repository structure under workspaces (you can read about workspaces later), for example /Root/Sites/Default_Site/workspaces/Document/londondocumentworkspace/Document_Library. A List can be displayed using a List portlet and providing a List View. The latter is a content that defines the visible fields of the list. The following how-to helps you get into picture with using Lists:
You can create a new workspace from built-in workspace types (Sales workspace, Document workspace, Project workspace, etc.), create one from scratch, or create a new template others can use. Every workspace has its own navigation, members (custom permissions) and many other settings that are related only to the given workspace (e.g. a workspace wall). A root site (e.g. http://intranet/) is also a workspace, which means that Sense/Net sites are built from workspaces.
You can read more about Workspaces here:
Portal Remote Control
By clicking on the Explore icon in the PRC you will enter Explore mode, the main administrative surface of Sense/Net where you can browse and manage your portal's content. Read on to see how it works!
Exploring and managing contentContent Explorer is the main administrative surface of Sense/Net. Here you can manage all content: create, copy, move, edit, delete, etc. The user interface provides a simple tree on the left side that shows all content in a hierarchical tree. This tree is the representation of the content repository, that is the storage layer containing all content in a tree. You can read more about the capabilities of this storage layer here:
The actually viewed content is presented on the right side. This presentation surface may vary for different content types - for a folder for example the child content list is shown here, whereas for a text file for example the text content of the file is presented. Read more about the Content Explorer here:
There are also a couple of actions available via links on the explorer surface with the help of which you can manage (copy, move, etc.) content. See more detailed info on managing content here:
Now you can manage content in the repository. All types of content, even users. Read on!
Managing usersContent Repository. They are placed in the folder /Root/IMS (http://localhost/Explore.html#/Root/IMS ) and you can manage them just like any other content you have already read about. Creating, deleting, editing users should be pretty straightforward, but the next article shows you everything you need to know about managing user accounts:
So much about managing content in the portal. Now it's time to leverage the broad arsenal of Content presentation features of Sense/Net! Read on to see how you can present the various content on portal interfaces to the users of your site!
You can always create a new page anywhere under a site in Content Explorer to put portlets on, but here is a short tutorial on this if you are having trouble:
You can read more about portlets here:
As you could see in the above articles there is a wide variety of available portlets defined in the system. We only going to need a couple of those to display some content on pages. Read on to find out which portlets do we need!
You can find detailed information on the portlets that can be used to present content here:
To present multiple content on a page you could use portlets that can list a collection of content as a coherent list. The children content of a folder for example can be listed using a Content collection Portlet. Refer to the following how-to for detailed steps on how to do this:
Not only child content of a single folder can be presented as a coherent list but you can present a list of various content that are collected using a query. You can use a query that defines a set of content in a Content query presenter Portlet. The following tutorial shows you how this can be done in Sense/Net:
You can read more about Sense/Net content queries here:
When presenting content on a page their view can be fully customized. This is done with Content Views and Collection Views. A collection of images for example can be presented as an image gallery with the help of Collection Views, as it is shown on the demo site. You don't necessarily have to define any ContentViews to present a content, since every content can be displayed using the built-in Generic Content View that is type-independent. You can explore ContentViews and renderes under the folder /Root/Global/contentviews or /Root/Global/renderes. You can read about these in the Getting started - building portals guide, but before proceeding you need to have an overall picture of how different content are built up. Continue our guide with Content Types!
Content TypesRoot Console on the Portal Remote Control and then clicking Content Types. Content types are defined in a type hierarchy meaning that certain Content Types inherit fields from other types. You can read more about Content Types here:
Individual Content Types are defined by a configuration xml referred to as a Content Type Definition (CTD). A CTD holds all the information that is necessary to represent a content in the Content Repository: the Content Type's name, Fields and Field Settings including visibility in Generic Content Views. Complex as it may sound, it's not a big deal to create your own Content Type, just go through the following tutorial:
Versioning and approving content
Approving mode of content can be set regardless of the current versioning mode. Approving means that the modifications to a content need approval of a user with appropriate permissions before they can be published to the public. Approving actions are available as action links on content (Approve or reject). Read more on versioning and approval here:
Creating content from templatesContent Types Content Fields can have default values. It is also possible to create content from templates, thus the newly created content can have different initial Field values depending on which template has it been created from. Moreover, not only default Field values can be defined using templates but whole content structures, so that when creating a new content a whole folder structure is created. To create a Content Template for a Content Type you just have to create the needed structure under the folder /Root/Global/ContentTemplates (http://localhost/Explore.html#/Root/ContentTemplates ). From then onwards the template will appear among the new menu items, and creating content structure from the template can be done just like creating simple content. Some pre-defined Content Templates include special file types like Empty document.docx (/Root/ContentTemplates/File/Empty document.docx) and complex structures like Project workspace (/Root/ContentTemplates/ProjectWorkspace/Project_Workspace). You can read more about Content Templates here:
A good example for creating content from templates is a Workspace. Read on to find out more about Workspaces!
SkinsContent Explorer and setting the Skin field to the skin of your choice. You can read more about this here:
Built-in web applicationsLogin Portlet for example allows your users to log into the portal on the page it is displayed. A Form Portlet allows you to display a form content and allow the users to submit forms after filling out the given form fields. You can check currently installed portlets in the folder /Root/Portlets (http://localhost/Explore.html#/Root/Portlets ) since portlets also appear as content in the portal. You can find detailed description of individual portlets here:
Congratulations! You have finished the Getting started guide on using Sense/Net! Managing and presenting portal content should not be a problem for you from now on. You can check out the How-tos page to see more tutorials or you can return to the Main Page and check out other Getting started guides to get acquainted with other areas of Sense/Net!