List view

• Peritext as a library

  Peritext should ultimately become a library focused on the fsTree-peritextSections conversions - contextualization-related and rendering-related modules should be separate module plugins. Web applications should then use peritext in their own way to organize, display or edit contents.

  No due date

  •2/2 issues closed
  100% complete0 open2 closed

• UC: scholarly blog ?

  No due date
  0% complete0 open0 closed

• UC: scholarly journal

  No due date
  0% complete0 open0 closed

• UC: scholarly book, one author

  No due date
  0% complete0 open0 closed

• UC: working draft

  Stephan wants to publish his Ph.D. and have some feedbacks from his colleagues. He needs to be able to share privately his working draft. His colleagues must be able to comment and advise on specific bits of information, from whole chapter to specific sentences or contextualizations.

  No due date
  0% complete0 open0 closed

• Static html/svg renderer for a document

  No due date

  •9/9 issues closed
  100% complete0 open9 closed

• Peritext v 0.1

  Peritext should work for at least one data source. Expected functionalities : * API functionalities * global folder parsing process * basic modulo-markdown functionalities * scholarly functionalities (glossary-handling, scholarly references handling) * figures management * css flexibility * basic responsive No editor at this step

  Overdue by 9 year(s)

  •

  Due by August 31, 2016

  •10/28 issues closed
  35% complete18 open10 closed