Re: [tor-bugs] #10022 [Blog]: We need a new blogging system

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#10022: We need a new blogging system
---------------------------+-----------------------------------------------
     Reporter:  phobos     |      Owner:  phobos
         Type:             |     Status:  accepted
  enhancement              |  Milestone:  2014 Tor Blog Replacement
     Priority:  normal     |    Version:
    Component:  Blog       |   Keywords:  blog replacement upgrade www-team
   Resolution:             |  Parent ID:
Actual Points:             |
       Points:             |
---------------------------+-----------------------------------------------

Comment (by jmtodaro):

 == Current Status ==
 Here is an updated flow list to better reflect out current status:

 1. ~~Get the content migration from drupal to jekyll working.~~ -
 '''Complete'''
 1. ~~Get the comment migration from drupal to jekyll working.~~ -
 '''Complete'''
 1. Front-end development to implement tags, archives, events and search
 within jekyll - '''In progress'''
 1. ~~Create Juvia web app and integrate into jekyll for dev/testing~~ -
 '''Complete'''
 1. Jekyll and Juvia html styling. - '''In progress'''
 1. Setup transitional systems for testing complete data migration
 1. Test a complete content migration to our jekyll. - '''Ready'''
 1. Test a complete comment migration to our juvia. - '''Ready'''
 1. Pick a date, migrate content and comments to new systems.
 1. Document how to add posts to the blog for current authors.
 1. Setup blog.torproject.org vhost on static systems.
 1. Setup comment.torproject.org vhost in Tor infrastructure.
 1. On date, migrate content and comments to new systems.
 1. Shutdown drupal blog.
 1. A week later, decommission motor.torproject.org (current drupal blog
 machine).


 '''I've set up a live working copy of the dev site in its current state
 here: [http://tor.jmtodaro.com/blog/]'''
 Search, tagging, and archive functions have been added. The archives will
 require a bit more work if we want a navigation system and not just a flat
 list. Also I fixed the pagination links at the bottom of the page and
 added the ability to disable comments on posts (such as the tor weekly
 news) by adding "comments: disabled" to post front matter.

 Design-wise everything is still a bit rough around the edges. I will move
 on to polishing the css when the functionality is fully implemented.

 The test site currently contains 40 of the most recent blog posts and
 their respective comments (~3000 comments) imported to a fully working
 copy of Juvia. '''Please feel free to test the commenting system out.'''
 New comments will only appear on the test site, so go wild. If Juvia
 doesn't load right away, give it a few seconds as the heroku app goes to
 sleep after an hour of inactivity and can take it a bit to "wake up".

 [[BR]]
 '''A word on Juvia'''
 After implementing Juvia and understanding a bit more how it works, I must
 say that I have some serious concerns about whether or not this is the
 right comment system for us to migrate to. Here are a few highlights:

 * Juvia doesn't support nested replies, and only does inline comments when
 "replying". There is not even a "jump" link.
 * This completely breaks existing comment threads and make them very
 difficult to follow as Juvia sorts by date and there is no context to the
 comment it is replying to. Compare https://blog.torproject.org/blog/tor-
 browser-403-released#comments to http://tor.jmtodaro.com/blog/tor-
 browser-403-released/#comments . A crude workaround might be to
 programmatically insert a snippit of the parent comment into the replies
 or possibly a jump link during the scrape.
 * There is no way to close commenting on an old thread.
 * I'm not sure there is a way to differentiate between an actual author
 commenting or an imposter. I could be wrong about this if the user has
 moderator status, but I'm pretty sure juvia only supports one moderator
 per site.
 * Juvia is currently unmaintained. ( https://github.com/phusion/juvia )

 '''I will begin research on other solutions unless we are dead set on
 using Juvia.'''

 [[BR]]
 Last but not least, I've created a repo of all the scraped and converted
 data from our current blog. The most recent full dump is here:
 [http://github.com/jmtodaro/tor-blog-data/]
 When using these, it will be necessary to update the urls relative to your
 own dev environment.

 The development site repo can still be found here:
 http://github.com/jmtodaro/tor-blog
 ----
 == Todo ==
 * Implement author blogs/categories
 * Archive navigation
 * Site Description and footer links
 * Display start and end times on event posts
 * Clean up Gemfile cruft
 * Html styling
  * tag cloud
  * archive nav and results page
  * search results page
  * comments (if we switch systems)
  * markdown anomalies
  * events calendar and list

 [[BR]]

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10022#comment:39>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs