Please submit your ideas on how to improve Cascade Server.
-
2
Scripts Formats (Velocity Templates)
I’d like to see support for Velocity Templates in Cascade as another option that can be used in the same manner as XSL
-
12
New Custom Roles
I’d like to see the ability to create arbitrary roles with whatever collection of abilities you want.
-
17
Sites
A Site is a formal collection assets that includes:
- own set of Page Configuration Sets, Content Types, Metadata Sets, Asset Factories, Data Definitions, Publish Sets, Workflow Definitions- NO targets, but a collection of destinations to which assets publish- users/groups members of the SiteSites will allow for:- Roles that are local to that siteTarget properties that will be moved:- Serialization Type (to the Page Configuration)- Output Extension (to the Page Configuration)- CSS Classes/File (to the Site) -
46
Asset Recycling Bin
It would be great to have a more robust asset recycling bin to prevent users from accidentally deleting items that can’t be recovered by administrators.
-
12
Menu Blocks
I’d like to see a Menu Block that would provide an easy way to create the most commonly used Menus:
- Breadcrumbs
- Context Navigation
- Next/Previous
- Global Top Nav (Arbitrary Selected Objects)
-
0
Feature Adoption Report
Offer a report in the administration area that helps new Cascade Server organizations explore the system feature set. Each row in the table would be a Cascade feature, number of components in use with an “In use” or “Needs to explore” indicator. Example: Content Type Indexes: count = 0; Need to explore. Offers ability for a project lead to quickly see how in-depth their usage of the product is at any time.
-
7
"Tags" Dynamic Metadata Field
It would be really cool to have a “tagging” metadata field type or a dropdown that also had a text box to add items. That way, users could add categories as needed, but would still receive a list of all existing categories. The interface could be like the search autocomplete or more like a traditional drop-down menu.
-
8
Dates in Dynamic Metadata
Having a special date/time/date-time chooser in dynamic metadata would make it a lot easier for users to add things like “Original Publication Date” or add more finely granular expiration dates like “Home Page Expiration” and “Section Expiration”.
See CSNEW-253 -
14
Folder Order for Asset Factories
I’ve gotten feedback that it would be very useful to manually order asset factories in the New menu. It also would be great to be able to add separators between groups of items. Maybe have a container be configurable to be a group with a separator or a menu level that must be expanded?
-
6
Allow disabling of TinyMCE
Somehow provide an option to disable TinyMCE on individual pages or sections.
This to be able to handle on an as-needed basis the inclusion of content that TinyMCE mangles in some way or another. -
5
Allow more asset factories to display on the dashboard in folder order
Allow more than six asset factories to display on the dashboard in the New Content Wizard area, as well as inherit the current folder order of the assets. The current folder order does not seem to translate to the dashboard.
-
28
Login as user
I would like the abilty as an administrator to login as a user so that I can check their access -
-4
Get "Published Size"
I would like the ability to get the size of a folder before it is published. to a web server -
0
Create Additional Roles
I love the fact that I can edit roles but I would like to be able to create my own roles to get more granular with permissions
-
22
Data Definitions in Blocks
I would like to attach data definitions to blocks. The metadata sets are usually limited with fields such as no WYSIWYG editor and no date chooser.
-
41
Export from one instance of Cascade/ Import to another
Our developers work in our test instance of Cascade which publishes to our test web servers. We would like an easy way to export assets from one Cascade instance (test) so that we would import them into another Cascade instance (prod). We need 2 Cascade instances in order to OS and software upgrades etc -
9
Sort logs by date
In the Administrator area of Cascade there is a place to view/download logs. It would be great if we could sort them by date. This would make it easier to find the appropriate logs for support
-
31
Ajaxify Publisher Status
Instead of refreshing the entire page, use ajax to update publisher status. In addition, possibly include a publisher status for each user at the top right to allow them to keep working while still knowing the status of their last publish.
-
15
Insert Form Elements through WYSIWYG Editor
We have users who need to create their own online web based forms. I would like to see the editing tool be given the ability to insert form elements (accessibly, of course).
-
13
Visually indicate when an asset becomes "dirty"
When an asset that is marked as “should be published” is modified, it should be displayed differently in the left nav until it is published again. This way it is easier to keep track of which assets are “dirty”; and by “dirty” i mean that the last modified time > last published time.
* Note - To input code samples, click the pencil icon (this will remove the WYSIWYG) then be sure to start and end code sections with @@@ (three '@' signs). For more information on textile markup, click here.
