alpeterson wrote:

Some ideas about how to do this...
similar to redirect syntax...

#BOOK=[[page1]] [[page2]] [[page3|piped link]]

Or,

#BOOK
[[page1]]
[[page2]]
[[etc]]

#Header={{header name}}

we specify our header template here

#Footer={{footer name}}

We specify our footer here

#sidebar={{sidebar template}}

Books could be nestable, I'm currently trying to make [[m:Help:Contents]] into a
hierarchical / yet flexible listing of pages.. as a page is likely belong to
both the editing category and the system administration category...

-AP

zigger wrote:

*** Bug 1900 has been marked as a duplicate of this bug. ***

registered wrote:

Just registered to add a request like this one.
It would be awesome such a book could be exported to the PDF format :)
I'm interested in whether it is in the current road map?

Regards,
Zarco

mike.lifeguard+bugs wrote:

(In reply to comment #3)

Just registered to add a request like this one.
It would be awesome such a book could be exported to the PDF format :)
I'm interested in whether it is in the current road map?

Regards,
Zarco

Collection will do PDF exports. But we still have nothing in the database to identify collections (or books).

happy.melon.wiki wrote:

(In reply to comment #4)

Collection will do PDF exports. But we still have nothing in the database to
identify collections (or books).

I think Collection covers this request.

mike.lifeguard+bugs wrote:

(In reply to comment #5)

(In reply to comment #4)

Collection will do PDF exports. But we still have nothing in the database to
identify collections (or books).

I think Collection covers this request.

It most certainly does not, since there is still nothing *in the database* to identify collections/books.

happy.melon.wiki wrote:

What about all those book pages that enwiki is so pissed off with?

Marking as a duplicate of bug 15071, which already has as dependencies bugs for specific features which depend on this needed database structure.

• This bug has been marked as a duplicate of bug 15071 ***