Static page support for events

dancerfly / django-brambling

Event website manager, specifically designed for dance weekends or other events with multiple simultaneous tracks of classes.

BSD 3-Clause "New" or "Revised" License

11 stars 3 forks source link

Static page support for events #227

Open harrislapiroff opened 9 years ago

harrislapiroff commented 9 years ago

We should provide basic CMS ability to add pages and template them so events that choose to do so can host their entire website with us.

melinath commented 9 years ago

This might need to be considered a separate service, depending on how complex it gets.

harrislapiroff commented 9 years ago

I think, for it to be effective at attracting events to our service, it will need to at least function as a single service. We could consider charging for it, but I think the draw would be sort of, like: Host your dance website with us! Also, now that you're signed up, we provide already-integrated registration if you want that!

harrislapiroff commented 9 years ago

Thoughts on templating:

More complicated: We can provide a full template system like secured Django Template processing or Liquid or what have you and provide forms necessary to shopping as template variables.
Less complicated: We can provide a simple template system where they just provide HTML that will wrap around our content. They would basically have to provide a single HTML template with containers that define head content and body content for us to slip materials into. (Often frustrating if they have a real web dev on staff who won't be happy about not having full control of the HTML).

harrislapiroff commented 9 years ago

http://www.shopify.com/ is probably the best example of a system that does this sort of thing.

harrislapiroff commented 9 years ago

Apparently OpenDance also supports pages like this.

melinath commented 9 years ago

I would be down with letting them put up static HTML pages created with a rich text editor, potentially. It would be pretty trivial to add support for text-only pages - though it would mean we'd need to redesign the masthead and such.

melinath commented 9 years ago

Should this just be static pages for now, then have a separate ticket for the CMS? Or should we make a separate ticket for the simple version?

melinath commented 9 years ago

Let's call this the simple version.

harrislapiroff commented 9 years ago

I think what we need to do with this ticket (maybe this is what you're proposing, I can't quite tell) is separate it into two features:

Arbitrary text pages (soon)
Custom Templating (someday, maybe)

melinath commented 9 years ago

Yes, that is essentially what I'm proposing.

melinath commented 9 years ago

But stated better :-)

melinath commented 9 years ago

Slash more correctly.