Forum thread

I like to start my Adobe Dream projects using Dreamweaver. Here kind of an idea. https://youtu.be/dXmFSIu849k

Hello everyone, and thank you again for choosing to participate in this particular debate. Generally speaking, and in order to avoid any misunderstanding, if you wish to continue this exchange, I would like to specify that my intention is not, on the one hand, to discuss techniques, technologies or even languages, nor, on the other hand, to approach alternative solutions other than those provided by the Creative Cloud (except complement).

On the contrary, I would like, and always if you agree, to approach the possible workflows that are precisely offered by this Creative Cloud, placing of course, and this is the whole purpose of this forum, Dreamweaver in the center of the process as a site manager.

Of course, as briefly introduce above in parenthesis, if you use a complementary software solution, in roundtrip with Dreamweaver, this is very interesting. Especially to see and understand how this use is productive in alternation.

I think the problem is most who contribute to this forum are 'lone wolf' developers i.e., dont work in a team, so dont really require many of the procedures you mention.

By @osgood_

well seen, you're 100% right, you evoke there a real basic and recurring problem in Dreamweaver. It is true that I have more and more the impression that many contributors of this forum, work only in isolation, and therefore are less concerned by collaborative workflows, or workflows that are sometimes dictated by the project managers

In any case, understanding and learning from others is paramount, so knowing each other's workflows is very instructive and rewarding.

For example, I particularly appreciated your method of working on a single file

we are dealing with designers wanting to show their creations.

By @BenPleysier

this is such a glaring point of truth, the eternal bridge between designers (round) and developers (square).

It is true that no tool has been able to bridge this gap. Well, once again, let's voluntarily put aside the purism of the code, and the result. But it seems to me that to date tools like wrappler explore this kind of context. Well, you are the best placed among us to enlighten us on the subject. (without going too far into wrappler and thus leaving the focus of Dreamweaver)

the question is ... should design come first, or should design come to dress up the structure and enhance the defined information architecture, only once the content is in place and accessible as Naked CSS.

As far back as I can remember, I've always had to talk to students about the undeniable divide between academic designers and developers. This is still the case. Interfaces are produced in Photoshop, long before information architecture thoughts, or content strategies are put in place. Kind of like placing the paintings and tapestries, before the house is even defined!

The work done by Atomic Design on this point is simply remarkable. But that's another debate... the question that remains is therefore...... is how to organize roundtrip elements, which are really efficient and operational, between Dreamweaver and Photoshop, Illustrator, XD, or even Word, Excel, .... or other data content production tools, whether binary or TXT-based 

how to you proceed when you have to work with external designer, do they work using Photoshop, Illustrator ?.... do they are sensible to the code aspect ?

Then there's the Illustrator generated SVG code.  What can I say?  It's not pretty code to work with but it's usable.  And with some persistence, you can manually clean it up and add interactivity in less than a day.  🙂

By @Nancy OShea

what I find very relevant in this workflow, is that once the event management is added (from Illustrator) the core development can be done externally from any code editor, including Dreamweaver.

the only problem I encounter, is that the responsive management is not at all taken into account, it is imperative to use several documents, otherwise, the SVG offers only a scaling (increase, decrease) but not different angles of view depending on the type of screen and the available space.

I had explored the track of workspaces (artwork I think in english), on the one hand to mutualize the scripts, but especially to optimize the development process.

How do you handle it on your side ?

I mainly use Bridge with Photoshop, never with DW.

By @Nancy OShea

This is a remark that I often receive. For a wide range of users , including on the prerelease, Bridge is exclusively associated with the pictorial aspect of the media, but not at all with the code snippets organisation and management (by the way do you know the Lumigraphics extension on this subject), nor with the administrative documents aspects of the projects, as legal notices, general terms of use, or sales, copyrights notice, and so on (in connection with Acrobat)... Bridge scripts are a fabulous source of solutions and utilities, nor with the all management of the files in general and specific to each projects.

Well Dreamweaver, from the assets panel allows us to move and/or copy files in between project, but that would be a real plus if both software could be first linked in between them, and second, with the Creative Cloud space.

sorry... I just realized that I was long....

I been sick and busy but I am talking to Adobe community leads on this sort of thing and to improve the coding side of the community.

For me I think Adobe is off the ball in terms of the modern web, what it is, how it is shaping and what is involved. They are not in the game right now with a number of swing and misses.

I want to work towards building the community aspect around websites, web development etc and help shape some community aspects to help build on that.

I was mainly around the BC space but for some time my main development and team development has been web in general and other solutions. Adobe does not have to have a specific product to be able to have its tools factor into both web design and building out those designs and concepts.

Things like Muse was a goal to get a designer to be able to convert that into designs. While XD is/was original a means to develop interactive designs that help lead to a build of a mobile app or website many are using it as almost a Muse replacement in some respects and having troubles as a result. I think building a community where designers who are primarly print and different scope to web/web application design can learn and grow and designers can connect better with developers who can work together to convert those concepts and designs into reality is something that would be awesome to build on.

And touching on design - You can always tell when someone who does not understand websites produces a web design, they are all fixed screen concepts - How it is designed is how it is.

Just as a touching point you vary rarely use PX in a design, fonts are REM, EM in a lot of cases, widths and heights can be percentage or Viewport based (VW VH) and everything is flexible and scalable becuase screen resolution and size and orientation is different where in many cases mobile first will be an approach if data shows the target audiance will mainly be on such devices.

Thank you @osgood_ , @Nancy OShea  and @BenPleysier for your participation.

It is true that starting such a debate can seem hollow, and devoid of interest for a certain number of us, regular or not, who come here only to ask questions, basic or not, and others to answer, and no more.

that's a bit of a forum...

but it's also, like the agora, a place to debate, exchange, transgress rules so that all the people (hear here those of the passers-by and participants) who wish to do so can re-interrogate themselves on their vision, their choices, their knowledge ... to question themselves.

I was talking about Dreamweaver and the Creative Cloud, and the Cloud... so what...?

if you allow me, I would just ask a question...

how many of you (and participate in this question who wants to, I do not think of anyone in particular) ... employs :

• bridge to prepare media, organize trees, folders, startup backbone, etc... execute scripts to prepare files and so much more...
• Color (formerly Kuler) to work on the different projects palettes (involving graphic designers, ergonomists, clients... in the process) and retrieving these elements directly from the CC library
• that pre-maps their articulations using XD @BenPleysier  you opened the door on this point... thanks
• works with interactive SVG using back ond forth, between Illustrator and Dreamweaver
• drops files (or other fragments) on the creative cloud space in order to share them with the team (team being also CC member or not)
• which designer working with you Developers / Integrators based on Dreamweaver, uses the collaboration and creation tools provided by the Creative Cloud
• uses and networks with Portfolio, Behance to present, share their development findings, or UI/UX ideas

in short, there could be many more such questions...

but...

the answer if there is one at least... is not to say... Yes of course I'm already doing that, or not...

but the question is how can we all share it, discuss it, exchange it, contribute this use in order to spread it in a first time within this forum...

but then and especially to give Adobe tools to better integrate these uses and make them fruitful for once coming from a community of Developers / Integrators, Dreamweaver's users, and not exclusively from designers, marketers...

that was just the point.

sorry for my frenglish... and sorry if I'm not clear enought to help you get the point.

lately I was wondering what folks around this forum would think about starting debates about the web in general, and the place of the Creative Cloud in this environment.

By @B i r n o u

By mentioning Creative Cloud and the web in one sentence, the water is already muddied. With the exception of Dreamweaver, there is nothing in CC that can be connected to the web, save static design. 

This puts Dreamweaver in a unique position. In the past, Dreamweaver has had to cater for developers and designers  alike, making it difficult to define a path forward.. Today, after developers have left Dreamweaver in droves, it is much easier for Dreamweaver, while it is part of CC, to define a path forward . The future of Dreamwear lies in a graphical UI where coding is not a requirement, much like Muse.

Now I can hear the purists say that the Muse code was a mess. But was it? What determines messy code? Muse websites worked, and were of a reasonable standard. The problem became evident when designers wanted to go further than what Muse offered. They turned to Dreamweaver! Nuff said.

Code smippets? Not required - no coding. Templates? Not required, we are dealing with designers wanting to show their creations.. Templating engine? Most certainly, a layout page that pulls the content into it..A library of widgets? Preferably widgets created by Adobe, maybe in conjunction with one or more of their other programs. XD comes to mind here. In fact, what is to stop XD and DW to be cojoined right now. This would make a super program for the current user.

Looking to the future, Dreamweaver would have to cater for containerised websites that can be uploaded to the likes of Amazon, Azure, Digital Ocean and the like.

That is it from me, and I did not mention Bootstrap once. Oops!

thank you for your feedback, and sorry, I didn't mean to start a debate that was meant to be condescending or to limit the level from below.
In fact my question was with Dreamweaver at the center of the project... how such a tool can be helpfull, how can we link it to periphericals set, are developper rely on better solution for linking libs or framework... how does team share work and is it using Creative Cloud or third solution... how is the best setting for DW that cans rely on drives other than C:\ when team is involved... and so on...

but let's wait for the mayonnaise to take hold

Given the web IQ of posts lately, this might be like trying to have a post-graduate level discussion on quantum bio-mechanics with 8th graders. But here goes...

To answer your question about how I work, I start all projects much the same way: 

1. Concept

2. Plan

3. Preliminary budget

4. Tools & supplies required (incl frameworks, templates, widgets... )

5. Team

6. Revised budget

7. Funding