I work on Yahoo Store on a nearly daily basis, and the way they do things works fairly well. You have a set of templates which you can apply to items in the database. On the edit side you can click through the pages, and they are generated dynamically so it's possible to edit them and get instant feedback. You can also not worry about testing things out because only you can see them.

When you are ready to publish, it runs anything that has changed (I'm pretty sure every row in the database has a flag to let the system know if it has been modified) through the templates to generate static html. This reduces server load and tends to be more more search engine friendly.

This model seems to work well, and I'm sure implementing something along these lines would give you the best of both worlds.

gav^

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.