something much needed in nof?

With Macromedia Contribute now anyone can easily update and publish content
to existing websites without knowing HTML. Here's what our beta users are
saying about it.

http://www.macromedia.com/software/c...uct_overview/p
df/con_datasheet.pdf

"The more I use Macromedia Contribute, the more I really like it. I love the
possibilities. It allows me to continue to use Dreamweaver and to maintain
control over our site, while giving the non-HTML users a great way to edit
pages with the ease of editing a Word document."

- Shaan Hurley, project engineer, Autodesk

I own DreamWeaver MX and Contribute, and it looks like Contribute will be a
useful tool for clients who want to do their own updating.

I currently use FuseDocs (www.fusedocs.com) and EMSO
(http://www.editmysiteonline.com) for content management with my Fusion
sites. Each has its own unique features, but both are subscription-based
and, in general, specific to one page only.

The advantage of Contribute is that it can be used to edit any page on a
site, and to allow users to create new pages.

Contribute really only works properly with DW sites (surprise!), and doesn't
understand Fusion's complex code, masterborders etc. It would only take a
couple of clicks in Contribute to completely destroy a Fusion site :<(

Perhaps WSP will take a leaf out of MM's book and look at something similar
for Fusion. Ideally, the web designer would be able to select which parts of
a page could be remotely edited, and the CMS application would restrict the
remote user to edits in these areas only.

Whilst this would be nice, as Fusion relies on an underlying database, any
re-publish of the site would destroy all the changes made remotely, as
Fusion would not be aware of them. Fusion site pages intended for remote
editing would need to have some sort of "don't re-publish" flag set, to
prevent them from being overwritten when publishing.

Perhaps they could name it ConFusion? :>)

Simon
--
Simon Lister - Team NetObjects
www.gotFusion.com

Subscribe to the premium.support news group
subscribe-newsgroups@gotfusion.com


"images" <johns@baynet.co.uk> wrote in message
news:asr16p$p2j3@news01.netobjects.com...
> With Macromedia Contribute now anyone can easily update and publish
content
> to existing websites without knowing HTML. Here's what our beta users are
> saying about it.
>
>
http://www.macromedia.com/software/c...uct_overview/p
> df/con_datasheet.pdf
>
> "The more I use Macromedia Contribute, the more I really like it. I love
the
> possibilities. It allows me to continue to use Dreamweaver and to maintain
> control over our site, while giving the non-HTML users a great way to edit
> pages with the ease of editing a Word document."
>
> - Shaan Hurley, project engineer, Autodesk
>
>
>
>

Are you sure it would destroy a NOF site?

The site claims you can use it with any authoring tool including Front Page.
If it doesn't destroy a FP site I can't imagine it would wreck one in NOF.

But I don't know this for sure.

What I didn't understand was it sounded like it only allowed people on a
network to change content, not a client at a different location. But I may
have gotten the wrong impression from watching the flash tutorial on their
web site.

On Fri, 6 Dec 2002 22:13:17 GMT, "Lucus" <lucus57@hotmail.com> wrote:

>Are you sure it would destroy a NOF site?
>

Yes. Fusion is not like other apps - it cannot edit html. It is a html
generator, not an editor. Therefore, any attempt to edit a site once
published by using another tool will result in the existing Fusion NOD
being redundant.

So, although it's easy to edit an uploaded Fusion site online using
any number of tools, your original Fusion NOD file is rendered
useless by doing this, unless meticulous records are kept of the
updates and these are later manually incorporated into the NOD.

This is where Fusion could possibly be made better by WSP providing an
external log utility - a log script which records all changes made to
an uploaded site since the publish date would be a very nice addon
utility...

For sites where certain pages need to be updated by the customer after
publishing, the best two methods for maintaining the master NOD are as
follows :

1. Create the site as a dynamic database driven site. That way, all
that changes is the database.

2. Create multiple "sites" within the domain. Split your "master "
into parts according to future editing requirements. That way, you
wont have to re-do the entire site in Fusion next time the NOD is
worked on - instead, you just edit the NOD relevant to the "site"
which has changed.

Sean

Simon «gotFusion.com» wrote:
>
> Whilst this would be nice, as Fusion relies on an underlying database, any
> re-publish of the site would destroy all the changes made remotely, as
> Fusion would not be aware of them. Fusion site pages intended for remote
> editing would need to have some sort of "don't re-publish" flag set, to
> prevent them from being overwritten when publishing.

I'm assuming that Macromedia's Contribute feature uses a server-side
database to store all the client changes. In which case, this would be
a simple matter of having Fusion generate some server-side code to
generate the content, which wouldn't change at all between publishes.

--
-----------------------------------------------------------------------
Blake Kadatz - BitMotion Software Inc. - http://www.bitmotion.com

In article <MPG.185e8c7dfca7e380989712@news.netobjects.com> ,
blake@REVERSE.noitomtib.TO.GET.DOMAIN.com says...
> I'm assuming that Macromedia's Contribute feature uses a server-side
> database
>
No - it uses ftp to connect to the actual html file and allows the user
editing ability (with limits set by the original author). Personally I'd
favour a system that structures the data by getting the user to enter
into a database but Contribute doesn't do this.

--
John Carratt
http://www.redleaf.co.uk
UK sales & training for Fusion

gotFusion
Your Fusion Community

John Carratt wrote:
>
> > I'm assuming that Macromedia's Contribute feature uses a server-side
> > database
>
> No - it uses ftp to connect to the actual html file and allows the user
> editing ability (with limits set by the original author). Personally I'd
> favour a system that structures the data by getting the user to enter
> into a database but Contribute doesn't do this.

Thanks for the info -- I stand corrected. Given that Dreamweaver is
generally geared more towards development of dynamic sites, I'd have
thought it would make use of something like this.

--
-----------------------------------------------------------------------
Blake Kadatz - BitMotion Software Inc. - http://www.bitmotion.com

In article <MPG.185ea509c4a8cb4b989716@news.netobjects.com> ,
blake@REVERSE.noitomtib.TO.GET.DOMAIN.com says...
> Given that Dreamweaver is
> generally geared more towards development of dynamic sites, I'd have
> thought it would make use of something like this.
>
I'd have thought so too - I was a bit dissapointed with the way
Contribute works. I guess it's a solution that works without php/asp/CF
though.

--
John Carratt
http://www.redleaf.co.uk
UK sales & training for Fusion

gotFusion
Your Fusion Community