@bmansurov - could you take a look at the a/c - I'm fairly certain that we will not be supporting the entire list, but wanted to double-check

paper size

Electron supports different paper sizes. We can keep this.

include table of contents

Table of contents exists in @Tgr's work. No page numbers though.

columns

Yeah, we can remove this option.

plaintext option (under format)

Yes, remove for now.

Make download option appear prior to Pediapress ordering option.

Why? I think Gergo's work integrates with Pediapress ordering page.

include table of contents

Table of contents exists in @Tgr's work. No page numbers though.

this is the option that lets us exclude the toc - would we still have that? I was under the impression we would have an auto TOC with no option to remove. If we still have it - no problem, we can keep it in.

Make download option appear prior to Pediapress ordering option.

Why? I think Gergo's work integrates with Pediapress ordering page.

Yeah, but users are more likely to print their own book rather than order from Pediapress (we're not removing pediapress, just it's weird that it's before actually downloading). I'll leave this one up to @Nirzar though

We can me showing the table of contents configurable. It's up to you.

Regarding Pediapress, I think I misunderstood you I mean the download page where users are able to order chapters and articles.

In T175681#3600103, @bmansurov wrote:

We can me showing the table of contents configurable. It's up to you.

Would it be configurable out of the box? If not, we don't really need to.

Regarding Pediapress, I think I misunderstood you I mean the download page where users are able to order chapters and articles.

Got it. Will make description clearer.

Would it be configurable out of the box? If not, we don't really need to.

If we don't code the UI part (i.e. we control it ourselves, and not let the user do it), then it's a simple change.

Here's a mock

Before

After

Changes

• Better form elements, textfields, buttons, dropdowns to match WMF styleguide
• Better sorting and ordering
• Better heirarchy of the page
• Prominent call to action to download
• upsell for pediapress

Yeah, but users are more likely to print their own book rather than order from Pediapress (we're not removing pediapress, just it's weird that it's before actually downloading). I'll leave this one up to @Nirzar though

totally agree, downloading is primary here. it is reflected in the mock

Looks nice! It needs a "create chapter" button though. And it would be nice if the mockup showed how chapters are displayed (the old layout uses an indented list; that probably doesn't look nice with the drag panels).

Looks nice! It needs a "create chapter" button though. And it would be nice if the mockup showed how chapters are displayed (the old layout uses an indented list; that probably doesn't look nice with the drag panels).

Thanks! forgot about that. let me put up another iteration

Updated the RHS a bit as well

Updated the UI for better hierarchy and layout

Much easier to understand

Looks good!

"Book creator UI" sounds like something that belongs to Collection, not to a rendering engine. Is the component right?

Is there someone working on this? The PDF creator was, somehow, reactivated (with lots of errors still), but creating a book is still impossible.

In T175681#7375961, @Theklan wrote:

Is there someone working on this?

No, there is not - the assignee field is empty and the task has "open" status. This applies in general.