Fix #65: Plugins Architecture

[SamyPesse]

Fix #65

[SamyPesse]

@AaronO it's ready to be merged 😄

[AaronO]

Merged

[bebraw]

Great!

A couple of notes:

• You should mention the sample plugin at README so it's more obvious to people
• Would it be possible to add a hook for marked? That would come in handy if some people want custom syntax.

[AaronO]

@bebraw We'll document the sample plugin a bit more before the 0.3.0 release tomorrow.

To be honest, I'm against major modifications to the syntax when it can be avoided. Using a new syntax makes it harder for other people to reuse, understand etc ...

You've been mentioning adding syntax for doing your screenshot phase. What I would do if I were you would be the following.

Write a small quick n dirty parser either leveraging marked or regexes, that finds the screenshots to be made, write a grunt/gulp/whatever task using that and phantomjs to take care of the screenshots.

Have a Gruntfile/Gulpfile with two tasks, first get screenshots, second build book.

I think by wanting to bring the screenshot build process into a gitbook plugin you are coupling your system, making future upgrade potentially dangerous etc ...

And to be honest, I think it's best to be decoupled when possible. I don't really see the advantage of being coupled in this scenario.

Sorry if I'm not getting your pain point ;)

[bebraw]

No probs! It's definitely possible to deal with this scenario in two passes like you describe. I'll give it a go. :)