or
tags>within their document for the correct paragraph spacing? How about links to>other documents? I have tips next to the HTML form that tells the editor>about HTML tags they might need to include in the article text (like: for a>paragraph return put in a
tag.)
and
not required, try wrapping in in the [pre]tag[/pre] as a testto see if that might help. We don't embed html inside our docs. Nevertried to even let these people do this. Reference to other html docs arehandled out of the data base not inside the doc. Now that is the way we doit. Doesn't mean it is right for you.>>My idea was for the editor to input a story into an web form and then the>story would be flowed into our template that formats their story and the>page. I then use a [writefile] to create the html page. My thinking is that>stories would be entered into the story.db, they would reside there for the>editor to work on. Once the story is final, they would publish it to the>web site using [writefile] (The reason for the actual html page was for>search engine spiders as discussed in many previous posts.)All our tech docs are on our private area of your servers so the searchengine part is not a issue for us. The public can not get to them. But Iassume the would pick up the text using the [include] tag>After the story has been published, the record from story.db would be>removed (or maybe not). The published story info (Title, Author, Keywords,>Filename) would then be placed into another database that would allow>end-user searching.>>Am I making this more complicated that it needs to be?>>MarkNo not really. You biggest problem is getting a large story into a placeto edit online. Maybe siteedit pro might be away to go to do the editingof the [included] file...Jay, John, Grant, somebody else want to chime in on using siteedit to writethe story part and then include it into an html doc via [writefile]===============================================Gary Richter PanaVise Products, Inc. 7540 Colbert Dr. Reno, Nevada 89511 Ph: 702.850.2900 Fx: 702.850.2929 Email: grichter@panavise.com http://www.panavise.com===============================================
Associated Messages, from the most recent to the oldest:
|
or
tags>within their document for the correct paragraph spacing? How about links to>other documents? I have tips next to the HTML form that tells the editor>about HTML tags they might need to include in the article text (like: for a>paragraph return put in a
tag.)
and
not required, try wrapping in in the [pre]tag[/pre] as a testto see if that might help. We don't embed html inside our docs. Nevertried to even let these people do this. Reference to other html docs arehandled out of the data base not inside the doc. Now that is the way we doit. Doesn't mean it is right for you.>>My idea was for the editor to input a story into an web form and then the>story would be flowed into our template that formats their story and the>page. I then use a [writefile] to create the html page. My thinking is that>stories would be entered into the story.db, they would reside there for the>editor to work on. Once the story is final, they would publish it to the>web site using [writefile] (The reason for the actual html page was for>search engine spiders as discussed in many previous posts.)All our tech docs are on our private area of your servers so the searchengine part is not a issue for us. The public can not get to them. But Iassume the would pick up the text using the [include] tag>After the story has been published, the record from story.db would be>removed (or maybe not). The published story info (Title, Author, Keywords,>Filename) would then be placed into another database that would allow>end-user searching.>>Am I making this more complicated that it needs to be?>>MarkNo not really. You biggest problem is getting a large story into a placeto edit online. Maybe siteedit pro might be away to go to do the editingof the [included] file...Jay, John, Grant, somebody else want to chime in on using siteedit to writethe story part and then include it into an html doc via [writefile]===============================================Gary Richter PanaVise Products, Inc. 7540 Colbert Dr. Reno, Nevada 89511 Ph: 702.850.2900 Fx: 702.850.2929 Email: grichter@panavise.com http://www.panavise.com===============================================
grichter@panavise.com (Gary Richter)
DOWNLOAD WEBDNA NOW!
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...