May entail using flexbox to get the divs to expand easily to fill the space (already started work on this in the https://github.com/neurodata/neurodata.io/tree/flexbox-layout branch)

Ensure we have correct logos, etc. Bottom of the about page.

• Replace video files with updated files of higher quality/better compression
• Both the mp4 files load on safari
• Create low resolution videos for mobile users
• Replace .gif for mobile users with video element (autoplay video used to be blocked but no longer)
• GIF loads even on desktop (undesirable as it's 3.5 MB)

g.static
g.static()

Returns a StaticFile object corresponding to a static file contained within the pod. is the full pod path of the static file. You can access the path property of StaticFile.url to retrieve an absolute link to the file's serving path.

It is a best practice to always refer to static files using the g.static tag rather than referring to their URLs directly. This has the benefit of making URL changes easy and Grow will catch broken links to static files at build time.

Prior to using g.static, routes must be configured in the static_dirs property of podspec.yaml.

Uses the current document's locale.

{{g.static('/static/example.png', locale=doc.locale)}}

Uses a hardcoded locale.

{{g.static('/static/example.png', locale='de')}}

We have some old URLs to preserve, e.g., https://neurodata.io/bock11/ redirects to https://neurodata.io/data/bock11/. Some of these are published in papers.

A list of these can be found in the ndwebsite urls.py:
https://github.com/neurodata/ndwebsite/blob/master/ndweb/urls.py

I believe we can do direction with the S3 website hosting:
https://docs.aws.amazon.com/AmazonS3/latest/dev/how-to-page-redirect.html

and monitor cost

cloudfront is a CDN and should make the website load fast everywhere

and it allows using SSL certificate

• Bhatia et al. (2015) 👻 (worm 4&5)
• Vladimirov et al. (2014) 👻 (freeman14)
• Jarrell et al. (2016) 👻 (Cook et al / emmons12)
• Deisseroth et al. (2016) 👻 (kutten/tomer15)
• Bumbarger et al. (2013) 👻 (worm2)
• Dyer et al. (2016)
• Weiler et al. (2014)
• Wanner et al. (2016)
• Tobin et al. (2017)
• Takemura et al. (2013)
• Randlett et al. (2015)
• Lee et al. (2016)
• Kristina et al. (2015)
• Harris et al. (2015)
• Kasthuri et al. (2015)
• Hildebrand et al.
• Collman et al. (2015)
• Bock et al. (2011)
• Bloss et al. (2018)
• Bloss et al. (2016)
• BigBrain (Release 2015)
• Ohyama et al. (2015)

data tiles at the top and all the links at the bottom corresponding to that project

something like the "detail" page that mission supplied

using AWS Certificate Manager

blog post could be useful: https://medium.com/@sbuckpesch/setup-aws-s3-static-website-hosting-using-ssl-acm-34d41d32e394

for example, on this page:
http://nd-website-demo.s3-website-us-east-1.amazonaws.com/data/bhatla15/

within each column, i'd prefer stuff is either left-aligned or justified, rather than centered.
in general, fewer vertical lines is better according to modern design practices.

thus, justified is the default, but if it looks silly for some reason in some places, then i still prefer left-align over center-align

The default S3 404 page is a bit gory.

ndviz links are great, but ndwebtools has a lot of the metadata information displayed about the project on the experiment page.

• Synaptome
• Connectome
• Projectome

fwiw, i think color is nicer.

• data\kharris15_bg.png
• data\weiler14_bg.png
• data\takemura13_bg.png
• data\takemura13_thumb.png
• data\kharris15_thumb.png
• data\kasthuri11thumbtmp.png
• data\weiler14_thumb.png
• data\collman15\collman15dataset1.png
• kavli_fpo.png
• team\lee_albert.png
• data\collman15_thumb.png
• data\flyCNS_L1_thumb.png
• data\lee16_thumb.png
• tools\placeholder.png
• data\placeholder.png
• team\ryan-marren.png
• data\deisseroth_thumb.png
• publications\placeholder.png
• data\worm.png
• team\placeholder.png
• tools\ndmg.png
• tools\flashx_preview.png
• team\jovo.png
• data\vladimirov14_thumb.png
• team\zhu_luke.png
• team\liu_jon.png
• data\randlett15_bg.png
• team\sun_tony.png
• data\tobin12_thumb.png
• tools\clarityVizLogo.png
• data\weiler14\paperfigureplaceholder.png
• data\lee16_bg.png
• data\kasthuri11.png
• data\collman15_bg.png
• data\flyCNS_L1.png
• data\deisseroth_bg.png
• darpa_fpo.png
• data\vladimirov14_bg.png
• data\tobin12_bg.png
• randlett15_thumb.png

• ingest large vol
• meda
• flashx
• lol
• multiscale generalized correlation
• ndio
• ndmg
• neurodata parse
• ndreg
• ndstore
• ndviz
• nd web tools
• oopsi
• randomer forest

that eyeball goes to a default ndviz url, i think people will like that

should improve experience on mobile, and might only be needed on mobile

• Albert Lee (alum)
• Alex Baden
• Alex Eusman (alum)
• Ben Falk
• Carey E. Priebe
• Cencheng Shen
• Da Zheng (alum)
• Disa Mhembere
• Eric Perlman
• Eric W Bridgeford
• Greg Kiar (alum)
• Guilherme Franca (alum)
• Heather Gaddy Patsolic
• Jesse Leigh Patsolic
• Jon Liu (alum)
• Jordan Matelsky (alum)
• Joshua Vogelstein
• Kunal Lillaney (alum)
• Leo Duan (alum)
• Luke Zhu (alum)
• Michael I. Miller
• Misha Kazhdan
• Randal Burns
• Ryan Marren (alum)
• Tanay Agarwal (alum)
• Tony Sun (alum)
• Tyler Tomita (alum)
• William Gray Roncal (alum)
• Youngser Park
• Vikram Chandrashekhar
• Kwame Kutten (alum)
• James Browne
• Kaveh Karbasi

Bottom of the about page

think it could better explain where the content folders are to edit

1. references, i am guessing the easiest way to do this is to be able to import a latex bib, because i keep one of those up to date anyway.
   jordan might do something like that here: https://jordan.matelsky.com/resume/
   if there is a simpler way for you, then i can migrate to using that instead.

2. talks we've given. bibtex might be easy to import. ideally each talk would have a functioning link to slides.

3. awards, our team was won a number of awards, best paper/talk/poster/etc. we should be highlighting that.

This is the content file: https://github.com/neurodata/neurodata.io/blob/master/content/projects/projectomes.yaml

Remove mendeley link or point it somewhere. About page.

• ndstore
• Randomer Forest

so each item that is listed on data page has

• name
• description

i'm guessing each md file should be its own "page"?
and about can have a sub-menu?
happy to discuss at your leisure, not urgently, as tagged.

• when the window is relatively wide, the word "neurodata" feels too wide. i think it can be removed, and the side bar can be less wide
• the side bar background could be largely (or entirely) transparent

the page for projects feels a bit lame.
i'm not sure how to make it feel less sucky, some options:

1. in the vertical navbar, add a "+" sign next to data, which drops down the 3 projects, so people can see the projects if they want, and remove the page

2. change the nav bar to have a submenu containing the three projects under data.

3. just remove the page and the entry in the navbar, so it takes 2 clicks to get there, no big deal

4. make the page more dramatic somehow. like, make the tiles way bigger, and little movies or something, even with a bit of text next to each? i think this option is my least favorite, but open to it if . you think it is better.

https://github.com/neurodata/neurodata.io/blob/master/content/projects/connectomes.yaml

project page would have the "cards" that someone could click on to get the project page

YAML publication files:
name should be author and year
subtext should be Title

Makes it more readable and almost none of the publications actually were using subtext

What should it do? @jovo

i'm not entirely sure what needs to be done for this because changing route53 and adding an entry in cloudfront, but I'm also assigning @perlman because I'd like his assistance.