Created by Robert Taylor, last modified by Benjamin Brink 29 Jun 2017, at 12:23 PM
Mockup is viewable http://69.67.174.135:8000/home/
Website redesign goals:
1. Convert the current website to an Xowiki implementation.
2. Upgrade the main template to zen.
3. Mount an instance of Calendar, Forums, BugTracker and ProjectManager on the site.
To Do:
1. Replicate OpenACS layout
a. Apply the CSS code in the while website.
b. at /acs-subsite/www/group-master the CSS include parameter has strange
behavior
2. Look at favorites to include the sites at the search contact phase
What about the content that are already in xowiki pck?
3. Missing packages to be installed and sections to be developed.
a. Bugtracker - I believe it's a package. I remember it available at repository. (done)
b. How the sections are developed? Are they pkgs, xowiki pages or subsites?
Documentation - ???
Community - Xowiki page
and Download - File-storage UI
4. Troubles when include pkgs in xowiki. Edit news-portlet package to be included at xowiki page. (Ask dave to cvs the widgets tempates)
5. Send Email to about News and Forum to be included on the main page.
6. What do we need to ask to the experienced people?
the answer is we ask for experienced suggestions
7. wait Robert setup the zone and make the mockup.
8. I'm afraid having the main page as plain text would compromise the information/content. Info need to be visible.
9. News - Add Xinha text editor
10. Discuss what way is the best to take
Iuri: on xowiki?
as a xowiki page?
linuxhooligan: well that was the original idea but i don't think it should be in xowiki
xowiki is for documentation
text types of documents
Iuri: i don;t get the whole pciture of that
linuxhooligan: if we start putting everything in xowiki then we can just get rid of the tabs
i know i know its confusing
Iuri: yes
one thing
linuxhooligan: lets talk about it and see if we can figure it out
i'm open to suggestions
11. When rob give the instance.
He will convert community and documentation to xowiki at openacs website.
12. PHASE I
Make a presentation of OpenACS website possible implementation.
Post forums, ask for inputs
Mount Calendar
PHASE II
Mount Project Manager and fix it up
Help Malte on PM
Created by Robert Taylor, last modified by Benjamin Brink 29 Jun 2017, at 04:18 AM
This page remains for legacy discussion.
This is regarding Approach 1. in en:Documentation_Project_Discussion. The milestones are performance based, instead of directly connected to work, which makes them an impractical plan to follow.
Overview:
Here are a few things we are working to accomplish with XoWiki and the OpenACS website:
Milestones:
MILESTONE I: Tooling Up - Before We Can Accomplish Anything We Must Have a Powerfull Wiki.
- XoWiki is functional for the most part
- a few bugs and feature requests remain, Gustaf and Dave have rocked the OACS boat and created some amazing functionality in a short period of time. When some of these items are cleared this Milestone will be considered accomplished.
MILESTONE II: Testing Packages after each OACS release.
- XoWiki is functional, we can start testing immediately. Look for a TESTING PROCESS document in the PACKAGES category (if it's not up now, soon).
MILESTONE III: Look and Feel vs. Content
- XoWiki is turning out to be very powerfull and easy to use. We will need to focus on content first, look and feel can be handled later. UTILITY has a greater priority over LICKABILITY.
MILESTONE IV: Fanatical Documenation.
- API documenation will stay as is.
- see en:Documentation_Project
MILESTONE V: New Blood.
- I think we can start attracting new devs as soon as our Documentation allows a new developer easy egress into the toolkit. Watching Dave, Gustaf and others litterally create new functionality out of thin air over the last week of January 2K6 is clear indication the barrier to entry is not the toolkit, it is with the resources and tools they need to be able to understand and become developers.
- I think getting a LICKABLE look and feel is something that can be done simultaneously, at a stage after XoWiki has been thoroughly debugged and tested.
Created by Ryan Gallimore, last modified by Brian Fenton 08 Oct 2008, at 02:36 PM
Updated from CMS Matrix.org
System Requirements
| Application Server | Yes
|
| Approximate Cost | Free
|
| Database | Postgres, Oracle |
| License | GNU GPL |
| Operating System | Unix, Linux, Windows
|
| Programming Language | Tcl |
| Root Access | Yes |
| Shell Access | Yes |
| Web Server | AOLServer |
Security
| Audit Trail | Yes |
| Content Approval | Yes |
| Granular Privileges | Yes |
| Kerberos Authentication | Yes |
| LDAP Authentication | Yes |
| Login History | Yes |
| NIS Authentication | Yes |
| NTLM Authentication | Yes |
| Pluggable Authentication | Yes |
| Problem Notification | Yes |
| Sandbox | Yes |
| Session Management | No |
| SMB Authentication | Yes |
| SSL Compatible | Yes |
| SSL Logins | Yes |
| SSL Pages | Yes |
| Versioning | Yes |
Support
| Certification Program | No |
| Commercial Manuals | No |
| Commercial Support | Yes |
| Commercial Training | No |
| Developer Community | Yes |
| Online Help | No |
| Pluggable API | Yes |
| Professional Hosting | Yes |
| Professional Services | Yes |
| Public Forum | Yes |
| Public Mailing List | Yes |
| Third-Party Developers | Yes |
| Users Conference | Yes |
|
Ease of Use
| Drag-N-Drop Content | No |
| Email To Discussion | Yes |
| Friendly URLs | Yes |
| Macro Language | Yes |
| Server Page Language | Yes |
| Spell Checker | Yes |
| Template Language | Yes |
| UI Levels | No |
| Undo | Yes |
| WYSIWYG Editor | Yes |
Management
| Advertising Management | Yes |
| Asset Management | Yes |
| Clipboard | Yes |
| Content Scheduling | Yes |
| Content Staging | No |
| Inline Administration | No |
| Online Administration | Yes |
| Package Deployment | Yes |
| Sub-sites / Roots | Yes |
| Themes / Skins | No |
| Trash | No |
| Web Statistics | Yes |
| Web-based Style/Template Management | Yes |
| Web-based Translation Management | Yes |
| Workflow Engine | Yes |
Interoperability
| Content Syndication (RSS) | Yes |
| FTP Support | Yes |
| UTF-8 Support | Yes |
| WAI Compliant | Yes |
| WebDAV Support | Yes |
| XHTML Compliant | No |
Flexibility
| CGI-mode Support | No |
| Content Reuse | Yes |
| Extensible User Profiles | No |
| Interface Localization | Yes |
| Metadata | Yes |
| Multi-lingual Content | Yes |
| Multi-lingual Content Integration | Yes |
| Multi-Site Deployment | No |
| URL Rewriting | Yes |
|
Performance
| Advanced Caching | Yes |
| Database Replication | No |
| Load Balancing | Yes |
| Page Caching | Yes |
| Static Content Export | Yes |
Built-in Applications
| Blog | Yes |
| Chat | Yes |
| Classifieds | Yes |
| Contact Management | Yes |
| Data Entry | Yes |
| Database Reports | No |
| Discussion / Forum | Yes |
| Document Management | Yes |
| Events Calendar | Yes |
| Expense Reports | No |
| FAQ Management | Yes |
| File Distribution | Yes |
| Graphs and Charts | Yes |
| Groupware | Yes |
| Guest Book | Yes |
| Help Desk / Bug Reporting | Yes |
| HTTP Proxy | Yes |
| In/Out Board | No |
| Job Postings | Yes |
| Link Management | Yes |
| Mail Form | Yes |
| My Page / Dashboard | Yes |
| Photo Gallery | Yes |
| Polls | Yes |
| Product Management | Yes |
| Project Tracking | Yes |
| Search Engine | Yes |
| Surveys | Yes |
| Syndicated Content (RSS) | Yes |
| Tests / Quizzes | Yes |
| Time Tracking | Yes |
| User Contributions | Yes |
| Web Services Front End | Yes |
| Wiki | Ye |
Commerce
| Affiliate Tracking | Yes |
| Shopping Cart | Yes |
|
