cos-archives/cos.io

cos.io's Issues

Calendar

Google calendar plugin, it would be nice to take a look at what it would take to style it so that it matches the rest of the site.

Preregistration page not display correctly

Flowdock integration

http://docs.wagtail.io/en/v1.6.3/reference/signals.html gives us a way to send messages to flowdock when pages are published. This would be a nice-to-have.

MFR

MFR has a drop in renderer, lets make a block that a user can just add a ling and the mfr will render that document.

footer not displayed right on blog pages in phone view

Header

Header needs to be working. links in header should point to right pages, structure of header should reflect structure of the site.

Styling on the main page hero is off

How it looks on ours:

How it looks on cos.io:

journals model

create journal model, import .json data into database and display 3 different blocks

table in phone view is not displayed right

tables should shrink.

heroblock in phone view is not displayed right

Enable elasticsearch

It seems that elasticsearch isn't running, we should figure out how to make different areas of the admin panel searchable. We might need another dyno to run elastic on.

google map and photo stream are not exactly the same as the official website

You can click the google map on the official site and it gets to the large view. Clicking the photo stream will pop a window floating to show a larger one.

In our site, clicking the google map does not happen anything. The photo stream displays duplicated pictures and clicking one photo it will show at the very beginning of the page.

Setting color on the footer isn't functional

It's marked as a required field but there's nothing in the template to do anything with it

blog index template

Blog index pages and blog pages right now are not displayed in the right format. New templates may be needed.

Remove unnecessary static files

There are a lot of images that we don't need in there because we'll be using the upload facility to handle them. If someone uploads a file that overwrites one of these, the file will get reverted when the sit collects static again. Also it really slows down build times because it has to upload them all.

issues on phone

Check the website cosio.herokuapp.com on a phone and see if there are display issues. Create tickets if issues found.

clicking "open science platform" and "osf for meeting" does not redirect to the osf website

Get this repository merged into the COS centerforopenscience.org repository

We want to keep the history there, lets get this setup into that repo.

clicking tabs causes instability of display

I noticed that if we click tabs the display of the page will change a little bit. This causes instability of the display.

Better People Model

It seems like snippets are the wrong solution for a person model, and I think having a page required to exist for each person isn't right either. We should create a person class in earnest that inherits from Django's user model, so it would be trivial to give any person that is a user access to the CMS if desired. Let's take a look at http://docs.wagtail.io/en/v1.6.3/reference/contrib/modeladmin.html

We can still use the templatetags; doesn't have to be a snippet for that.

Parallax block

not sure if we really need this but it would be fun to do; making a block with a parallax scrolling effect like https://ihatetomatoes.net/simple-parallax-scrolling-tutorial/

Code block

such that the user can put in code, and the block will format the text correctly and add syntax highlighting. we should definitely use a js library for this. lets look at whats out ther and what will be the best fit.

footer in phone view is not displayed right

Refactor models.py

The models.py file is quickly growing and could easily get out of hand.

It might be a good idea to refactor out some of the blocks to their own module. This way we can:

• Better organize the few models that will be left over
• Not have to place blocks in seemingly random places because the need to be declared before or after other ones.
• Not slow down my editor on the giant file 😦

tabs block is fragile

js needs to be reworked/ reordering of tabs. delete the tab when the struct is deleted.

Forms

There is a need to provide a way to get feedback from users. There is a wagtail form editor, lets look at what that's like.

settings for blocks

it would be pretty cool to have an additional button here

for changing settings related to that particular block, like CSS, custom classes, maybe actions or dataset attributes.

Maybe a separate issue, but we should also have some way of editing css for the site as a whole. maybe this belongs in the settings > Sites > and we'd add tabs to this page. Styles might be handy stored as an hstore in postgres

To-do list for release

This ticket serves to keep track of all issues that must be resolved before this site is viable for community use. I encourage everyone to update this ticket as we find issues to get an idea of how close to release we are.

Punch list

• Fix offset navbar #177
• Make navbar orderable.

Better Jobs Model

Again with http://docs.wagtail.io/en/v1.6.3/reference/contrib/modeladmin.html, lets see how Jobs would look, giving a job listing page the ability to just have a listPanel where each item in the list would be a dropdown or something like that to include that job on the page.

[Jobs Page] Job listing

It would be more usable if the job descriptions made up their own block so that the HTML/JS is uniform and easy to extend

menu button in phone view is not displayed right

the menu button should be a blue block

The up picture could not be found

tab block is not working in phone view

tabs are not clickable in phone view.

News page

The news page probably ought to inherit from routable page mixin, http://docs.wagtail.io/en/v1.6.3/reference/contrib/routablepage.html, and news articles that are regular models http://docs.wagtail.io/en/v1.6.3/reference/contrib/modeladmin.html
This would enforce that all news articles exist under that news page.

gunicorn implementation

Use gunicorn for safer deployment.

Header is still off

On my 13-inch display, the header appears as the following:

[Jobs Page] What we do bubbles should be their own block

It would be nice to be able to have an individual block for these bubbles. This way an editor could upload the image to be used, and not rely on static links

Generic Column

Two column block and three column block could be combined and made to be more generic. It might make editing easier if each column were its own block, and we handled creating the row transparently in the template;

If we add a small checkbox in the corner of each block (or in a block settings pane) that would add a clearfix class to the element, we wouldn't need a dedicated clearfix block.

Though -- I hate clearfixes in general; can we make it use overflow: hidden to make the parent of a set of floats contain the floats? this way we would only have one edge case where the width of the columns doesn't add to 12, and if there were two sets of columns immediately next to each other. We can solve this be requiring contiguous columns widths add up to multiples of twelve.

Paginate rather than serve all articles.

https://github.com/HalcyonChimera/cos.io/blob/master/common/models.py#L620
We can't just dump every article in the database on the browser. can we find a way to paginate this? user would get say twenty articles, they'd scroll down, to the end of the list, it would say loading, and the next twenty would render. If they're at the end of the list it would say something to that effect.

footer default

we should create a fixture so that if there's always at least one footer in the database, and have a way to specify a footer as a default footer, that would automatically be selected for each page.

redis implementation

use cache to fasten website responses

Footer

Can we make the footer on each page customisable? like maybe put a selector in the settings tab for each page to pick which footer. Right now that's handled by an 'active' boolean; maybe that should be a 'default'? Pages also need a reasonable default for the footer; right now if there is no footer, the template wont render! lol...

blog title and authors are squeezed together in phone view

menu is not aligned well

There are so many elements in the menu that it's not aligned well. Need to decide what compromise to be done to make the menu realigned.

fix deprecation

app/.heroku/python/lib/python3.4/site-packages/blog/models.py:218: RemovedInWagtail17Warning: Using a tuple for search_fields on Page subclasses is deprecated, use a list instead

templates for sponsors + partners

improve organization model so that sponsors and partners blocks could be delivered automatically.

Customizing admin interface

Try to find a way to customize the interface of blocks the admin sees when creating different pages. For example, if the admin creates a footer, in the 3-column block, he/she wants to see the google map option. But if the admin creates a 3-column block inside an article page, he/she may not want to see the google map option.

Also try to customize the tab creating interface so it's more user-friendly.