John Hildenbiddle

@Jacco-V @Koooooo-7 -- I haven't tested this PR, but perhaps we can work with the escaped character limitations using one of the following approaches: 1. Allow titles to be wrapped...

@Jacco-V, @Koooooo-7 -- No arguments from me about the issues with building upon problematic legacy code. My comment was intended only to propose a way to make the stated drawback...

@trusktr FWIW, I don't think we need to test `marked` either. I only converted these tests from the old setup because I didn't want anyone to say "what happened to...

Thanks for taking the time to document the request, @illBeRoy. This looks interesting. I haven't had time to think this through, but here are a few thoughts off the top...

> @trusktr - I think `fetchRoute` is a better name than `beforeRequest`. They imply entirely different things. `beforeRequest` implies that it runs before a request, which is not what we...

Hey @illBeRoy. Thanks for the thoughtful breakdown and your willingness to work through the details. I agree we're talking about two different approaches, both of which address the route-focused use...

@illBeRoy -- Checking in. :smile:

@illBeRoy -- Sounds great. Looking forward to it. Happy to lend a hand if needed.

@illBeRoy -- Very excited to hear about your progress! Thanks for devoting the time and energy on this. Very much appreciated. :) > While it seems like an extremely convenient...

@illBeRoy > I see that in Lifecycle, we use function.length to determine whether or not the callback expects a next function ([here](https://github.com/docsifyjs/docsify/blob/develop/src/core/init/lifecycle.js#L42)). So I guess I'll go down that path...