hamakor / pycon-israel Goto Github PK

On Heroku deployment: If you go to COC or to Venue pages, you see that the title of the sidebar is "Sponsors" even when we change language to Hebrew.
This is because "gettext" is not included in the Heroku Python buildpack (so the dyno does not have the lib, and ./manage compilemessages fails with an error).

Possible solution is to git-add the translation. Other might be to add the missing package. e.g. this https://github.com/grauwoelfchen/heroku-buildpack-gettext

Allow mails to be sent from the website. GMail appears not to be a viable solution (does not allow to set sender email, always sends authenticating account).

We need to design and implement the display of sponsors -- certainly on the home page, maybe also on the sidebar? do some weighted lottery and present one of the sponsors each time there?

It is visible e.g. on https://il.pycon.org/2018/en/speakers/profile/134/

It is much more convenient for attendees if they can prepare a "selected agenda", showing only the presentations they're interested in. This should have some sort of persistence, so it stays on their mobile browsers when they're offline (and when they're online, of course).

It should present a personalized aganda.

Bonus point: Support more than one presentation per slot
Bonus point: Support setting some sort of reminder or calendar

That's just what comes to my mind. Some client-side expertise seems required.

Tested on Firefox:

1. In the log-in screen (choose sign-up or login option from main page), the navbar text is hidden and the language buttons overlap the sponsors tab
   

2. IMO, the orange color of the language changer buttons (in main page - not in screenshot above) is too low-contrast against the surrounding blue & red. Maybe using a background, or a different color would make them more readable?

3. On "Code of Conduct" page, we see both the title that's in the markdown and the page title, which are very similar, one below the other. Would be better to show just one (the longer of them)

4. Missing favicon

5. Header title (shown on browser's header) is missing the page title part for pinax pages, and the page- title part in the hebrew homepage is not bidi-separated (shown mangled)

English draft is there, Hebrew still required.

From main menu: remove

1. "sign-up" (we add managers manually via admin, sponsors/CFP/tickets are managed by external means).
2. "sponsors" (we wil manage through admin)
3. Login: this is up for vote: depends if we want to manage the site from production or have a separate staging site.

Probably declined:

• Temporary remove sponsors section from homepage and the whole sidebar. That's because I wanted to go live without them and add later
  (Since we did not go live in time, maybe better to just fix all the issues with sponsors section)

symposion sponsorship has a dedicated sponsors page (already available under the /sponsors/ URL, but currently removed from the sitetree).
I think we should use this for a page containing full descriptions of the sponsors. People might want to see the full sponsor descriptions without having to wait for them to be randomly chosen by the sidebar.

Also, this opens up the possibility for a sidebar containing all sponsor logos, as links to appropriate anchors inside the sponsors page (as alternative for displaying just one).
Also note that the sponsors full text will appear in the blog...

Footer links should include ways to contact us (mail, facebook, twitter), the website's own public repo, and probably also links to share/like on social networks.

Basically a view that does loaddata -- which will allow us to prepare data files and load them in without including them in the site sources.

It would be nice if this view can also handle media files.

At some point we want a solution which allows downloading "full data" (including both data and dynamic media) as a backup; if the "upload" solution can just take whatever the "backup" produces, it could be really nice.

Prepare a page listing all speakers, prefereably by category/track; keynotes, general, pydata.
also have it in the menu.
(i suppose speakers app already has it...)

I think we should disable the sign-up in production. Maybe even the login button - have them available only on "staging server".
If we keep using ti.to, registration would come through there, and I think also the sponsors would be simpler to handle by us via admin interface (I want to just remove the sponsors stuff from the menu).

The benefit of disabling login & signup is that we will not have to worry about the stability, usability & translation of the Dashboard (only we will see it), and as byproduct reduce risks of spam & security. As an example: confirmation emails are not being sent on signup now (would be nice if we would not have to worry about that).

Anyways, state your opinions. Once we decide - fix accordingly.

We need a blog for the conference.

One option is pinax.blog from https://github.com/pinax/pinax-blog/

probably should add a --exclude .heroku/python/lib/python3.6/site-packages to the commandline (which is in bin/post_compile hook)
Should check if pip installs the packages with .mo included and if we actually need these messages at all.

Showing, for now, just a general skeleton of the schedule, and maybe keynotes. Doesn't need to be ready for the initial website launch.

Because that's the right place for such things

Procfile is at the root of the project, and now creates a folder and a link before running the web server.

These belong in bin/post-compile instead

We have pages with language prefix, like /en/code-of-conduct/ and /he/code-of-conduct/ but if a user enters one of them with the wrong language chosen (through session or browser preferences) then they may get a mixed page -- Hebrew content in a LTR page with english menu and sidebar, or vice versa.

If the URL has a language prefix, we need to make sure the indicated language is active.

See https://docs.djangoproject.com/en/2.0/topics/http/middleware/ for Django Middleware, the right component for handling this
See https://docs.djangoproject.com/en/2.0/ref/middleware/#module-django.middleware.locale for the Django built-in language-selecting middleware

Thanks @AmitAronovitch for noticing

We need to decide what goes on the homepage and how. Our own past confs are not exactly available for review (changed to post-conf home pages) but we can take note from e.g. PyCon US

Find out how to define the SMTP settings on heroku so the site can send mails, and apply it.