Forum Moderators: not2easy
The trouble is im not sure where to start? I know the idea,principles etc but i could do with seeing an example to get me started? I use dreamweaver MX and ASP. with either Access or SQL databases.
If anyone knows of a sample that i can either download or pay for a template i would be gratefull.
I would like the client to be able to update the sites on their own, and options to preview before publish.
Ive heard of PD's online HTML editor, is this of any use as i cant find much about it.
thanks
xyzString = "SELECT * FROM Tablename WHERE variable=" & value
Edited because of stupid typos
[edited by: Sinner_G at 1:33 pm (utc) on July 10, 2002]
Onya
WOz
I agree. Look at noah grey's greymatter, there are some nice add-on modules starting to surface for that one, such as photojournals.
For a web-based system that provides strong editorial control over the templates, site navigation (through headers/footers), and I've modified homefree. It is not database-driven, however.
They range from being Free to one I saw at $2,000. As Sinner_G said, the principle behind it is fairly straightforward.. but if you're in a hurry have a look at some of the free script sites.
It looks pretty impressive so far, I have to say
I've been in the review stage for quite a while now, but I keep coming back to Zope as well. SEO considerations come as a top priority of course, so how does zope-produced html look to the spiders?
[webmasterworld.com...]
AFAIK, the issues are not so much the HTML (seems you can churn out good, valid code), as the the fact that out-of-the-box, you aren't publishing .html docs. You drop all your objects in a folder in the management view, and when the request comes in for that FOLDER, the Zope web server assembles the HTML, and sends it.
I did see somewhere an add-on that lets you pick up that folder structure, and convert it to static HTML docs. Obviously, this approach has drawbacks, as the dynamic, object orientated nature of the Zope product is one of its strengths, and you are deliberately limiting that. However, so long as you don't have a huge churn rate in terms of data, I see no reason that it couldn't be made to work.
You would then have the advantages of Zope management side, and good ole HTML docs server side. Depends on the individual site, I guess