Widgets are where the rubber meets the road— or, rather, where dynamic Web content meets static Web pages.
Widgets are, in a nutshell, instructions to the CMS to show some dynamic content. A widget might say something like this: “Show me up to three news items tagged “important” from the Biology, Chemistry and Physics groups; display them in random order; and if any of them are starred, give them a yellow background.”
Creative widget usage is key to making great LiveWhale-powered websites.
When you create a new widget, the first decision you’ll make is what type of content it displays.
If you’re using LiveWhale Calendar, no decision needed—you’ll be making an Events widget.
For LiveWhale Storyteller, it’s probably a News widget.
If you are using LiveWhale CMS, you have a lot more choices: in addition to widgets for displaying all the various types of dynamic content—news, events, widgets, blurbs, forms, galleries, blog posts, images, files—there are also some special widgets. For instnace, you can use a widget to display Twitter posts, Groups, or QuickAccess results. You can even use a Stream widget to combine the results of multiple other saved widgets into a single list.
Simply put, group-aware widgets are shared widgets made by a LiveWhale Admin, typically a widget titled “My Events” for instance. What makes them special is that when you insert them into your page, LiveWhale automatically uses content from the group that “owns” the page. In other words— if it’s your page, it’s your content, automatically. This is done using the me option in the Group selector, or
<arg id="group">me</arg> in a Widget Template.
You can filter and search for widgets by group or use the search field to receive a listing of widgets that are available.
In LiveWhale CMS, you may be working on a hidden page whose widgets will contain profiles, news, events, or blurbs that are also currently hidden.
In LiveWhale 2.0+, you can preview a front-end page and include hidden content (news, events, profiles, blurbs) in all of that page’s widgets by adding ?include_hidden=1 to the page URL. (Note, this will only worked for logged-in users.)