1 - What was the first CMS you used?

XOOPS 2.0. Prior to this I was hand coding html. It was laborious and I was quite bad at it. It came as quite a revalation to discover that there were programs that would automate all the hard work for you. It still suprises me how many people out there are hand-coding html because they don't know this. Really, the world is full of them.

2 - Why this? Why not others? What others did you check?

Experimented with a variety of Nuke clones (Nuke, Post-nuke, Nuke-it-again-just-to-make-sure). While thrilled at the potential (see above) these tools were not flexible enough to do what I wanted, even back then. XOOPS was i) more flexible and ii) simple to use, so it got the gong.

3 - Describe your path from this CMS to iCMS. When did you move on, and why?

*nuke => XOOPS => XOOPS + ImpressCMS.

I use and like both. I find myself 'hanging out' here though partly because most of the people I used to work with are here, and partly because not so welcome elsewhere any more (but let's not get into a discussion about that). Anyway, what I'm trying to say is that a CMS project isn't a pile of code, its the people that make it (the community).

Secondly, the recent development of ImpressCMS has suited my needs and I appreciate the active and continuous development of the system. Sustainability is important to me. I take a long term view so I am always looking at the future prospects of a system rather than where it is now.

I think Impress has a pretty good and constructive community now, but there's a lot of good projects out there and a lot more competition these days. Finding ways to stand out from the crowd is not easy. Publicity, propaganda, publicity publicity!

Very interesting Nachenko! I could not resist to blog about this: How did I came in ImpressCMS

For people liking summary:

1 - What was the first CMS you used?
XOOPS 2.0

2 - Why this? Why not others? What others did you check?
I used Nukes-like, but XOOPS was the first that really worked!

3 - Describe your path from this CMS to iCMS. When did you move on, and why?
All explained in my blog post, but in summary: XOOPS => SmartFactory => XOOPS Core Dev => ImpressCMS

Now I gotta go to sleep !

Health and republic.

I'm incubating a article/formal proposal/essay/something worth considering for the community, and I'm at the idea collecting level.

You know, that level many people don't get out of in years.

But I'll try to get out and bring something. Promised.

Please everyone spend some time and do this for me, for the whole community an exercise of introspection. please reply for me, and for the community, these questions:

1 - What was the first CMS you used?

2 - Why this? Why not others? What others did you check?

3 - Describe your path from this CMS to iCMS. When did you move on, and why?

Quote:

Coranto.

I was working on a technical site as a writer - and we used this as the back-end code base.

I was later recommended to Xoops 2.0.6 by my hosting provider.

(I forgave him for this later)

Moved away from xoops after Skalpa's departure

Quote:

Drupal is quite nice, Jamoola is unweildy - ImpressCMS met my needs better.

Quote:

xoops 2.0.16 -> ImpressCMS 1.0

Quote:PHPNuke was the first CMS I came across while on the hunt for an Open Source something or other to implement a corporate portal for the job I had at the time. I really didn't know what a CMS was but soon discovered that Nuke was unworkable for me. I found Mambo and then XOOPS 2.0.7 I believe.

XOOPS just made sense to me in that installing a module was much like installing an application in your OS. The added functionality was clearly defined from the core and I could figure it out easily. The permission system was very simple and functional. Because this was a corporate setting it was a must have.

Quote:

Have tried many of the most popular CMS's but iCMS has such an active development community and the people here seam to be on the same page as myself.

Quote:

I had been a lurker in the XOOPS community for most of my XOOPS career. I had been away from the site all together and when I began visiting again there was the usual turmoil. There was discussion of getting a restructuring team together and sorting through the issues. I offered to join and through this process of trying to get the project back on it's feet it became clear to me that I was in agreement with the same folks time and time again.

As it became clear that those were the folks moving in the direction of iCMS, it also became clear that it was the direction I was going to head.

That has been the right decision as is evidenced by the accomplishments of this team in such a short period of time. A fresh start was what was needed and has definitely worked out for the best.

1 - What was the first CMS you used?
XOOPS 2.0

2 - Why this? Why not others? What others did you check?
"First time, first love" (from the coca-cola song 1990) My first cms ever was Xoops 2.0.x I searched for a "easy" cms and found the great german community myxoops.org. Thats it.

3 - Describe your path from this CMS to iCMS. When did you move on, and why?
Xoops 2.0.13 -> every update to Xoops 2.2.6 -> ICMS 1.x
I moved because xoops standing to long at the same point.

What was the first CMS you used?

My first sites were not CMS sites. Static HTML for my personal sites as I got my feet wet. I was fairly heavy into genealogy, which where I got my first introduction to phpGedView - a php-driven application for sharing and editing family tree information. I wanted more on my site, so I integrated it with the HTML and then started learning of others that had made PGV work in phpnuke.

I tried a bunch of the nukes, but didn't really find them easy to use or to fit my needs. I had developed a php-driven frontend for my then-employer's helpdesk software, but soon saw the benefits of having a portal for all our documentation and utilities. Then, someone at PGV started talking about XOOPS - then on version 2.0.7. I soon found what I was looking for and have been around since then. I created my account at XOOPS on 17 November 2004 = 4 years ago, today!

Why this? Why not others? What others did you check?

As I mentioned, I tried various versions of nuke before settling on XOOPS. Security had a lot to do with it - there was a lot of attention being paid to having a secure platform at X, and that was important, especially since I was dealing with personal information at my family site, and business information at work. Along the way, I've also checked on Mambo, Joomla, Drupal, Modx - all adequate, but with different learning curves and appropriate for specific needs, just not mine.

Describe your path from this CMS to iCMS. When did you move on, and why?

I occasionally posted at XOOPS in my early years, but really started to get involved in late 2006 - early 2007. There was a lot of 'discussion' over the future of the cms and I issued the 30-day challenge. My own contribution from that was Starting a New XOOPS Site, which is #4 in all-time views in the forums.

From there, I started working on reviving XOOPSDocs, starting XOOPSWiki and XOOPSInfo. Skipping ahead.....that didn't fit with the direction of the new XOOPS, but I formed a lot of great connections with the group now at the core of ImpressCMS. So, just about this time last year, we officially began making plans for a new CMS project and here we are!

I still bridge between there and here, but mostly because of modules I maintain - pgvxoops and (now) wiwimod.

Quote:

The first would have been PHPNuke I think, I'm sure there was another before but it was so long ago I can't remember.

Prior to Nuke, in the mid 1990's I started using "Front Page", although I'm not sure it was called that when I started with it. I then moved on to HTML and later CSS although from my current work non of that would be evident, lol. I guess over the years things just kept happening in real life that stopped me learning everything I wanted to.

With so many from Nuke originally I'm surprised our paths didn't cross before XOOPS.

Quote:

I'm not entirely sure in all honesty, perhaps at the time it was probably one of the most popular in searches for 'content manager'.

I never really liked how it did certain things and so looked for other options.

Quote:

Well as I said, I wasn't overly happy with PHPNuke for what ever which slips my mind now, so I searched for a new options and then joined XOOPS in 2002.

If my memory serves me right that was about the same time that a hosting company we used went bust and unreachable, our sites went off line and they wouldn't respond to give us our most current data.

I then went to XOOPS, I nearly went of with E-XOOPS (now RunCMS) but ultimately stayed because I once believed in the product back then.

Over the years I've worked with many other systems including WordPress, Mambo, Joomla, Drupal, XOOPSCube, PHPBB, IPB, PostNuke, Media Wiki, 4Images (I believe also a module for XOOPS once), Moodle (also a module for XOOPS once), Coppermine and the list could go on.

I occasionally use another system if it suits the need of a given project at that time.

But no matter what I always found myself loyal to XOOPS. I was then working closely with JMorris last year over at XOOPS we made some tough choices and long hours to get the CMS back on track but then for reasons irrelevant to this thread we decided enough was enough and so moved on.

Most of the people that built and inspired XOOPS over the years are here at ImpressCMS, so although disheartening after all those years, we still have each other as a community but with a slightly different name, ImpressCMS.

We're more like a family here now, and I feel ImpressCMS has brought a lot of people much closer together.

Quote:

I clicked on the little blue planet with the cute little red fox on it. In the thing called the "address bar", I typed community.impresscms.org then pressed the "ENTER" key. Then, out of nowhere, this beautiful "web page" showed up in front of me like "magic".

Quote:

You been smoking something dodgy today?

You sure are in a funny mood! lol