Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Advice required regarding using MOSS for web sites

  Asked By: Douglas    Date: Feb 24    Category: MOSS    Views: 772

A bit of a noobie question I'm afraid, am after some advice. My
company (smallish charity) are looking to move our website away from
old Lotus Notes based CMS to... something else. Rather then paying
through the nose for an external CMS, I had thought of building the
basic front end in Expression Web (would allow us to make the site
standards compliant) and then use MOSS to provide the background fancy
bits such as user customisation, RSS feeds, blogs etc.

I guess what I am asking is, does anyone know if this is a really bad
idea?

Share: 

 

4 Answers Found

 
Answer #1    Answered By: Dwayne Jensen     Answered On: Feb 24

Some of that depends on exactly what you mean by basic front  end and
back end. If you are looking for a single contiguous URL where the root
site is developed in Expression Web and subsequent pages in MOSS, then
the answer is No. If you want to build a Expression Web front end  that
links into MOSS pages on a separate URL as the backend, then yes it is
very possible.

 
Answer #2    Answered By: Jose Baker     Answered On: Feb 24

> A bit  of a noobie question  I'm afraid, am after some advice. My
> company (smallish charity) are looking to move  our website  away from
> old Lotus Notes based  CMS to... something else.

Well, anything is probably better than Lotus for CMS.

Is MOSS the answer? I don't know.

I've never been a fan of large CMS systems. They tend to be bloated,
woefully behind standards*, and have a lot of overhead.

This is especially true for smaller web  sites.

MOSS might be right but I make sure it isn't overkill for what you're
trying to accomplish. If you need to stay in .net land, take a look at
dotnetnuke or community server as well.

Now, if you already have a tone of content in MOSS and need to just put
some of that out for the public, then I suppose MOSS makes perfect
sense. But as it is now, even though we're moving MOSS into our intranet
and collaboration portals, I don't think we're in any hurry to replace
our CMS for our public sites  with MOSS.

* the standards issue might be the main hurdle. For instance,
SharePointDesigner can't render CSS layouts.

 
Answer #3    Answered By: Cornelius Guerrero     Answered On: Feb 24

Cost is another important factor, especially if you are a cash-sensitive
charity. Hanging MOSS on the Internet is going to cost you tens of thousands
of dollars. You're probably better off with an alternate approach as Darrel
suggested. Fortunately there are lots of freeware packages that deliver
document management capability. One of the most popular is Joomla!, built on
WAMP (Windows, Apache, MySQL, and PHP). It's not .NET but the price is
right.

 
Answer #4    Answered By: Roderick Wolfe     Answered On: Feb 24

Thanks for these answers, they have all been really useful. I am
definitely now thinking that MOSS is not the way forward for our
website (although we are already using this for our Intranet and
Extranets). I like the look of Community Server so far and am
evaluating that for use with blogs  and forums etc. Like the look of
Expression web  for the main design work.

 
Didn't find what you were looking for? Find more on Advice required regarding using MOSS for web sites Or get search suggestion and latest updates.




Tagged: