Nathan Walker

Precisely the reason for `xplat/[platform]` here. Once `ssr` support is available you would put your `amp` specific template handling in there. * Drop all your shared component code down to...

_From @goelinsights on April 23, 2018 23:20_ @NathanWalker that sounds awesome! Can't wait. Followup. I'll have two versions of SSR (AMP and normal web SSR'd for SEO purposes) + web...

As far as `admin` portion of your template code, there's a couple ways to handle that (outside of anything related to xplat really - just angular decisions primarily) you could...

Oh nice really appreciate your feedback btw, yes we can definitely plan on supporting `xplat/ssr-web` + `xplat/ssr-amp` that's an interesting idea. I'll think through that a bit and whether that's...

@johannesschobel always a great question. This explains the reason for it fairly well: https://nstudio.io/xplat/fundamentals/architecture But let me expand on a few things with a few questions: * If you build...

Thanks @phillipplum that helps explain - When creating app's without xplat architecture and plan to use purely Nx lib's yes you are going a more manual route and do have...

@johannesschobel That's correct. With our approach `libs` is intended to be "platform agnostic" (meaning TypeScript code that can be executed on *any* platform (no specific platform details within) and `xplat`...

@cjohn001 thanks for ping - I'm circling back here on Tuesday to see if can assist. I'll be honest I don't use these schematics myself (we use https://github.com/nstudio/xplat which accomplishes...

@cjohn001 thanks for update - If you run into trouble ping me on Slack and we can try to hop on Zoom together to gain more clarity.

@nongrata081 WebStorm and other IDE support is on todo list. There's some wip support in however some edge cases to handle so not ready for WebStorm yet. We have some...