Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AMP web version #1

Open
NathanWalker opened this issue Jul 22, 2018 · 1 comment
Open

AMP web version #1

NathanWalker opened this issue Jul 22, 2018 · 1 comment

Comments

@NathanWalker
Copy link
Member

From @goelinsights on April 23, 2018 19:13

Trying to understand the docs. Sounds like if it needs different HTML templates, then it would go under a xplat category rather than an app?

Therefore would we need to create an xplat/amp directory? Sounds like that will be the structure for the upcoming ssr?

Copied from original issue: nstudio/xplat-issues#2

@NathanWalker
Copy link
Member Author

Good question @goelinsights - You can place platform specific templates in your app or inside the appropriate xplat/[platform] directory. Creating a component template inside xplat/[platform] largely depends on whether you intend to use that view across several different app targets. Oftentimes I may build it xplat/[platform] for the scalability if I foresee a need for that view in another accompanying app.

xplat/ssr is planned and will be the place for Universal and Amp powered setups you are correct.

We are currently working through a few details around the ssr integration to ensure it's clear enough for an upcoming release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant