Regarding the "simple conversion of existing HTML" part ... well, someone has to have knowledge of HTML in order to do this. With Krang you set up the skeleton of the document and provide objects that render themselves when published while simultaneously providing widgets (input boxes, radio buttons, text areas, etc.) that allow your users (editors) to enter in the content. But someone with a good knowledge of HTML has to set up the page framework, and someone with a good knowledge of Krang sets up the overall object heirarchy and Apache configuration.

As for "keeping the doc as a single HTML document," when you publish a page in Krang, you have a single, static HTML document. Your editors edit the document via a webpage form that you, the Krang developer create for your editors. It is possible to this without having to have your editors know HTML or HTML::Template, but you will have to jump through many frustrating hoops to accomplish this.

What it sounds like is that you want to have your cake and eat it too. Rarely is this possible, you have to make compromises. Krang indeed addresses these issues, but you have to do a lot of work to climb that steep learning curve. Since i myself do have a bit of Krang knowledge and experience, i would look into Krang to solve this problem.

I am of the belief, however, that people who want to make HTML pages should at least learn HTML or be prepared to hire skilled web developers. Would you trust just anybody to work on your car or house? Didn't think so. Why do people insist that the websites should have the ability to be built and maintained by unskilled people? :(

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

In reply to Re^3: Making static html documents editable, but still static. by jeffa
in thread Making static html documents editable, but still static. by leocharre

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.