Things lost in bulk conversion from old site #5

Closed
wcaleb opened this Issue Jul 14, 2014 · 1 comment

Projects

None yet

1 participant

@wcaleb
Contributor
wcaleb commented Jul 14, 2014

The bulk conversion methods that I used (described in #4) were able to carry over most of the necessary structure and metadata from the old website. But some things that were in the original HTML pages did not survive the conversion process.

I'll divide these things into two categories:

Things Removed from Markdown Versions that Could be Automatically Restored with a new Bulk Conversion

  • comments (see discussion on #4; these can also be added back later with Disqus)
  • navigation links to "next" and "previous" lessons
  • distinction between literary and technical reviewers
  • nested url structures; all lessons are now under the lessons directory, whereas on the old site some (like the Zotero lessons) were under a subdirectory

Things Lost from HTML Versions that Can't Be Automatically Restored in Bulk

  • tables (we'll have to make Markdown versions manually)
  • images that were also hyperlinks, as well as figure environments and figcaptions (as documented on the repo wiki, we will need to add these back, manually, using Liquid template variables)
  • any kind of styling that depended on span tags or style attributes within other tags (the filename and username span classes were converted to Markdown inline code, but any attributes of those spans were lost; for example, the regular expressions lesson had some red and green highlighting spans that would have to be manually restored)
  • images that were hosted externally; these will currently show up as broken images in our markdown lessons; we'll need to locate the images and save local versions into our image directory

Things that are Style-Related that Can Be Added with CSS/Javascript

  • line numbers in code blocks

Please report other things that appear to have gone away in the bulk conversion, so I can categorize them on the above lists. If things come up that can be carried over by tweaking our bulk conversion workflow, we should do that before making tweaks to individual markdown files that would be overwritten by the bulk conversion process.

@wcaleb
Contributor
wcaleb commented Jul 21, 2014

Going to close this issue, per Skype conversation with editorial board, and open separate issues for things that need to be done.

@wcaleb wcaleb closed this Jul 21, 2014
@wcaleb wcaleb referenced this issue Aug 7, 2014
Closed

Check individual Markdown lessons for errors #15

38 of 40 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment