Re: [OSCOM] CMS Choices --> link management

Michele Ann Jenkins <[email protected]>
Newsgroups gmane.comp.cms.oscom
Message-ID <[email protected]>
Hello all,

I was just skimming through a backlog of about 100 OSCOM posts hoping to
come across some mention of link management as a feature of open CMSs,
but didn't see anything. I'm working on a project to migrate ~1000 pages
(currently in FrontPage <ugh>) to a CMS and one feature that keeps
coming up is link management. 

Any suggestions for something that includes most of the features below
plus some form of link management? I've looked at Magnolia, Bricolage,
Drupal, and a few others... I'm also interested in systems with easy
import of legacy content, either in an XML format (I know Bric takes
SOAP imports nicely) or something else to speed up the migration
process.

Thank you,
Michele

On Sat, 2005-02-05 at 16:09 -0800, Oliver Crow wrote:

[..]
> In the end we chose the commercial version of Sitellite.  It used to be 
> open source, and is transitioning in the newest version to commercial 
> only. I would have chosen a fully open source option, but I really 
> couldn't find anything that had:
> 
> a) template structure for a page based, published site (as opposed to a 
> CMS for a community/blog/BBS style site)
> 
> b) a powerful, configurable back end with versioning & workflow
> 
> c) an easy to use, simple authoring interface
> 
> d) good documentation for authors, and for template developers
> 
[..]
> 
> 
> On Sat, 5 Feb 2005, Thomas Bolioli wrote:
> 
> > I am in the process of deciding on a CMS product for my needs and I need a 
> > little guidance since I have never had a need for CMS before. I can be pretty 
> > flexible as far as technology (java/php/etc;) but I have some pretty specific 
> > needs with regards to function. I would prefer some form of open source, 
> > something that runs on linux, based on open standards (to the extent they 
> > exist) and that has the ability for plug ins/addons/extensible. Basically, 
> > the setup I am looking to implement is multiple sites by multiple companies 
> > so I would like to not have to setup multiple installations but share one 
> > installation but I will use multiple installations if I need to. The sites 
> > have a mix of static data and dynamic data presented based on queried/posted 
> > info from user input. Some sites will require events calenders, search 
> > capability, newsletters and address book management (site address book users, 
> > not CMS users). I am a programmer so I can write/modify plugins to do what I 
> > need to do when it does not exist (ie; that address book thing). The site 
> > owners do not (mostly) really need to create new pages (I am doing it so I 
> > can code without wysiwyg), although one site will need to create new 
> > newsletters from templates (or dynamically based on data...), but they will 
> > need to create and edit events, and other content. That is actually why I 
> > need the CMS portion, just to handle the data entry. I was thinking of 
> > writing all of this myself since an editor is not really needed, just data 
> > entry but I would hate to reinvent the wheel and would prefer to leverage 
> > what is out there.
> 
> > The front end site cannot look like a CMS based site so things such as 
> > blog/slash-like packages are out. What I am currently looking at is Mambo, 
> > Midgard/Aegir, Cocoon/Lenya, ezPublish, and openCMS. What is everyone's 
> > opinion of those choices and am I missing something here that I should be 
> > looking at? Is CMS overkill and I should roll my own? I am curious about 
> > search. I do not see much out there so any advice on that part would be good. 
> > In a pinch we can use google's API so that is not required.
> 
> > Thanks in advance,
> > Tom
> 
> _______________________________________________
> General mailing list
> [email protected]
> http://oscom.org/cgi-bin/mailman/listinfo/general
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.