mysociety / ainow Goto Github PK

We need to be able to attach various "resources" to presentations for further information. I'm assuming these will either be links or uploaded documents, but that we'll present them all as a bunch of links (perhaps with a title and some guidance as to what they are and why they're there).

There's still code for AINow in HomeView which had a livestream during the conference and switched the homepage afterwards to reference some specific talks. This will break the site (because the presentations it references don't exist), so we'll need to do something about this before then.

@wrightmartin - This is just a placeholder to make it clear what you're working on. Feel free to split up into whatever makes more sense to you if needs be.

Used by workshop ('leaders') and conference ('speakers')

Before the conference we need to be able to link from the detail of a talk to it's relevant theme(s).
After the conference we need to be able to organise talks by theme.

add local media storage (not encoding/transcoding)

We need to be able to add approx 5 pages for the main "themes" of the workshop. Each page will have some content, and also a set of uploaded documents (papers to read mostly), which presumably might each need a title and individual introduction/description too.

Any field where it's possible to enter multiple lines of text should probably accept Markdown so that it can be nicely formatted. (Except maybe things we might want to truncate like talk abstracts).

So that we can collect all of the detailed info about them in one place, embed the video etc.

We need to be able to provide a unique link for each participant in the workshop (given their email and name) that can be included in a personalised email to them. Ideally this would drop them straight into editing their profile (perhaps after setting their password first?).

req. from SB to change the link from below the name of each organiser to their name.

I would argue this is less obvious and may cause issues elsewhere as I assume names are supposed to link to their own page in the site, with the sessions that they're running.

Initially, because we were unsure of the speakers for the 2016 conference at the point of building the site we did not include explicit 'speaker' objects in the way we did for AINow.

Now that the conference is over we do know who each speaker was. In addition we also know who each speaker was in previous years, which we would now like to add.

Stuff like changing passwords, emails etc sets a message at the top of the page - we'll need to use bootstrap's styling to make that look good I guess.

Create a shiny new sub-app with its own theme and content to promote TICTeC 2017 (and, in time, provide things like delegate lists to attendees).

We currently have two aliases setup: info@ and rsvp@. It seems like the latter is no longer needed, but we need to add a third: ainow@.

At the moment these just forward info on, but we need to be able to send mail from them as well, ideally via a new, shared, gmail inbox.

There should be a way for the AINow admins to add generic pages of content to a section of the site, so that they can structure some supporting information, introductions to the topics etc.

https://github.com/mysociety/django-info-pages seems like a good fit for this.

Minor bug

So that we can send them reset links.

part of #53

This will need some design though from @wrightmartin and then some work to manoeuvre the content into the new IA.

This line: https://github.com/mysociety/ainow/blob/master/Vagrantfile#L66 needs to activate the venv, relying on conf/post_deploy_actions to do it doesn't work

I think we need a little bit more info about how things will work on this regard before I can commit to an approach here. Will we expect workshop/conference people to be totally separate? How will the workshop people get to the private sections? How much do we need to keep the workshop secret?

Presumably the videos will be hosted elsewhere (e.g. YouTube or Vimeo) but we'll want to embed them nicely on the page for each talk.

We need a simple way for admins to manage an FAQ page (with separate sections/headings that can be pulled out into a menu), or possibly two (for public and private events).

A little more involved that you might think but, as much as possible we should

• improve documentation for others to pick up and use this
• improve tools available for those who wish to 'vagrant up and go'
• genericise as much as possible, specifically away from the original project.
• rename this repo

Right now we have a user record, and it can optionally have a speaker profile or an attendee profile.

I've been working in #10 on the mechanism for people to edit their speaker profile, but it seems like we might have to have some way of transparently (to the user) knowing that they're speaking or attending (but not both?) So that the right people can fill out the right profile. Perhaps even copying their speaker profile to their attendee profile or some such?

Within the main structure of the site, there will probably be blocks of content (welcome text, footer stuff, etc) that it would be good to be able to manage from the admin, even though the majority of the page comes from code. Again, markdown processing seems like it would be the best way to handle this.

Had one report of the text not rendering at all on Linux with Chrome.

Unable to reproduce so far, but will keep looking into it

in order to help administrators add new/preceding years to their event.

This references presentations that don't exist so will break once the conference date has passed.

This title is misleading. SB would like some postgrads students to help lift and shift the shedules/content from those pages.

What this ticket should read is 'add multiple years to event tracks'.

The approach discussed to implement this is to abuse the current, multi-schedule support for AInow and the fact that FAT/ML has only one schedule to add new schedules for previous years and present them as such.

In the end, AINow have done RSVP's directly via email instead.

For extra points: have an option!