No, there is no preview for updates, but you already knew that. We have preview when editors make updates, so such a feature is feasible. I don't expect schedules from volunteers so I won't say anything more about when such might become available. Certainly don't hold your breathe. (:
I think a scheme that might scale better would be to post an improved answer and let Q+A Editors remove duplicates (and do other clean-up if needed).
- This allows all to notice the improved answer immediately (even if it takes 2 weeks for a Q+A Editor to do something about it)
- This means all can help with improving the content instead of forcing only Q+A Editors to write improved "copy"
- This likely reduces the amount of admin work required by editors (Q+A Editors can't delete replies to answers so they'd have to get 3 editors to help them, while they can, acting alone, delete a duplicate answer)
For trivial updates, a /msg to Q+A Editors is probably preferred.
-
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.
|
