Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
editoria
editoria
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 114
    • Issues 114
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 8
    • Merge Requests 8
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • editoria
  • editoriaeditoria
  • Issues
  • #229

Closed
Open
Opened Nov 12, 2018 by julien@julientaq
  • Report abuse
  • New issue
Report abuse New issue

Lumino specifications export needs

I've been working on implementing the UCP styles for the Lumino open access collection for UCP. To be able to export those books, there are a couple of things that needs to be done:

  • as paged.js is evolving quickly, would it make sense to use a cdn so we dont need to update the whole component every week until we reach a working version 1.0 (which is almost the case).

On the export:

  • Images name get transformed on import, which means that we can not style the image based on the name: for example [src*="something"] will let you style all the images that contains something in their name. This could be a simple solution until we have more control on adding classes and metadata to images.

  • When a fragment has no title, the component should not appear in the table of content;

  • When a fragment has no title, the chapter should start with a <header> element;

  • When a chapter starts with one or more epigraphs,they must be included in the header;

  • <cite> element should be included as the last child of the <blockquote> element, as they have multiple styling possible (inline OR block, depending on the type and location of the quote);

  • The title hierarchy in the HTML make things complicated to style, as same element is used differently (even using classes, as you're reccursively overriding style): we could have something like this (while keeping the class they have now)

style element
chapter title h1
heading 1 h2
heading 2 h3
heading 3 h4
  • The only list that should be set as an <ol> is the ordered list, all the other (including dialogue) should be <ul> (for style and semantics)
  • i also update the exported with a couple of script: working hyphenation regardless of the OS using hyphenopoly, pushing <h3> to the next paragraph to have inline headers, etc. We can update the exported html to include those, so it's made during the export as @yannis told me it should :D

Here is the html template i use with the scripts and the js libs template.html

@alexgeo do you see any question in here? Do you want me to elaborate more on some of those? We can create issue for that.

Edited Nov 12, 2018 by julien
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
No due date
0
Labels
None
Assign labels
  • View project labels
Reference: editoria/editoria#229