Hi,

Apologies if this is a dumb question, but in exploring VSD I'm a little confused. Managed to find the 'add folder' option under add files, and created a new folder and moved some htm files into it and saved.

Here is the bit that is confusing me - using windows explorer (I cant see a way to see the project structure in VSD) it looks like the VSD source files have remained in the original structure but the output folder after 'save' shows the folder structure I want to use for the site.

Can anyone tell me how to manage the folder structure in VSD, please?

Essentially, how do I manage folders?
I am used to creating a folder structure first and then populating that by creating htm files and adding content (e.g through dreamweaver site windows etc)

At the moment I can't find a site management capability so am guessing I must be missing something.

Is there an advised way to go about creating the structure for a site so as to keep source files organised in subfolders etc?

Thanks.

Hiya K G,

Most everything you do for VSD will be within the VSD program itself. The structure would be included in that as it stores this information in a file that ends with the .vnu extension. This file is then extracted to your server when it uploads and any files that have been updated since the last time uploaded are then updated on your server.

If you want to just "see" how the files will look, structure and all you can have it save your site to your computer rather than uploading it to a server. Don't edit these files though as the VSD program is only able to see the .vnu file and nothing you change outside of the program will be recognized.

Other than that, someone that knows VSD will need to tell you how to actually do the files and folders, but I hope that helps to understand how the program is actually working for your files and folder.

KG i think what you are missing is that VSD is intended to simplify website design

It does everything necessary for you (but in its own peculiar way)

As a total novice when i started, and now having developed over 10 in use websites (see signature) , i can honestly say, i have never needed to worry about any part of my websites TECHNICALLY except for adding sitemaps and google verification codes the rest has all been totally automated.

A programmer friend of mine hates it, as he says it goes against the grain his words "how can you develop websites and not Know how they work"

Personally who cares i get orders through my website (jewellery sales) which pays the bills.

I guess if you want/need to know the ins and outs Eric or a few others might be able to explain things , better, but this is my NON TECHNICAL REPLY

Thanks Jo Ann.

I'm guessing that the vnu file is a database file (along the lines of the old robohelp source file where source and output are not the same). What I'm looking to do is create an organised set of source files so I can keep a track of content files needed for the htm pages - something like:
1. create my site folder structure
2. create the core htm pages in the folders.
3. import my images and other content files into correct folders
4. populate the htm pages

What I was hoping for was that VSD would allow the quick layout options usually missing from wysiwyg editors but also allow for some site management.

The layered approach looks great for creating design, but am now wondering what this would mean for long term content management.

Hiya KG,

Viv and Eric could help you best with that as I don't use the program myself. I do know that although it does things differently for VSD than it would for a code based site, it's definitely got all the right things built into the program to do what you would need for pretty much any website. Since the files and folders are all managed from within the program, although you may not have "full" control on how that's all structured, you still are able to log into your server and see how it's all setup or to have it save the site on your local pc to see what the structure actually would look like. I'm sure in the end it works pretty well for file management once you get used to how it all works.

If I'm reading you right you want a fixed layout but be able to upload new content at will. Like naming an image header then any time you want to change it you will just upload an image called header that's the same size.

Cheers Viv.



No, the whole thing about layout was one of the reasons I wanted to try it out - I'm stuck using an old version of Macromedia (now Adobe) Dreamweaver 8 after getting totally fed having spent years on the constant short upgrade cycle that had more to do with corporate profit than new features.

Left it as long as possible - but changes to hardware and software alongwith html5 etc mean I have little choice but to start looking at shifting.

Since Dreamweaver 8 handles CSS layout like a pig getting hacked by a blind butcher, I've relied on tables and cludging content. Problem is there is not much life in that approach, but I would not use a fraction of the latest 'features' in CS5.5; also the sys reqs for it would mean buying new hardware and replacing more software than I care to. Not convinced about XP mode - I want to get things done, not fight with the machine!

Not interested in hand coding, but do need some access to site management and code tweaks so thought that VSD for layout and HTML editor for code would do the trick until I found that changes made by the editor cannot be reflected in the .vnu db file...

Real bummer because the drag and drop layout looks great for a design over coding approach.



Yeah - I've spent a long time working with Robohelp and got used to setting things up in a particular way so I know how he feels!
This project is not for me - I'm trying to help someone set up a website that they eventually want to manage themselves - given that more than one person could be involved - a single source file in the form of .vnu may prove to be a show-stopper. I'd been hoping to set up the structure and allow access for different people to different areas where they could use some of the coffee cup apps to add a little content (e.g. one person wants to set up photo galleries and another will be writing news articles).
They are running on a shoestring budget and are not technically enabled, so the whole approach of VSD sounded like it might be great for them.

That sort of thing - I'm used to creating a local folder and file structure and then using something like ws_ftp to manage remote files.

I can see the sense of the vnu file and know about hacking around output that then has to be updated in source - just can't see a clear path for that with VSD and non-technical users.

Cheers

KG

Eric,

Do you know if it is possible to use multiple vnu files on a single site?

i.e. create a vnu for the high level site that doesn't change too much and have other vnu files for sub areas?

Trying to think of a work around where the person who wants to do galleries could be given a vnu for their site area and the person who does news and event updates uses another vnu but protecting the overall site structure.

That way I could maybe let them take advantage of the easy layout options for additions to their areas of interest without the risk of them messing-up the whole show or having to mangle the management of the entire site with a single vnu file

Cheers

KG

Anything is possible but keeping it clear is another issue. I think you could use multiple vnu for a site but managing the index page is going to be a problem.