Hi Eric!

> Good point, I can run the ‘content’ through Html2MarkDown(http://html2markdown.com/) before it goes into a front-matter formatted markdown file.

Brilliant!

> Also as a quick note, Jekyll (probably Middleman too) can handle simple HTML markup and markdown together in front-matter formatted files, so this might not be an issue.

I think for legacy posts it might be fine but in terms of readability I am of the opinion that it would be _best practice_ if blog posts/content would mainly consist of clean markdown files with as little markup as possible as:

* Vanilla markdown is a very readable format in itself

* Encourages others to contribute as each post/page is essentially a simple text file with no potentially confusing markup

* Makes the content somewhat platform agnostic as you can take those markdown files and do whatever with them (eg. print and bind a book!)

Rey

-- 
reyhan.org

On Wednesday, 8 January 2014 at 11:15, Eric Schaefer wrote:

Also as a quick note, Jekyll (probably Middleman too) can handle simple HTML markup and markdown together in front-matter formatted files, so this might not be an issue. 


On Jan 8, 2014, at 12:11 PM, Eric Schaefer <omg@eric-schaefer.com> wrote:

Hi Rey - 

> Just had a look at `entries.json` that's on the ticket and noticed the markup in the `content`.
Good point, I can run the ‘content’ through Html2MarkDown(http://html2markdown.com/) before it goes into a front-matter formatted markdown file.

> When you export to markdown, for example, would this be a clean markdown file per post with frontmatter, etc?
Yes, this is the plan. Separate markdown files per post, front-matter formatter (or another format depending on the site generator)

Eric


On Jan 8, 2014, at 11:50 AM, Rey Dhuny <rey@spcshp.com> wrote:

Awesome!

Just had a look at `entries.json` that's on the ticket and noticed the markup in the `content`.

> I can export each post into a markdown file or whatever format the community decides on for the static site generator. 

When you export to markdown, for example, would this be a clean markdown file per post with frontmatter, etc?

Rey

On Wednesday, 8 January 2014 at 10:37, Eric Schaefer wrote:

I have scraped all the old blog posts with a small ruby script that I threw together.

They’re all stored in a JSON file, and I can export each post into a markdown file or whatever format the community decides on for the static site generator. 


Just FYI so we don’t duplicate this effort.

Eric
 

On Jan 7, 2014, at 1:50 PM, Eric Schaefer <omg@eric-schaefer.com> wrote:

Hey everyone, I’m new to the Tor community (Hi!) but I’ve had some relative success with migrating Drupal blogs to other formats. 

As the debate around which static site generator starts up, I figure that I could help with just moving the old posts out into usable HTML chunks (re this). 

Could andrew/lunar point me where to get a snapshot of the database and code for the blog? Thanks!

-ultrasandwich


________________________________________________________________________
Tor Website Team coordination mailing-list

To unsubscribe or change other options, please visit:

________________________________________________________________________
Tor Website Team coordination mailing-list

To unsubscribe or change other options, please visit:
https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team


________________________________________________________________________
Tor Website Team coordination mailing-list

To unsubscribe or change other options, please visit:
https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team