if the site is static why use a cms? just serve the static files, you won't get any faster than that
On Tue, Feb 5, 2013 at 8:37 PM, Steve Metivier <spmetiv...@gmail.com> wrote: > > - Project: Convert an essentially static HTML website and its attached > WordPress blog, to Django, to improve on its currently slow load time, and > to enable its functionality to be extended. (It’s currently implemented on > a platform that I believe introduces significant overhead at runtime, and > is very restrictive in extensibility. It’s on one of those “build your own > website with no technical expertise” platforms.) > I should note that I do have technical expertise, having been a > professional developer in C for many years, and I now have a decent handle > on HTML and CSS, but am a beginner with both Python and Django. > - The website is a famous quotes site. (It’s > www.InspirationalSpark.com<http://www.inspirationalspark.com/>, > if you want to take a look.) Each page focuses on a specific subject (which > its URL indicates), and is comprised of some introductory text, including > meta tags, followed by 12-20 famous quote entries, each made up of the > quote itself, it’s author, and a short description. Finally, there are > related page links at the bottom, and AdSense in several places. The > navigation consists of topic links in the left column, and there is also a > right column containing various elements that are shared on all pages. > - I envision each quote becoming a standalone object, so it can be > shared socially and, eventually, rated/voted. I intend for each quote to be > associated with a single topic page, for the most part. > - The purpose of the *blog* is to allow daily additions of new quotes, > which are scheduled as a “quote of the day”, go out to a feed, and are > posted to an associated Facebook page and to Twitter, and then listed on > one of the topic pages. I don’t actually want the individual posts to be > visible to the search engines, due to the thin content issue. They should > only be visible within one of the topic pages, and on the home page. > - It’s critical that the page URLs remain unchanged, due to the number > of inbound links that already exist, and current traffic (around 10,000 > views/day). > - I think what I’m looking for is a CMS, with a twist, to enable > multiple objects per page. > Here’s the long-term plan: > - Phase 1 – re-implement the website (separate from the blog), as is, > in Django, to hopefully improve its currently poor load time. High priority > is given to maintaining the current URLs completely, for SEO reasons, and > to time to production launch. > - Phase 2 – migrate the current WordPress blog to Django. > - Phase 3 – add social media buttons to each quote on the page – for > Facebook and twitter. > - Phase 4 – add user-created pages, where they can store and display > their favorite quotes, with accounts and registration. > - Phase 5 – add voting on individual quotes within a page. > - Getting to phase 1 completion is a high priority, even if it means > reworking components later to do so. > - The admin interface would need to provide for adding new quotes, and > assigning them to topic pages, plus adding new topic pages. In the current > Wordpress blog implementation, it’s very handy to be able to specify each > of the fields for a quote entry via a form, then pick the category from a > list. It would be nice to keep this type of interface. > - The scheduling of new “posts” feature is also desirable, so I can > batch up new additions, and trickle them out, updating the home page daily. > > > > The big question: Should I start with a Django CMS like Mezzanine, and > modify it as needed, start from some other open source project, or start > from scratch? > > > > Thanks. > > --steve > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at http://groups.google.com/group/django-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
