amyjko / faculty Goto Github PK

They're scattered in a lot of places and hard to find.

• Move course data to a separate data file
• Make a course component
• Automatically generate the course list on the teaching page

That way viewers have options. Just add little links to the right.

Some events recur annually without exception, such as holidays, Ph.D. recruiting, etc. It would be nice to have support for this, so I don't have duplicate events each year.

The link is too small to be noticed.

They're currently strings. Prevents generation of consistently formatted lists.

It makes sense to highlight them since they are notable, get lost in my publications page, and are good resources.

It's a big ugly list right now. It also overlaps with the impact in the projects. Find a way to unify them. Perhaps make an impact data structure then symbolically link in the projects.

The bullets are boring. Add logos to the platforms and a fun photo of the office suite.

The current bars are a whole percent even when the hours in the month are only part of the month.

Move off the Gist. The formatting is inconsistent, the translation from GitHub markdown isn't standardized, and I can't easily file issues on the file. The barrier to this is how to represent it; it's currently GitHub flavored Markdown, and translating it to JSX would lower modifiability. One option would be to lean on GitHub's parsing service to render.

This will help others write good proposals.

It'd be cool to have their thesis statements.

Check out: https://jestjs.io/

Some of the super basic tests I might want to write:

• The React App component mounts
  • There are no console errors on any page

How about "6 people, 12 papers, 3 videos..."

Some categories of promises, such as travel, holidays, etc., are non-overlapping, leading to a large set of sparse rows that waste vertical space. Think of a way to collapse them, so the visualization is more dense.

One way to do this would be to collapse all categories into a single row. Some categories with a lot of promises (research), would stack high, but the others would not.

Move the projects page to a dedicated projects page, replacing it with a feed that has a bunch of block inline things with videos, papers, blog posts, tweets, etc.

Currently, all promises have a fixed weekly workload. But many kinds of promises spike over time. For example, if I'm working on a paper, I might work on it a few hours a week, but then it spikes at the deadline.

One way to specify this would be to allow all promises to have two hourly workloads, one to start and one to end, with a date in the middle when it spikes. Then I'd interpolate upward.

This will improve consistency and reuse.

They end up with a big whitespace gap, which is a missed opportunity.

List the official NSF grants and links to the official NSF pages.

There's a lot of null fields. Make them optional.

Likely an issue with the .htaccess rewrite rules passing the working directory but rewriting the path, which prevents build/app.js from loading.

The press should use it.

Have a route that goes to /project/name. Then, on the project page, just have a super short summary of projects rather than all the detail.

The big text list is kind of boring and the project annotation gives a sense of topic.

This is because we use weeks to compare whether we're in scope, and the last week has no comparison.

He's missing from a few publications and projects.

• Improves reuse
• Improves consistency
• Reduces defects

It'll help future candidates apply. Include some narrative about how I feel about them now. This could go on the advice page.

This way, people can report issues.

• Leads don't look like leads
• Contact info is ridiculous

The image directory is getting unruly. Move blog post images into a dedicated directory, as well as other image types.

I spend so much time on the cover images for my Medium posts, it’s a shame to not include them on my faculty page. Find a way to either link to them, or just do the work of manually including it in the cite.

Current, the direct links work by going to the page on which the content is displayed. It would be much nicer to have specific pages for specific content, such as a page dedicated to a talk or paper that shows additional detail. For example, a paper specific link could be a route like:

http://faculty.uw.edu/ajko/papers/irteval

And that page, in addition to showing the same data on the publication page, could include all download links, a relevant image from the paper, impact the paper has had, etc.

We'd do the same for blog posts, talks, books, and other content on the site.

This will make it easier to send links to particular topics.

I probably need to clean up my ResearchGate profile before I post this.

Need to tag the impacts with projects somehow.

Filter by project category at the very least, or potentially venue.

This would help junior faculty apply for promotion. This could go in the advice page.

It’d be great to have a single way of formatting all of the books I maintain, while keeping the content separately. Currently, everything is formatted in HTML, and making updates to the formatting requires a lot of manual edits to a lot of files. Instead, it’d be great to have a little library that I can include in each book repository, then just update the library to update the formatting on all of the projects.

This would allow me to remove the copyright block and also be more personalized.

Ensure that funding for my work is transparent, listing all institutions and people who I've taken money from.

They work when navigating within the app, but something is broken about the htaccess file.

One thing I observed is when clicking contact for email - its further expect to click to get email
link="mailto:[email protected]"

I know if someone really wants to find your email - then the idea is to click, I usually block new tab/popup in my browser, so it makes bit harder. You must be having a strong reason for it, but if not, pls consider to display straight under the header down
<br/><strong><a href="https://twitter.com/search?q=%23BlackLivesMatter">#BlackLivesMatter</a></strong>

P.S We support you and love all of your work towards diversity and educating the general.

This is the fault of recent revisions to the .htaccess file. The rewrite rules need to be conditional on the path requested.

I quickly hacked the promises page together without much mind for maintainability. Go through, comment, refactor for reuse.

The Medium publication page is too hard to navigate and not complete.

Must be a regression from React Router.

It’d be fun to add some photos to my long biography, to personalize the history. Find some representative photos from each era.