Mario Nebl

Thanks for the suggestion @Nosen. Currently there is no way to reference/import other code files into Markdown files. I am rolling around some ideas about this involving https://github.com/mdx-js/mdx but those...

Ok, understood. There is currently no way in patternplate to do this. I imagine a new widget could be implemented, e.g. ```js const React = require("react"); const {ComponentArtifact} = require("@patternplate/widgets");...

My bet currently is on patternplate‘s compiler resolving styled-components from its nested node_modules for the mono-repository scenario. Haven‘t verified this yet though.

> It would be very strange if it somehow would still resolve to this version of styled-components wouldn't it? True - I am debugging into this and my initial suspicions...

Thanks for your PR @anilkk! I'll have a closer look later today.

Good idea let's do this.

by @pixelass Documentation often provides an "edit on ..." or "improve this ..." link that opens the source on GitHub or similar. I would like to see something similar. ###...

Thanks for the suggestion @sandra0503. We might builds this enabling user-code to emit parts of the markdown files below a pattern demo, maybe a [widget](http://localhost:1341/doc/docs/guides/use-widgets?guides-enabled=true&reference-enabled=true&advanced-enabled=true) could do the job, too....

@sandra0503 Thanks for the suggestion. I think we def. should implement something like, probably using the `widgets` mechanics of patternplate: https://patternplate.github.io/doc/docs/guides/use-widgets?guides-enabled=true&advanced-enabled=true This could be part of a general push for...

Understood. Are you aiming for a declarative API or something like `yargs`?