1. Requests for your team
- could you implement the code change in your copy of Alfresco that would result in us being able to use the full, current version of Tinymce this week?
- once the above is completed, can you implement the workflow Yong sent along so we can test that - it includes the ability to publish? We have yet to test out publishing beyond staging
***We'd like to be able to finish testing these pieces by the end of this month at the latest.
- Joe mentioned you had a copy of the access control documentation - could you send that to him this week?
2. Functionality questions for Alfresco - we have two scenarios we want to run against the team for feasibility
- Scenario 1:
We create a collection of blubs (5-6 short lead-ins to stories) and upload those to a "blub" directory, each as separate web content associated with the proper template. Next we create a template called "template x" that can be used across a few different areas of the site (e.g., in the clubs section, the reunions section, in the news section). The web content created using template x have a block area that is optional (e.g., like images or a promo might be optional - you can use the + function to add it to the web content being created). The optional block in this case would be a sidebar on a page. When a contributor creates new web content using template x and adds the optional sidebar, they would be presented with a pulldown menu (or something similar) of the 5-6 blurbs as the potential content to fill the sidebar - they could choose one or more of the blurbs to show up in whatever order they want in that sidebar.
The end result would be that if the text of a blub was updated the changes would be reflected on the pages using template x w/the sidebar option added w/that blub included in it. We wouldn't have to edit all the pages w/the blurb separately.
- Scenario 2:
Can you set an expiration date and a publish date for pieces of web content? Would this be done as part of the workflow? For example, you let a particular group of contributors have an option of submitting publish & expiration dates for web content they create/edit and submit to the publisher. At the same time, you also set up the workflow so the publisher, as part of the workflow, can edit those dates, add them if the contributor hasn't done so, or remove the specified publish date and remove an expiration date all together. If this is part of the system now, can we test this asap?
- Reporting:
How will site managers & contributors know there is a broken link w/in their site. Even if a way to browse and make links w/in the CMS via Tinymce (see priorities below), if web content or an asset is deleted by even an administrator, how would you know there are now broken links w/in the site? We could use Dreamweaver, but are there any plans for reports in Alfresco. What if an administrator wanted to run a report to find out the last publish date of every page on the site? Or they wanted to know how many pages, how many images, how many PDFs, etc. are currently live on the site?
3. Priorities for releases
Below is what we want to see in each of the releases noted. For us to agree to Alfresco as our CMS choice we need a written commitment from them stating that they will be able to include the features listed below in the releases noted. We would also like a complete list of what is slated to be included in each coming release - is it available on their Wiki? That way we can communicate to Big Bad (the firm we're working with) what they can expect as they work on the project.
Release 2.1 (April '07)
- Advanced search integration into the WCM, including the ability to find related articles and display them to alumni who visit the site
- Tinymce integration - when you click on a the make a link button in Tinymce you are able to do two things: 1. insert the URL to an external site as the link; or 2. navigate the directory structure of the site to make a link to an asset (non-image) or web content, and make sure that the person making the link cannot corrupt it through the process of making the link (e.g., they cannot edit the link).
- Tinymce integration - when you click on the insert an image link in Tinymce you are able to navigate the directory structure of the site to make a link to an image and make sure that the person making the link cannot corrupt it through the process of making the link (e.g., they cannot edit the link).
- Safeguards in the CMS to keep just any contributor from being able to delete and asset or web content from the system - the ability to assign delete rights to different roles.
Release 2.x (Summer '07 - preference for July 1, 2007)
- Enhance "add new web content" - IS&T and MITAA team to develop scenarios for Alfresco (e.g., browsing vs. restricting access to directories for contributors adding content)
- Versioning w/in individual sandboxes
- Source compare
4. Bugs found in Tinymce
The following bugs were found when testing Tinymce using their example implementations at:
- paste MS Word content: you can paste the text into the pop-up window but cannot go any further, submit button does nothing
- paste plain text: you can paste text into the pop-up window but cannot go any further, submit button does nothing- clean up code button: clicking on it does nothing - code is not cleaned up (e.g., pasting code w/tons of extra span tags from MS Word is not cleaned up)
Overview
Content Tools
Activity