Site portal to static site

[neverendingqs]

What about converting the site portal to a static site? Right now it uses Django templates. I can work on that next.

From #350. Templates: https://github.com/PokeAPI/pokeapi/tree/master/templates

The 404 page might be useful as well: https://www.netlify.com/docs/redirects/#custom-404

Requirement: since we're using Netlify's Open Source plan, we need to give them proper attribution. An inclusion of their [logo[(https://www.netlify.com/press/) should do the trick, or maybe a "hosted by Netlify" statement in the footer.

[cmmartti]

Should the pokeapi.co portal be moved to a separate project? To me, it doesn't really make sense to keep it with the API. We would need to extract the static pages anyway to host beside the json files, and other people who self-host the API probably don't need or want the site portal.

What do you think?

[tdmalone]

^ I think that's a good idea. They're two different projects: a website, and an API =]

[neverendingqs]

I like the idea, but I'm not sure how to combine the two at deploy time if they are in two separate repos. Thoughts?

[sargunv]

The deploy script can simply clone all relevant repos and copy all the static files it needs into a single location

[neverendingqs]

The deploy script can simply clone all relevant repos and copy all the static files it needs into a single location

That's not available out-of-the-box. We can manage deploy keys, but I think it would be best to just put them in a different directory in this repo to keep things simple. We can always split them up at a later time.

[sargunv]

That's not available out-of-the-box.

Not sure what you mean. Netlify's build system appears to give the option of running any arbitrary command (and if not, another CI system certainly will) so it's just a matter of cloning relevant repos and cp. Am I missing something here?

[neverendingqs]

Sorry I forgot that all our repos are / can be public. I'm used to working with private repos at work, which means having to manage credentials / deploy keys to be able to clone another repo.

I still think it's simpler to manage everything in one repo, but I can support either option without the credentials issue.

[tdmalone]

If it adds complexity maybe it’s worth keeping them together until we’re up and running on Netlify and then we could look at the pros/cons of splitting them?

[cmmartti]

How about putting the website in a different Netlify server all together, then set up a proxy in Netlify to redirect requests from pokeapi.co/api/ to api.pokeapi.co? That way both projects can be kept completely separate and can be updated separately.

[cmmartti]

By the way, I'm still interested in doing this. Not sure why it shows that I'm unassigned.