Matthew Conlen

I wonder if upgrading to react 16 will provide an easy fix for this, since they've changed the way that errors in individual components affect the entire tree's rendering /cc...

This could be specified via the mechanism described in https://github.com/idyll-lang/idyll/issues/246

Thanks @jimidle! Yes - implementing this via a plugin makes sense, I just edited the issue to reflect the recent changes

That described syntax works on GitHub and agree we should match. For this to happen we'll need to update the [markdown link rule](https://github.com/idyll-lang/idyll/blob/master/packages/idyll-compiler/src/lexer.js#L288-L293) to recursively parse the contained text (as...

Ah yeah, I think your assessment is accurate. We'd need to replace the first `TokenValue` with a rule that could match bold, italic etc. Something like ``` LinkInline -> "LINK"...

That's a good point we defintely don't want that recursive behavior. I guess then we may have to make new rule to just match style elements that we want (em,...

Will keep this open because it should parse, but does `[Equation latex:"f \mathbin⨾ g \in \operatorname{hom}(A, C)" /]` work as a workaround?

Got it - thanks for reporting @suhr. That leads me to suspect the bug is coming from the compiler rather than the `[Equation]` component. I'll dig into it and report...

You can do this by using the page `template` option! To use a custom template, update your idyll build like so: ``` $ idyll index.idl --template=path/to/template.html ``` you can start...

Ah okay - for tables of contents, footnotes, references, etc, we are working on enabling that functionality via https://github.com/idyll-lang/idyll/issues/70