Yes, surely. As I mentioned, in this case optimal solution is to have static page with form in github, but form link should lead to google appengine backend (or heroku, or other free service).
The main idea is that AppEngine won't use caching by itself and if your site is under heavy load (not necessarily many users, but for example you put fat images here) your web site may have poor performance (especially due to vague AppEngine quotas).
For example one of web-sites I built CP-algorithms works this way - text content comes from AppEngine, but all javascript, css and images come from github pages. Both free.
I believe nowadays it is quite general approach to have static stuff separate from dynamic content...
Yes, surely. As I mentioned, in this case optimal solution is to have static page with form in github, but form link should lead to google appengine backend (or heroku, or other free service).
The main idea is that AppEngine won't use caching by itself and if your site is under heavy load (not necessarily many users, but for example you put fat images here) your web site may have poor performance (especially due to vague AppEngine quotas).
For example one of web-sites I built CP-algorithms works this way - text content comes from AppEngine, but all javascript, css and images come from github pages. Both free.
I believe nowadays it is quite general approach to have static stuff separate from dynamic content...
Ok