John M. Gabriele wrote: > I'm putting together a small site using Python and cgi. > > (I'm pretty new to this, but I've worked a little with > JSP/servlets/Java before.) > > Almost all pages on the site will share some common (and > static) html, however, they'll also have dynamic aspects. > I'm guessing that the common way to build sites like this > is to have every page (which contains active content) be > generated by a cgi script, but also have some text files > hanging around containing incomplete html fragments which > you read and paste-in as-needed (I'm thinking: > header.html.txt, footer.html.txt, and so on). > > Is that how it's usually done? If not, what *is* the > usual way of handling this? The basic idea is correct - but there are sooo many other people that had the same problem, and thus they creted web-framworks like e.g. CherryPy or Django or... and then there is ZOPE. Search this group for webframeworks, and you might get more answers than you wanted :) Diez
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4