Slashdot Mirror

OK in Slackware Linux and possibly others: Ubuntu?
More?

Yes, there is a fix, but not so straightforward.

But it boggles the mind, how can a site directed for Linux users, not be tested under a few common Linux distros.

The content management system for Linux.com seems to be written with Xaraya.

Do they test and develop the site under Windows though?

Linux.com developers. Kindly develop your site - with your main target audience in mind: Linux users.

...won't win the popularity content. If this was a functionality contest, http://www.xaraya.com/ would be in the running. However, since Xaraya was developed with an eye for technical sophistication, not fool-proofing, I doubt it will have the visiblity to challenge the other major players.

For now, we'll all have to settle for just finding out which CMS has the most name recognition.

...Xaraya!

http://www.xaraya.com.

Nothign beats xaraya in terms of flexibility and customization. There is a workflow module in it.

Xaraya is a highly extensible and customizable system. You may want to give it a look.

One guy did a summary of all names posted and completely ignored/overlooked mine. That guy would be me. There have been a handful of people who complained about me overlooking their suggestions in the list that I created. Quite frankly, that response pisses me off. I spent many hours scouring through that horrific thread where people essentially vomited their name suggestions to the screen without any concern for the guidelines set forth by the Core Team and without any sense of concern for trademarks or available TLD names. Many people simply ignored the conversation and even submitted names that had already been submitted multiple times. That thread is the worst case scenario of what can happen when a project's development is in the hands of the open source community. As I said multiple times ont hat forum, the thorn in the side of the open source community is disorganization. What I did was attempt to start the organization process of that mess. My list resulted in 486 names. That was only a starting point. Soon after, cmeister2 created a database from my list where the names could be further organized, and overlooked names or newly submitted names could be added. If I overlooked your precious name, then you could've added it to his list, that is, if you were paying attention to the conversation within those threads. Most of the names on that list were horrible, but even some of them were better than the Joomla! name. They could've done better. I wish the Core Development team would've appointed someone to organize that discussion. They could've taken cmeister2's database and php script and created a quick voting module out of it to get feedback from the very users and community developers of their CMS. They could've pooled together the potential strength of the community. Only organization will do that. If I would've organized that list, I would've first started an open discussion to establish guidelines, such as the name shouldn't be similar to mambo. After establishing guidelines, I would then setup a quick script where people can submit names based upon those guidelines. If their suggestion did not fit the guidelines, then the submission gets thrown out. That way, they have 60 quality names instead of 500 names that mostly are not usable. A big concern with the name choosing was that viewers (or perhaps someone representing Miro) might poach the domain names that were suggested. To prevent that, I would create a group of volunteers, perhaps 20-30 who have a reputable background within the Mambo community, to finalize the discussion of the new name in a private forum. I can say that the logo discussion is going a little better than the name discussion. They could just do better. I will stay updated with Joomla! development, but I'm personally focusing my efforts on Xaraya

PHP and MySQL are two pillars of open source, there are a lot of resources on them. I would choose a CMS/app framework using PHP/MySQL and build the class around accomplishing tasks in that framework, where each student ends up with a complex website. The framework code can serve as a corpus of examples/best practices and illustrate app design, while the coursework focuses more on user interface, content design, and data management.

A fairly complete list of frameworks can be found at http://www.opensourcecms.com/, with reviews and user comments. My preference is Xaraya, but Xoops or Drupal would be good too. Stay away from the Nukes.

For those of you looking for an Open Source CMS system, you may also want to consider Xaraya (which sprang out of the PostNuke project). Xaraya is currently closing in on its 1.0 release, and we've been running a site successfully since the 0.9.9 version. Extensibility in the form of modules and hooks feature prominently in Xaraya as well. And if you're still confused about which CMS system to pick (or want to be confused!), take a look at cmsmatrix.org.

For those of you looking for an Open Source CMS system, you may also want to consider Xaraya (which sprang out of the PostNuke project). Xaraya is currently closing in on its 1.0 release, and we've been running a site successfully since the 0.9.9 version. Extensibility in the form of modules and hooks feature prominently in Xaraya as well. And if you're still confused about which CMS system to pick (or want to be confused!), take a look at cmsmatrix.org.

Smarty might be "slick", but it has a real weakness in not being XML based, like this templating engine.

Dreamweaver is an impressive behemoth of a tool, no doubt whatsoever. Back in 1999/2000 it was the only possible way to edit and manage websites on a professional level. Dreamweavers wysiwyg power with the older browsers and it's HTML editing features are unmatched. The template engine completely abstracts changes to a website in your developement directory and automatically keeps track of anything you what across multiple documents. If DW doesn't crash and screw up your template dir that is - which does happen more often than you like. It's the best thing you can use ... ...if you don't have a CMS.
Which gets me right to the point:
Sorry, but it's like five years since the early dot-bomb days where dynamic server side stuff was considered exotic and people got payed for klicking static websites together. You may haven't noticed, but the world has moved on. There are something like fifteen bazillion open source content management systems out there. One better than the next.
Who the fuck needs DW nowadays? You don't want DW! DWs concepts are ancient by todays standards. The last time I used it was about 4 years ago in some project where the system team couldn't get their stuff together and set up a halfway decent JSP framework and we had to hack the webdocs by hand in record time. And my web productivity has tripled by now, since I exclusively use content management systems (as every body else does), and be it "only" to generate the html docs offline and publish the output to static webspace.

Honestly now: Ditch DW allready, it's nothing but a huge waste of time these days. Trust me, I make a living with this stuff. And take a look at one of the frameworks above. To save your time, I recommend checking out one of the following: Plone/Zope, Callisto CMS, Mambo, Typo3, Mason, Slashcode, or (forgot this one above) Xoops. Save yourself half to three quarters of webdev time in the long run.
Oh, and welcome to 2005. ;-)

Xaraya is a fork of PostNuke, written by the people who forked PostNuke from PHPNuke (and who left the project en masse in August 2002, including myself).

Xaraya shares no code and little architecture with any CMS in the nuke family... it is somewhere between CMS and application framework.

shameless plug of my favorite one:
xaraya

A merit of http://www.opensourcecms.com/ is the
categorization : it's important to distinguish generic ("portal") CMSs from just weblogs engines,
and other variants. Though -of course- there's no clear cut-off.

I've been making some research recently.
I wanted an open weblog engine (perhaps with some light cms features), in php+mysql (for ubiquitousness), with good internals (decent code and developer docs).

Among the heavyweigth CMSs -escaping from the horrible mess of PhpNuke and sons- I looked at Mambo, Xaraya and XOOPS ; all of them are really interesting; but too complex beasts for my needs.

Drupal (a generic CMS with weblog included) deserves consideration: nice developer docs, carefully organized coding base and very active. But I dont like the concepts it uses ("nodes","taxonomy"), the templating strategy and the focus in general (a CMS too abstract, I feel).

On the other side, on the KISS weblogs engines, Wordpress has gained a lot of attention. And I liked it overall.
BUT: the code is rather immature and poorly organized and the docs are terrible. Lots of poor software design choices, both at maintainability and performance aspects(yes, guys; I know it's just PHP, but even then... lots of globals, nearly no classes, plugins bad integrated, etc)

I finally choose Nucleus. It beats WP largely in software design and documentation. A minus: it's weak activity (compared with wp and others): a year from the last stable release (2.0). But it's alive, has a decent forum, 3.0RC released this month; and going in the good direction IMHO.

I have set up a cms (content management system) to do just what you mention and it is working great.

Contrary to most other cms'es of the PHP-Nuke series, xaraya has the flexibility to manage all publication types (FAQ, articles, reviews) into one single module, which avoids lots of clutter. You can add fields to each type. Myself, I have created a "research blog" publication type (where I describe what I do each day in a blog format), and then "reviews" (for the books I read), "articles" (the articles I read), "todo", "docs" (for things I keep forgetting). Each of these publication types have one or more category trees associated with them (with some trees overlapping) so that I can search/display my blogs by category and/or by pubtype. Finally, I have set it up so that only I can access it. The permission system allows for you to set up different kind of access to the different pages depending on various criteria.

Using a full blown cms may be overkill but the flexibility and extendability is great. To mention your needs, you can use the autolink module to generate automatic links in your modules, and so on..., search works great, for BibTeX you'd probably need to create your own hooks, which I believe vouldn't be terribly difficult.

A wiki might work, but your pages would look identical across tasks and categories, and I like the ability to visualize different pubtypes and/or categories differently. The tendency to generate a mess is enormous in wikis, but with a single user less so. Good luck.

I agree completely. A (possible) example of such a naming would be Xaraya. A "extensible content management system." It was cool- they opened up to the community for naming suggestions, and in the end.. went for something that didn't really mean anything, but sounded vaguely familiar (in spanish i believe?) Which is kinda cool to not have it (necessarily) linguistically attached to english. (my opinion)

It's unique, not bogged down with similarities to other endeavours or product names, readily identifable, and they even have a wav file to instruct you on how to pronounce it. (i still say it wrong in my mind)

all in all, a good name. a good process to get to it!

Maay of you are probably not familiar with Xaraya, but here's the story of where the name came from.

"Project X", as we were calling ourselves in the early days, decided to conduct a name contest among the development team. Entries were submitted, and the voting commenced. Not happy with any of the entries, I decided to come up with something new based of 3 criteria:

• Must start with X. Many of the devs had become collectively fond of this letter for various reasons.
• Must end in A. I thought the product (a CMS) should be female. Most Latin-derived languages identify female words by ending in A.
• Must have three syllables. I considered this the optimal length; nice flow, little chance of getting confused with existing words in most languages, and not too long.

I also felt the name should be a little exotic according to US/European tastes. So, I trolled through a database of Australian place names, entering various short combinations of letters. After a while I had a list of seven possibilities... then I started swapping letters (mostly vowels).

I presented these in IRC, and a couple of them (including Xaraya) caught on. So well, in fact, that the name voting had to be reset to include the new entries. One of our devs who lives in Spain said Xaraya reminded him of the Spanish word for Manta Ray ("raya", literally "blanket"), so I went looking for manta images to create a logo which supported this concept. "Xaraya" won the name contest, and evenually a Manta logo was also adopted.

Of course, this name has nothing to to with what Xaraya does. Making that connection is the realm of the marketing and branding people.

It hasn't been a problem for us at Xaraya with the donations, as we reinvest the donations that we receive back into marketing, pr, etc. We report back the balance of the donations about once a month to the other committers on the project and discuss and have specific goals for the money earmarked. If you expect to get rich from the donations coming in from a project, remember that there are other much more worthy charities that folks will donat to. Donations are generally $20 to $50 scale and are just nice ways of saying thanks, when someone doesn't have the knowledge to reinvest in the project via code / bug reports / docs.

The main problem is that you are using slashdot in the first place. You probably like Perl or have a site with 1 million hits a day. Those are the reasons to choose slashcode. If you don't need that, there's plenty of other options, the best one in my opinion is xaraya

> With Java you have easy access to a lot of OOP features that are very difficult to implement in Php, and the function base is simple to expand. Yea it's big and beefy, but that's what you need sometimes.

Right. Take a heavily OOP PHP program, which has everything in a class, neatly designed into a great architecture. Now, for EVERY SINGLE FREEKING HTTP REQUEST, it has to parse a boatload of OOP code, then run it, creating all the objects. PHP objects cannot persist between page requests. (I don't know if Java objects can or not, but at least they wouldn't have to be recompiled each time.)

I saw one project die a horrible death for exactly that reason. Each HTTP request took quite a few seconds.

And I'm afraid Xaraya, which looks like a very slick new CMS, is going to follow suit. I've tried it, played with it, looked at the code. And it's parsing quite a bit with each request, and on my server each request took at LEAST two seconds, sometimes quite a bit longer.

Ask any webprogrammer/designer, netscape 4.x is the bane of their existance.

Not mine. I never coded specifically for IE, and still don't. Why? Because of all the times my coworkers asked me "Why doesn't this table show up in Netscape?" My automatic reply: "IE tries to interpret your missing tags, add the </table> where it belongs. And start closing everything else properly while you're at it."

The day Mozilla 1.0 was released, I decided to drop all support for NS4. Now IE is the bane of my existence, not only because it's still stuck in 1998 with regard to standard support, but because every version of IE has a slightly different set of rendering bugs. There are things that work according to W3C spec in 5.5 that don't in 6, and so on.

I now code XHTML 1.0 all the time, strict if I can get away with it. The projects I work on benefit greatly from this.

My candidate for sneakiest NS4 bug: Naming any form control "submit" (all lower case) hides the submit() function of the form, and you won't be able to submit the form back to the server via script.

An easy project would be to get involved in one of the Open source Content Management Systems such as xaraya and develop a school oriented extension.

You could then use it for your own site. It's in php and can take subproject with different skill sets (somebody less programming oriented could easily develop custom themes which require not much more than html knowledge).

(there is no such thing as an Open Source Artist people)

Don't agree with that. There are plenty of folks who are willing to contribute non-coding talents (artwork, UI design, documentation, etc.). I know,I've worked with them. Just checkout Xaraya.com. We put out a call for a logo and got back over 50 original designs. We have theme designers lining up to learn to use Block Layout. And, we have talented writers in line to help with documentation. If you are willing to work with people, they are generally willing to work with you.

I made an icon for LOTR a while ago, but couldn't figure out where to post it. You can see it here.

Taco, are you listening?

Check out Xaraya, a promising Nuke clone. It's still in development phase but you should be able to take the codebase and extend from there your modules. There are several others nuke cms (phpnuke, postnuke, envolution...). The open source cms development is still in an evolving phase due to repeated forks.