wbamberg

## Scraping chapter lists It's going to be tricky to scrape documents that use Next/Previous into the model proposed here, because the Wiki docs don't provide enough information for the...

@chrisdavidmills > So you are saying that the code that builds these links would have an option to include the "^ Overview" type links, or not, depending on your needs?...

Something like what @joedarc says. But having slept on it I'm not sure any more that this is a good idea. The `"examples"` in reference docs are a different kind...

Of course most of the code in the renderer is the code that actually renders each live sample, and that would be totally sharable.

> Could have an `` component along with `` component and abstract out some of the reusable pieces? I think this would be the way to go. If we end...

> Relaxing the linter would probably mean that we will end up not deep linking correctly into specifications sometimes. On the other hand, the case of a top-level document (like...

One thing is that BCD has "standard_track", which inverts the meaning from "non-standard". I think it would be nice to represent this in the JSON as "non-standard", though, since that's...

I've been thinking about this and here's the weird thing. Currently, pages point to recipes. A recipe lists the things (ingredients) that should be present in a doc, and we...

> To further complicate things, what about a fourth option: > > In recipes, we use `prose.some_section` to show that we expect some Markdown (and, in scraping, some H2 in...

At the moment, the situation is like this: * for every file in /content with a `recipe` property, build-json makes a standalone JSON object saved as a file into /packaged....