Start with shop/base.html. That's the core of the store. Overriding a template doesn't simply mean changing some CSS rules. If it falls to completely rewriting the HTML of the templates, that's fine, too. You're not expected to hold on to the original HTML. Izantal makes a good point on keeping the templatetags, of course, since those are already there ready for what Satchmo's views return.
Other important templates are, of course, product templates, checkout templates (for whichever payment module you choose), cart.html, etc. You'll find that starting with base.html will get you on the right track to finding out which templates need further overriding. Best, Bob On Tue, Oct 13, 2009 at 12:31 AM, lzantal <[email protected]> wrote: > > Hi > > On Oct 12, 2009, at 6:12 PM, David Marcin <[email protected]> wrote: > > > > > Hi all, > > > > I'm putting up my very first Satchmo store, and I have a question > > about overriding templates. The suggested method I've seen is to just > > pull in the templates you need to modify and override those. > > > > My question is: Do people use this in real store situations? > Yes I do. The store is not open to te public yet but I will post a > link when it is. > > That is, > > when you want to apply a custom theme and layout that is very > > different from the default store, it seems to me that figuring out the > > tweaks to the default templates is more trouble than rewriting your > > own custom layouts from scratch. Have others found this to be the > > case, or am I simply Doing It Wrong. :-) > > > When I am changing the default template I throw away the HTML and > replace it with mine.I keep all the django template tags. > > I also create a base_site.html file which extends base.HTML. > In my temlates I extend on base_site.HTML. > Also any app template I override I create a base.HTML this way I can > add any app specific js or css. > > I hope it helps > > lzantal > > > If others feel that using a full set of custom templates is the way to > > go, it would be helpful to have a list of the "essentials" that > > satchmo needs to function. e.g. the important POST commands / views > > that drive the store backend. Having this in the documentation would > > be great, and if nothing exists already, I'll look into putting > > something together for review. > > > > Thanks, > > David > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en -~----------~----~----~----~------~----~------~--~---
