User blog:Najevi/My wish list for blogs at Wikia

In no particular priority order:


 * Preview for comments: this will improve the quality of comments left by users and it will avoid the premature reaction to any inflammatory comment (comments currently need to be posted before they can be reviewed and edited by the author of the comment)

@najevi - have you tried ...
 * Make the timestamp beside each comment an anchor link: Suppose the timestamp provided a link to the current comment's unique page. Currently the only way to easily get to that page is to tediously search Special:RecentChanges for the comment's time stamp and copy the link from there. (When it is your own comment you have access to the history link right beside the comment.) Having this link handy beside each comment would allow a user responding to another user's comment via such methods as
 * to be specific about which comment (from among potentially numerous comments) is being referred to. Furthermore it would allow specific portions of the comment to be more easily quoted as part of the response.


 * Most recent comment at top: ahh ... thank you for this! Now if only my personal setting of this field was remembered each time I view a blog, any blog.

 Search announcements
 * Include the central blog space in forum search results: At central.wikia.com so long as Wikia have adopted the policy that Wikia announcements be made via staff blogs rather than via forum topics then those sometimes important announcements risk being missed by users searching for answers at the traditional venue.


 * More bytes consumed by the avatar than the comment: I am not a fan of eye-candy but I can appreciate that others do enjoy the display of some unique icon against their name. The sad fact remains that every visitor to a blog page downloads user avatars which consume more data bandwidth than the comment (and even the several comments by the one user in many cases!) It's a trivial matter to users whose ISP charges a flat rate for internet connectivity but there are less densely populated countries on the planet where ISP's either charge by the MB/GB or shape your broadband bandwidth after exceeding some arbitrary data down/up-load threshold. You don't need to visit a third world country to experience this ... although some might consider Australia to be at least a 2nd world country!


 * Date and time of original post: Although every comment bears a time-stamp the original blog post does not (unless the poster signed it like they do/should a forum post). Curious! (case in point is this blog)


 * Comment count is not updating: At Blog:Wikia_Staff_Blog the number of comments does not seem to update until a new blog is added to the list (or presumably any other edit takes place at Blog:Wikia_Staff_Blog). A small detail that may lead to confusion.


 * &lt;bloglist&gt; bug #1:Categories are being deleted whenever a blog is opened for edit. This bug was reported fixed in August but it is broken today.


 * &lt;bloglist&gt; bug #2:Regardless of whether or not the timestamp parameter is set to true or false a timestanp is generated.

FROM:                             TO: div#wk_blogs_article              div#wk_blogs_article div#wk_blogs_post                 div#wk_blogs_post - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  div.wk_blogs_link                  div.wk_date div.wk_date                       div.wk_blogs_comments div.wk_blogs_summary              div.wk_blogs_link div.wk_blogs_comments             div.wk_blogs_summary I haven't studied the box/panel style output as thoroughly yet but it's clear that what's good for one is not good for the other. The relevant div elements appear to be div#wk_blogs_panel div#wk_blogs_body - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  div.wk_blogs_link        ** div.wk_blogs_details span.wk_blogs_date span.wk_blogs_author div.wk_blogs_summary    ** div.wk_blogs_comments   ** The trouble here is that since no ID labels are used for these 4 key these elements they can only be identified by element.class selectors and as you know 3 of those are shared between the two different output formats available within ;&lt;bloglist&gt; tags. This makes specifying one desirable style for a compact plain/wide output format difficult without compromising the desired style for a boxed/narrow output format. In the long run I'd prefer a customization solution that does not require javascript.
 * &lt;bloglist&gt; needs id tags to allow CSS customization:Div element IDs are needed for the following to allow us to customize the layout and reduce wasted screen space. For the plain text output an example might be reordering (really a job for JQuery/JS and not CSS) the 4 main divs as follows:


 * I am a fairly patient sole but today I was tearing my hair out trying to tweak the plain text layout of a blog feed generated using ;&lt;bloglist&gt; tags. The problem is that the 4 key elements are not identified by an ID tag only a class label and unfortunately some of those same class labels are used in both the plain text output and the Boxed panel output.