I'd go with what's easier to maintain.
If the static website is somehow related to your web2py app then I'd create it as a web2py static page. Should be less work :) Alex Am Donnerstag, 27. Februar 2014 02:56:12 UTC+1 schrieb Carlos Zenteno: > > I would like to have a website in front of web2py, > probably one of those one pagers that are in vogue nowadays. > > What is the best way to achieve this? > > An html page that links to web2py? > A web2py static page? > > I am thinking on having a blog too, > for that I either going to use one of the web2py blog apps > that exist or a Pelican static one. > Any advice/opinions on the two options? > > thanks again... > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
