<br><br><div><span class="gmail_quote">On 1/5/07, <b class="gmail_sendername">Moshe Weitzman</b> <<a href="mailto:weitzman@tejasa.com">weitzman@tejasa.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>> If you are looking for a one-way publishing system, where one group (editors)<br>> define what another group (readers) see, I think Drupal is the wrong choice.<br><br>i disagree. drupal is great for this application. see
<br><a href="http://www.angrydonuts.com/publishing_articles_a_tutorial">http://www.angrydonuts.com/publishing_articles_a_tutorial</a><br><br>a preview feature is a bit complicated and site specific though, so it does<br>not exist. it depends on the details of your workflow. you might tag all
<br>articles that will be published as 'edition 12' and then do a Panel or View<br>with 'edition 12' articles to see the next home page.</blockquote><div><br>Great suggestion, Moshe. I would put it even slightly more different:
<br><br>* Tag/put in a workflow called "Preview"<br>* Have a view / panel that is live + preview + preview-archive (the preview-archive is for, perhaps, articles that will go away from the live<br></div>* (optional) make a little code that moves all "preview" to "live" (and live to preview-archive)
<br></div><br>-- <br>Boris Mann<br>Vancouver 778-896-2747<br>San Francisco 415-367-3595<br>Skype borismann<br><a href="http://www.bryght.com">http://www.bryght.com</a>