07-28-04 11:10 PM
Hi Ray
We had a similar issue with a client who had inhouse site designers, and
used Dreamweaver for most of the web development work and had no experience
with VS.net.
Unfortunately the only possible thing to do is get the site designers to
create the template layouts in HTML.
Then a developer will need to add in the placeholders and bind the
placeholder definitions uing VS .net. and build the project.
Having said this Macromedia might have some information on the dev net site,
I used to use Dreamweaver a long time ago but not anymore. Also they have
released a new suite of products for Content Management but I doubt that
this is more for a generic audience who are more doing static web sites:
http://www.macromedia.com/software/webpublishingsystem/
MSCMS 2001 used to support template creation with other editors but CMS2002
because of the VS.net integration does not allow this to be done easily as
far as I know.
cheers
Chan
"RayT" <ray_trattles@hotmail.com> wrote in message
news:%23FZXPB%23cEHA.3792@TK2MSFTNGP09.phx.gbl...
> Hi all,
>
> I have a client that recently came over to MCMS. Most of the previous web
> site's pages were developed or at least started using Dreamweaver (not
sure
> of version). The page design group have a graphic artist background and no
> programming experience. The project lead wants keep their graphic design
> skills yet minimise the culture shock to a VS environment. They also have
> access to the new r.a.d.Editor placeholder control.
>
> As I know next to nothing about Dreamweaver, is there a way for
Dreamweaver
> 2004 to know about MCMS placeholder controls or at least the r.a.d.Editor
> placeholder control so they could create aspx pages that included MCMS
> placeholders and could set some of the placeholder properties. The idea
> being that the pages would then be added later to the project in VS by
> developers or maybe even having the Dreamweaver .NET project as part of
the
> MCMS solution. Most likely the template definitions and placeholder
> bindings would performed by the developer group. I know there could be
> further issues with bin directories, namespaces, references etc.
>
> Any hints or alternative suggestions please.
>
> Ray T
>
>
[ Post a follow-up to this message ]
|