pyconca / 2013-web Goto Github PK

In the same vein as the About page.

This includes:

• Getting content from the sponsorship team (when they're ready)
• Adding the English translation (use make i18n to generate the po files, and a second time to update the mo files)
• There's already a pair of routes set in symposion_project/urls.py, but they're not quite right (the "learn how to" button-link on http://2013-staging.pycon.ca/sponsors/ doesn't point there…)
• Adding a link to the navigation bar, below the masthead.

It's blank…?

Pages such as signup/ and login/ , this is because these Django forms have been overwritten by custom templates -- I will remove these templates and tweak a bit with the inheritance and CSS.

Try to avoid causing merge conflicts, so disabling may be a better thing than outright deletion.

Unless we can think of some reason to keep the CMS (but I don't think so, unless it can be configured to work like a wiki, then maybe…)

Add a venue page similar to http://2012.pycon.ca/venue

http://2012.pycon.ca has Google Analytics, shall we add it to http://2013.pycon.ca as well?

Design and implementation (if necessary, create a second implementation ticket later).

UI -- the final frontier!

Add messages/flashcards back.

Add a contact page similar to http://2012.pycon.ca/contact

Not for release guys -- hence no milestone.

It's the only page I've seen so far that goes edge-to-edge, as opposed to sticking to the central column. Missing a div somewhere?

Just a reminder to ourselves. :)

Should go to sponsorship/prospectus ?

Just wondering if it's a good idea to write tests for this Symposion -- it has 0% test coverage if I am not missing the something obvious. It does seem like a pretty big project to write tests for though. It seemingly passed the real life tests of being used for several conferences over the years without many hiccups..

Need to split settings.py

A) it should serve the 2013 site
B) The SSL cert should be for 2013.pycon.ca

And some "other" link to the dashboard.

We should probably set up a different externally facing email for volunteer signup, as opposed to [email protected].

The existing infrastructure only translates things from symposion_project as far as I can tell. It looks like a bunch of {% trans %} tags already exist for symposion, so I suspect it will look easy in hindsight. ;)

I am curious to see if we end up with a single .mo file for symposion_project+symposion, or separate translations for each…

Need to have complete copywriting. This ticket is a "make sure it's all there". There are separate tickets for particular areas of concern.

Translation's moved into #28.

Fonts are not web fonts, need to fix them using possibly: https://developers.google.com/fonts/

There is a link that pops up sometimes to download the prospectus -- definitely there. And maybe on the page where it says to email [email protected], add a sentence w/ href that lets them download it.

Prospectus PDF is here https://drive.google.com/a/pycon.ca/#folders/0B7SBXlan5cd3SFdxeG94Tnpmcm8

We should have a mobile stylesheet for the schedule, as a lot of people will be using it from their mobile. We can probably re-use a lot of the CSS and JavaScript from http://2012.pycon.ca/schedule

On pages that aren't the front page, we don't have the name of the event anywhere on the page other than a small logo and copyright notice in the footer (eg. http://grab.by/mgdE).

To match the current prospectus.

Add breadcrumb for proposal pages?

Add a venue page similar to http://2012.pycon.ca/venue

Assuming we are sticking to Guestlist to sell tickets.

Add CoC page, similar to http://2012.pycon.ca/conduct (?)

• Friday night "Party"
• "Talks" in morning and afternoon
• "Lunch" somewhere in the middle

That's the dashboard, speaker profile create/edit, and proposal create/edit.

This is a/the most important subset of #9.

Copied from #14:

List of pages that needs to be checked:

• Code of conduct page
• Contact page
• Venue page
• About page
• to_be_added

I've pinged our contact there to get the instructions on how people can book.

Right now I only see the 3 ticketing levels :)

Welcome Ideas for favicon!

Note: There are two! A bigger one at the top and a smaller one at the bottom.

WHITE on BLACK, outlines are a bit on the thick side?

Right now it's sitting very oddly at the bottom of the main page.

It would be nice if it said "Français" as well. :)

See also: https://twitter.com/brandon_rhodes/status/328156884039262208

According to @wolever:

# It's straight forward to make a route to do that kind of generic static rendering:
    url("sponsor/(.*)", views.some_function_to_lookup_and_render_the_template)

I suppose we might need something like that for each section ("sponsor", "speaker", "in the area", etc). Perhaps the lookup function can take some kwargs, more like:

    url("sponsor/(.*)", views.some_function_to_lookup_and_render_the_template, {
        {"template_directory": "sponsor/"}
    )

In the same vein as the old 2012 site.

This includes:

• Creating the template with {% trans %} tags
• Adding the English translation (use make i18n to generate the po files, and a second time to update the mo files)
• Adding a route in urls.py to render the About page (unless someone's already done #4, in which case it should hook up through that
• Adding a link to the navigation bar, below the masthead.