nuprl / nuprl.github.io-archive Goto Github PK

I have a few blog post ideas, but they would all require some amount of inference rules and/or diagrams.

How would I do that?

Except for the first & last seminar,

• click the title
• admire the abstract
• click the title again
• abstract disappears, blank space remains

Jan pointed out that the old seminars don't show up as grayed out anymore. It looks like the mechanism to gray them was some javascript that compared the date, but it looks like that javascript has been escaped, which means it doesn't run.

Could someone who understands the generation tool, and perhaps what might have changed recently about it, help me out? (maybe @Benn, our webmaster?)

(also, if it's easy while poking around, the links to institutions don't work either. They have "@link" as the href...)

The PL research area page on the CCIS website should link here instead of the old website.

We also should think about whether that existing text should still be there or not.

E.g. Arjun's for Nov. 16th 2015 is listed as "1:00:00pm"

List in something like an info.rkt, and find a way to check that the dependencies are sufficient in the automated build, too.

I'm working on redoing the publications page to scrape DBLP, but I'd like to get some feedback on the idea. The work in progress is here: https://github.com/schuster/nuprl.github.io/tree/dblp-pubs

The general plan is to use DBLP as the (mostly) exclusive source of publications, filling in some manual entries for missing information as needed. We'll pull in the XML file for each faculty member (hard-coded), and use that to create the list of entries. Duplicates will be removed by comparing for same title and venue.

A likely incomplete list of open questions:

• What should we do publications without a faculty member author?
• What should we do about former lab members who published with us (e.g. DVH, Sam Tobin-Hochstadt, former students, etc.)?
• Should we filter the faculty publications to only be included if it was while they were part of Northeastern?

@howell or others, thoughts?

Pages like http://prl.ccs.neu.edu/new-members.html mention the prl students/staff mailing lists, but I can't find any links to sign up pages. Are there pages we can link to for that?

When zoomed in slightly on home page, when you scroll down you see a white bar below the top image but above the text.

Here's what the contact page looks like on an ultra HD monitor:

It would be helpful if the site used the large monitor more effectively, and the layout of people to contact was more visually efficient.

Maybe use Travis or something similar?

I should not have to manually add "finished" to the class list everytime we have a seminar....

I was looking at an an old blog post and it numbers in the code look nearly invisible because they are white on a very light background, see the part right after "ghci will tell us".

I see this is defined in https://github.com/nuprl/nuprl.github.io/blob/master/css/pygments.css , does anyone that cares about design have an opinion on what color it should be? Just scrolling through css colors, darkviolet is easy to read, but probably hard for colorblind people to distinguish from red.

This may be more of an upstream issue with Frog; I haven't looked into it. Just adding this issue as a suggestion.

We should update for old students who've graduated and new students and researchers that have joined this semester.

Move these olds to the alumni \o/:

• Asumu
• Paul

Add the newbs. Need pictures, titles and blurbs:

• Dan Patterson
• Ming-Ho Yee
• Prof. Heather Miller
• Filip Křikava
• Filippo Ghibellini
• Prof. Frank TIp

Dan just got here, but others are coming soon

There appears to be an artifact on the bottom of the picture when zoomed in.

This will prevent so much stuff on the page changing every time we re-build the pages (except when new talks are added, but that seems like a reasonable trade-off).

Page titles appear and disappear when it is not supposed to. This can be seen by scrolling up and down a bit near the top of the page.

Webpage stutters when scrolling, causing a very low frame rate. This appears to be doing a very large amount of re-rendering.

The seminar page claims Mitch Wand runs the PL Seminar, while the contacts page claims Amal and I are in charge of PL Seminar.

The two images on the teaching page looks a bit jarring.

The "Blog" link wraps to the next line on browser windows with less width. Also the blog header should have the main PRL page header.

Largish (~100 lines) chunks of code are duplicated between source files, such as the nav bar and footer. Even in files, there are patterns that could be abstracted, like seminar talk details.

Why are we not using a templating language? Particularly given the giant yellow letters on the home page: "... programming languages are therefore our fundamental tool."

http://prl.ccs.neu.edu/blog/blog/2016/05/03/nepls-on-may-31st-at-umass-amherst/ <-- the "blog/blog" looks funny

E.g. "Please don't let contracts be misunderstood"

Blocked on greghendershott/frog#162

Port this from the CCIS Grad Wiki, and then link from that old page to the PRL site (also maybe duplicate some of the general PhD getting started advice from the wiki, too, and link to the wiki from the site).

The twitter follow link at the bottom of the blog should probably be for neu_prl and not racketlang (it points to neu_prl on the home page, for example).

We should put instructions into the README on how to merge changes from the src branch into master. I just did it myself and figuring it out was a pain (partially because I hadn't dealt with git cherry-pick before).

@bennn You mentioned in #44 (comment) that you've just been using git cherry-pick, rebuilding, then commiting the auto-gen stuff. Is there some better way to do this until we switch to a full CI system? Seems like it's hard to make sure the two branches are actually consistent with each other.