Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to output into a single dom tree (html file) #988

Open
est31 opened this issue Jul 23, 2019 · 7 comments
Open

Ability to output into a single dom tree (html file) #988

est31 opened this issue Jul 23, 2019 · 7 comments

Comments

@est31
Copy link
Member

est31 commented Jul 23, 2019

Continuation of #301 after that one was closed.

Right now mdbook creates multiple html files and you are forced to navigate through them via controls. Right now books often have entire pages full of one headline, one sentence and otherwise whitespace (beyond index, search bar, etc). IMO this makes quickly skimming books unneccessarily hard. It'd be therefore prefferable to have the entire book condensed into one single html file. This pattern of serving both combined single pages as well as fractured snippets is nothing new, e.g. the GNU Make manual is offered in single html and multiple file modes as well.

This was referenced Jul 23, 2019
@heyakyra
Copy link

This seems like a duplicate of #982, while #301 was meant to be aboout the input being a single file.

@Dylan-DPC-zz
Copy link

thanks @heyakyra, but I told them to create this issue because it is different from SPA

@est31
Copy link
Member Author

est31 commented Jul 29, 2019

Lol, it's a bit confusing.

@heyakyra if I read your request correctly, what you want is to create a JS application that behaves to the user like the current thing except that more of it is done via JS. Is that right?

What I want is that mdbook in addition to creating multiple small files also creates a file that is a combination of all the small files into one big scrollable html file. Without any need for JS or fetch during the loading process (Chrome sadly blocks fetch on file://).

@heyakyra
Copy link

@est31 That's right, and I see now that it is different from what I suggest, but it is also still different from #301. So I was just suggesting to @Dylan-DPC who said in the other report:

Closing this since we can carry on the discussion on the new issue. Thanks

but I don't think it should be closed since it is different from mine and from this one.

@est31
Copy link
Member Author

est31 commented Jul 29, 2019

@heyakyra oh you are right, now I realize. This issue is different from #301. I originally got confused because I reported the single page question on another repo and it got closed as dupe of #301: rust-lang/reference#68

@Dylan-DPC-zz
Copy link

@heyakyra yes. I mainly closed it because it is an old issue and I didn't want to ping people who may no longer be concerned by that issue any more. Hence suggested to create a new issue :)

@depombo
Copy link

depombo commented May 17, 2020

What I want is that mdbook in addition to creating multiple small files also creates a file that is a combination of all the small files into one big scrollable html file. Without any need for JS or fetch during the loading process (Chrome sadly blocks fetch on file://).

I went through the thread across all the different issues and this is exactly what I think would work for my use case as well. I need a single HTML page with editable playpens so I am currently manually overriding the theme to hide the sidebar and other control buttons.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants