iris-hep / iris-hep.github.io Goto Github PK
View Code? Open in Web Editor NEWInstitute for Research and Innovation in Software for High Energy Physics
Home Page: http://iris-hep.org
Institute for Research and Innovation in Software for High Energy Physics
Home Page: http://iris-hep.org
I'd like to spruce up the presentation of a few project pages. One area where I could use particular help is best practice for embedding figures. Example:
https://iris-hep.org/projects/tpc.html
These are currently somewhat-ugly blobs.
What's the best way to tackle these?
related, some people from steering board etc. are being displayed. Eg. Paolo on the AS page
https://iris-hep.org/as.html
Maybe focus area leads should just edit which names have their focus area mentioned in the individual's yaml files.
It appears that people who have been marked as inactive are still appearing on the team lists, at least the overall team list and the focus area ones. What is the point of marking someone as inactive if they still show up? Please remove inactive people from “active” team lists.
Hello, I am using your website to set up the DANCEOrg website, but I am running into some issues with deployment. (https://github.com/DANCEOrg/iris-hep.github.io-source)
Help would be thoroughly appreciated, and I would be glad to contribute if that would be useful.
The step that is failing is the "Check RuboCop" step. I checked the permissions for the get_indico.rb and it returned that it has rwx. Also, not sure why the Assignment Branch Condition size for inspire is too high for our code but was not for yours since our code is the same.
Offenses:
_plugins/getpub.rb:129:5: C: Metrics/AbcSize: Assignment Branch Condition size for inspire is too high. [<23, 49, 20> 57.71/55]
def inspire(pub) ...
^^^^^^^^^^^^^^^^
_scripts/get_indico.rb:1:1: W: Lint/ScriptPermission: Script file get_indico.rb doesn't have execute permission.
#!/usr/bin/env ruby
^^^^^^^^^^^^^^^^^^^
Hi… something went funky here with PR #961
See
https://github.com/iris-hep/iris-hep.github.io-source/pull/961/files
you see the related-work: true
was removed and the citation was changed. But the website didn’t update properly.
Current version of file:
https://github.com/iris-hep/iris-hep.github.io-source/blob/master/_data/publications/1864766.yml
But the publication still shows up in related work section with old citation information. Caching?
Would be nice if a focus area page like this:
https://iris-hep.org/as.html
automatically listed the team members working in the area.
We have several publications that are in INSPIRE, but INSPIRE doesn't know about what conference they were published in.
We've been adding that with the citation
field, but that wipes out the author information.
Looking more closely, there seem to be several like this.
Examples:
1864766.yml
1858493.yml
It would be nice if there was a field that just added additional information (like note
or additional_info
that did not remove the author information pulled from INSPIRE.
We need an overview of all projects page.
The collaborations page (https://iris-hep.org/collaborations) looks a bit basic. At the minimum, each project should have a sentence or so on how they intersect with IRIS-HEP (not just NSF project numbers!).
Additionally, (at least) the following are missing:
Full team updates missing for:
University of Cincinnati - @mdsokoloff
University of Chicago - @robrwg
Main page of the website is now showing all events rather than just the upcoming ones.
Please review the contents of the IDDS project page here: https://iris-hep.org/projects/idds.html
Try to have the following
A student submitted a pull request that initially seemed ok as far as format. It passed through the usual checks as well. However, the page never appeared on the site. After some investigation is seems that the extra line feeds in the project_goal caused an issue. It was not obvious at first when I looked at the file. The only clue I had that something was amiss was when I viewed the markdown file in the github repo, it did not appear "formatted" as the other fellows' markdown files.
You can see the changes I made here:
ae1b3d5
It would be nice to sort the team, maybe alphabetically by surname or first name.
I only see presentations in the template
https://github.com/iris-hep/iris-hep.github.io/blob/master/_data/people/cranmer.yml
We have some projects that maybe don't need to be featured in the focus group.
Instead of deleting it, it would be nice if we could add a field in the project so that it is hidden on the focus group webpage.
Maybe the project webpage is still generated, just not linked off the focus group page.
As I'm not very familiar with Ruby (though I know a lock file when I see one) it would be helpful if there was a CONTRIBUTING.md
for the repo that outlined the expected development cycle and testing procedures for a PR before a core dev was flagged for review.
Some helpful feedback received from @davidlange6 on how to improve the pyhf
project page was
An example addition might be a gallery of results (basically graphics from the "use in publications" list).
There are already plenty of results that exist across the internet that can be shown, including results from SModelS, so this would be an easy addition.
A note to self: The pyhf
page is already pretty list-y, so maybe try to "lead with awesome" and get some of the example plot up at the top.
For team members on a given project, it'd be nice if we could show their profile picture instead of link to their homepage. More visually appealing and "personalizes" each project.
Please create a new Coffea Casa project page inside the DOMA area.
Try to have the following
As @henryiii pointed out, a test can be added (maybe even as a pre-commit hook?) to follow up his PR #83 to check that every person listed in an individual person YAML file also has their shortname
listed in an institution personnel listing YAML file.
I don't know Ruby or I would add it myself right now, but if no one beats me to it I could take a stab at it when I've finished my thesis (in a few weeks).
On the newteammember
page and the fellow
page, the instructions for adding presentations say that the url
field "should be a direct URL to the presentation file (e.g. pdf)", but in the last few PRs I've made to update my presentations, I was asked to link to the Indico contribution instead.
The footer does not display properly on fellows pages. It has a gap on the left.
I believe the work in the "modeling data workflows" activity are all wrapped up (https://iris-hep.org/projects/modeling.html). Let's scrub the page to make sure everything is correct and we list it as wrapping up at the end of the design phase.
Please review the contents of the TPC project page here: https://iris-hep.org/projects/tpc.html
Try to have the following
The following people are not in a focus area:
floe
andrewchien
vgvassilev
klute
haxxardoux
rct225
b_cousins
m-carothers
meevans1
evanmassaro
o_gutsche
p_koppenburg
talvandaalen
yk_kim
ioifrim
a_digirolamo
tatiana-m
jeyserma
k_kvdam
mdhildreth
d_costanzo
dpiparo
g_raven
HedgeMage
danielsibemol
936-BCruz
s_campana
m_norman
t_boccali
alanjoshua
d_swanson
kherner
g_stewart
e_s-kennedy
GuillermoFidalgo
sthapa
p_couvares
d_brown
Use focus-area: core
if general, or focus-area:
if there's no specific focus area.
https://iris-hep.org/about/team
There will be some duplicates, but seems ok.
hi @rct225 fyi - I was looking at fellow pages for a different reason
some potential inconsistencies (today is Nov 1)
Needs a fellow page Ajay,Rawat
Did a presentation but missing from the website
4eshanb.md -> presented Oct 25
FeistKyle.md -> presented today
HectorNoguez.md -> presented last week
SofiaGraziano.md --> presented today
decheine.md -> presented today
eric-moreno.md -> presented last week
AlanAneethJegaraj.md -> talked Oct 5
AneeshHeintz.md -> Oct 14 2020
AnishBiswas.md -> May 10 2021
Rahul-Agrawal.md -> Oct 25 2021
XiongfengSong.md -> Oct 14 2021
Add a collaborator "badge" for non-IRIS-HEP members in projects will have to be done manually Nevermind, may be automatic.
Today @msneubauer added the YAML for a new entry to the team page (me) (c.f. abda6c8) which we can see from the commit history that GitHub pages successfully deployed. However, the Full Team page isn't updating.
I haven't attempted to build the page locally and see how it looks, and won't have time for the rest of the week, but if someone has thoughts on this it would be good to fix and then see if checks can be added in the future for page deployment. (@pelmer as it seems that you've done most dev work on the site maybe you have thoughts for things to poke here) Maybe something like Netlify as it seems to be nicer deployment testing then ReadTheDocs.
The plan is to move the source repository for the iris-hep website to a new name, iris-hep.github.io-source
, on Wednesday some point after 15:00 EDT. There will be a small disruption in availability during the move. The website will become statically available again a few minutes later, and the Travis CI produced output will follow after that. This will enable publications to appear, as well as enabling PRs to be automatically checked for common issues.
Here are the missing tags that need to be worked on. If there's really no project associated with a presentation, then project:
(blank) can be added to silence the warning.
presentation #0 in _data/people/jlefevre.yml must contain location.
presentation #1 in _data/people/jlefevre.yml must contain location.
presentation #2 in _data/people/jlefevre.yml must contain location.
presentation #3 in _data/people/jlefevre.yml must contain location.
presentation #4 in _data/people/jlefevre.yml must contain location.
presentation #5 in _data/people/jlefevre.yml must contain location.
presentation #3 in _data/people/pelmer.yml must contain location.
presentation #4 in _data/people/pelmer.yml must contain location.
presentation #1 in _data/people/mweinberg2718.yml must contain project.
presentation #2 in _data/people/mweinberg2718.yml must contain project.
presentation #3 in _data/people/mweinberg2718.yml must contain location, project.
presentation #1 in _data/people/fatala22.yml must contain location.
presentation #2 in _data/people/fatala22.yml must contain location.
presentation #3 in _data/people/fatala22.yml must contain location.
presentation #5 in _data/people/fatala22.yml must contain location.
presentation #6 in _data/people/fatala22.yml must contain location.
presentation #7 in _data/people/fatala22.yml must contain location.
presentation #9 in _data/people/fatala22.yml must contain location.
presentation #10 in _data/people/fatala22.yml must contain location.
presentation #11 in _data/people/fatala22.yml must contain location.
presentation #0 in _data/people/wguan.yml must contain location.
presentation #1 in _data/people/wguan.yml must contain location.
presentation #2 in _data/people/wguan.yml must contain location.
presentation #3 in _data/people/wguan.yml must contain location.
presentation #4 in _data/people/wguan.yml must contain location.
presentation #5 in _data/people/wguan.yml must contain location.
presentation #6 in _data/people/wguan.yml must contain location.
presentation #7 in _data/people/wguan.yml must contain location.
presentation #8 in _data/people/wguan.yml must contain location.
presentation #9 in _data/people/wguan.yml must contain location.
presentation #10 in _data/people/wguan.yml must contain location.
presentation #11 in _data/people/wguan.yml must contain location.
presentation #1 in _data/people/drankincms.yml must contain location.
presentation #0 in _data/people/mmasciov.yml must contain location.
presentation #1 in _data/people/mmasciov.yml must contain location.
presentation #0 in _data/people/meevans1.yml must contain focus-area, project.
presentation #1 in _data/people/meevans1.yml must contain focus-area, project.
presentation #2 in _data/people/meevans1.yml must contain focus-area, project.
presentation #3 in _data/people/meevans1.yml must contain focus-area, project.
presentation #4 in _data/people/meevans1.yml must contain focus-area, project.
presentation #5 in _data/people/meevans1.yml must contain focus-area, project.
presentation #6 in _data/people/meevans1.yml must contain focus-area, project.
presentation #7 in _data/people/meevans1.yml must contain focus-area, project.
presentation #8 in _data/people/meevans1.yml must contain focus-area, project.
presentation #9 in _data/people/meevans1.yml must contain focus-area, project.
presentation #0 in _data/people/cranmer.yml must contain focus-area, project.
presentation #1 in _data/people/cranmer.yml must contain focus-area, project.
presentation #2 in _data/people/cranmer.yml must contain focus-area, project.
presentation #3 in _data/people/cranmer.yml must contain location, project.
presentation #4 in _data/people/cranmer.yml must contain focus-area, project.
presentation #5 in _data/people/cranmer.yml must contain focus-area, project.
presentation #6 in _data/people/cranmer.yml must contain focus-area, project.
presentation #7 in _data/people/cranmer.yml must contain project.
presentation #8 in _data/people/cranmer.yml must contain project.
presentation #9 in _data/people/cranmer.yml must contain project.
presentation #10 in _data/people/cranmer.yml must contain project.
presentation #11 in _data/people/cranmer.yml must contain project.
presentation #12 in _data/people/cranmer.yml must contain project.
presentation #13 in _data/people/cranmer.yml must contain project.
presentation #14 in _data/people/cranmer.yml must contain project.
presentation #15 in _data/people/cranmer.yml must contain project.
presentation #16 in _data/people/cranmer.yml must contain project.
presentation #17 in _data/people/cranmer.yml must contain project.
presentation #18 in _data/people/cranmer.yml must contain project.
presentation #19 in _data/people/cranmer.yml must contain project.
presentation #20 in _data/people/cranmer.yml must contain project.
presentation #21 in _data/people/cranmer.yml must contain project.
presentation #22 in _data/people/cranmer.yml must contain project.
presentation #23 in _data/people/cranmer.yml must contain project.
presentation #24 in _data/people/cranmer.yml must contain project.
presentation #25 in _data/people/cranmer.yml must contain project.
presentation #26 in _data/people/cranmer.yml must contain project.
presentation #27 in _data/people/cranmer.yml must contain project.
presentation #28 in _data/people/cranmer.yml must contain project.
presentation #29 in _data/people/cranmer.yml must contain project.
presentation #30 in _data/people/cranmer.yml must contain project.
presentation #31 in _data/people/cranmer.yml must contain project.
presentation #32 in _data/people/cranmer.yml must contain project.
presentation #33 in _data/people/cranmer.yml must contain project.
presentation #34 in _data/people/cranmer.yml must contain project.
presentation #35 in _data/people/cranmer.yml must contain project.
presentation #37 in _data/people/cranmer.yml must contain project.
presentation #38 in _data/people/cranmer.yml must contain project.
presentation #39 in _data/people/cranmer.yml must contain project.
presentation #40 in _data/people/cranmer.yml must contain project.
presentation #41 in _data/people/cranmer.yml must contain project.
presentation #42 in _data/people/cranmer.yml must contain project.
presentation #43 in _data/people/cranmer.yml must contain project.
presentation #44 in _data/people/cranmer.yml must contain project.
presentation #45 in _data/people/cranmer.yml must contain project.
presentation #46 in _data/people/cranmer.yml must contain project.
presentation #47 in _data/people/cranmer.yml must contain project.
presentation #48 in _data/people/cranmer.yml must contain project.
presentation #49 in _data/people/cranmer.yml must contain project.
presentation #50 in _data/people/cranmer.yml must contain project.
presentation #51 in _data/people/cranmer.yml must contain project.
presentation #52 in _data/people/cranmer.yml must contain project.
presentation #53 in _data/people/cranmer.yml must contain project.
presentation #54 in _data/people/cranmer.yml must contain project.
presentation #55 in _data/people/cranmer.yml must contain project.
presentation #56 in _data/people/cranmer.yml must contain project.
presentation #57 in _data/people/cranmer.yml must contain project.
presentation #58 in _data/people/cranmer.yml must contain project.
presentation #59 in _data/people/cranmer.yml must contain project.
presentation #60 in _data/people/cranmer.yml must contain project.
presentation #61 in _data/people/cranmer.yml must contain project.
presentation #0 in _data/people/savvy379.yml must contain meetingurl.
presentation #1 in _data/people/savvy379.yml must contain meetingurl.
presentation #2 in _data/people/savvy379.yml must contain meetingurl.
presentation #3 in _data/people/savvy379.yml must contain meetingurl, location.
presentation #4 in _data/people/savvy379.yml must contain meetingurl, location.
presentation #5 in _data/people/savvy379.yml must contain meetingurl, location.
presentation #6 in _data/people/savvy379.yml must contain meetingurl, location.
presentation #7 in _data/people/savvy379.yml must contain meetingurl, location.
presentation #8 in _data/people/savvy379.yml must contain location.
presentation #0 in _data/people/evanmassaro.yml must contain focus-area, project.
presentation #0 in _data/people/davidlange6.yml must contain location.
presentation #1 in _data/people/davidlange6.yml must contain location.
presentation #2 in _data/people/davidlange6.yml must contain location.
presentation #3 in _data/people/davidlange6.yml must contain meetingurl, location.
presentation #4 in _data/people/davidlange6.yml must contain location.
presentation #5 in _data/people/davidlange6.yml must contain location.
presentation #1 in _data/people/gordonwatts.yml must contain location.
presentation #3 in _data/people/gordonwatts.yml must contain project.
presentation #4 in _data/people/gordonwatts.yml must contain location.
presentation #5 in _data/people/gordonwatts.yml must contain location.
presentation #6 in _data/people/gordonwatts.yml must contain location.
presentation #7 in _data/people/gordonwatts.yml must contain location, project.
presentation #8 in _data/people/gordonwatts.yml must contain location.
presentation #9 in _data/people/gordonwatts.yml must contain location.
presentation #10 in _data/people/gordonwatts.yml must contain location.
presentation #11 in _data/people/gordonwatts.yml must contain location.
presentation #12 in _data/people/gordonwatts.yml must contain location.
presentation #13 in _data/people/gordonwatts.yml must contain location, project.
presentation #14 in _data/people/gordonwatts.yml must contain location.
presentation #15 in _data/people/gordonwatts.yml must contain location, project.
presentation #16 in _data/people/gordonwatts.yml must contain location.
presentation #17 in _data/people/gordonwatts.yml must contain location, project.
presentation #19 in _data/people/gordonwatts.yml must contain project.
presentation #28 in _data/people/gordonwatts.yml must contain project.
presentation #31 in _data/people/gordonwatts.yml must contain project.
presentation #0 in _data/people/bbockelm.yml must contain location.
presentation #1 in _data/people/bbockelm.yml must contain location.
presentation #2 in _data/people/bbockelm.yml must contain location, project.
presentation #3 in _data/people/bbockelm.yml must contain meetingurl, location.
presentation #4 in _data/people/bbockelm.yml must contain meetingurl, location, project.
presentation #5 in _data/people/bbockelm.yml must contain meetingurl, location, project.
presentation #6 in _data/people/bbockelm.yml must contain meetingurl, location, project.
presentation #8 in _data/people/bbockelm.yml must contain location, project.
presentation #10 in _data/people/bbockelm.yml must contain focus-area, project.
presentation #11 in _data/people/bbockelm.yml must contain location, project.
presentation #12 in _data/people/bbockelm.yml must contain location.
presentation #13 in _data/people/bbockelm.yml must contain location.
presentation #14 in _data/people/bbockelm.yml must contain location.
presentation #15 in _data/people/bbockelm.yml must contain location, project.
presentation #16 in _data/people/bbockelm.yml must contain location, project.
presentation #17 in _data/people/bbockelm.yml must contain location.
presentation #18 in _data/people/bbockelm.yml must contain location.
presentation #19 in _data/people/bbockelm.yml must contain location.
presentation #20 in _data/people/bbockelm.yml must contain location, project.
presentation #21 in _data/people/bbockelm.yml must contain location, project.
presentation #3 in _data/people/carlosmalt.yml must contain location.
presentation #18 in _data/people/carlosmalt.yml must contain location.
presentation #0 in _data/people/etorro.yml must contain location, project.
presentation #0 in _data/people/BenGalewsky.yml must contain project.
presentation #1 in _data/people/BenGalewsky.yml must contain project.
presentation #4 in _data/people/BenGalewsky.yml must contain project.
presentation #1 in _data/people/SebastianMacaluso.yml must contain project.
presentation #0 in _data/people/ivotron.yml must contain focus-area, project.
presentation #1 in _data/people/ivotron.yml must contain focus-area, project.
presentation #0 in _data/people/robrwg.yml must contain location, focus-area, project.
presentation #1 in _data/people/robrwg.yml must contain location.
presentation #2 in _data/people/robrwg.yml must contain location.
presentation #3 in _data/people/robrwg.yml must contain location.
presentation #4 in _data/people/robrwg.yml must contain location.
presentation #0 in _data/people/tresreid.yml must contain location.
presentation #0 in _data/people/msneubauer.yml must contain project.
presentation #1 in _data/people/msneubauer.yml must contain project.
presentation #2 in _data/people/msneubauer.yml must contain project.
presentation #3 in _data/people/msneubauer.yml must contain project.
presentation #4 in _data/people/msneubauer.yml must contain project.
presentation #5 in _data/people/msneubauer.yml must contain project.
presentation #6 in _data/people/msneubauer.yml must contain project.
presentation #8 in _data/people/msneubauer.yml must contain project.
presentation #9 in _data/people/msneubauer.yml must contain project.
presentation #10 in _data/people/msneubauer.yml must contain project.
presentation #11 in _data/people/msneubauer.yml must contain project.
presentation #0 in _data/people/heather-gray.yml must contain location.
presentation #1 in _data/people/heather-gray.yml must contain location.
presentation #2 in _data/people/heather-gray.yml must contain location.
presentation #3 in _data/people/heather-gray.yml must contain location.
presentation #4 in _data/people/heather-gray.yml must contain location.
presentation #5 in _data/people/heather-gray.yml must contain location.
presentation #6 in _data/people/heather-gray.yml must contain location.
presentation #0 in _data/people/slava77.yml must contain focus-area.
presentation #0 in _data/people/sfiligoi.yml must contain meetingurl.
presentation #7 in _data/people/sfiligoi.yml must contain location.
presentation #0 in _data/people/marianstahl.yml must contain location.
presentation #1 in _data/people/marianstahl.yml must contain location.
presentation #0 in _data/people/irinaene.yml must contain location.
presentation #26 in _data/people/henryiii.yml must contain meetingurl.
presentation #0 in _data/people/irinaespejo.yml must contain project.
presentation #1 in _data/people/irinaespejo.yml must contain focus-area, project.
presentation #2 in _data/people/irinaespejo.yml must contain focus-area, project.
presentation #3 in _data/people/irinaespejo.yml must contain focus-area, project.
presentation #0 in _data/people/xiaocong-ai.yml must contain location.
presentation #1 in _data/people/xiaocong-ai.yml must contain location.
presentation #2 in _data/people/xiaocong-ai.yml must contain location.
presentation #3 in _data/people/xiaocong-ai.yml must contain location.
presentation #4 in _data/people/xiaocong-ai.yml must contain location.
presentation #5 in _data/people/xiaocong-ai.yml must contain location.
presentation #6 in _data/people/xiaocong-ai.yml must contain location.
presentation #7 in _data/people/xiaocong-ai.yml must contain location.
presentation #8 in _data/people/xiaocong-ai.yml must contain location.
presentation #0 in _data/people/cvarni.yml must contain focus-area.
presentation #0 in _data/people/xweichu.yml must contain location, project.
presentation #1 in _data/people/xweichu.yml must contain location, project.
presentation #0 in _data/people/nickcinko.yml must contain location.
presentation #1 in _data/people/nickcinko.yml must contain location.
presentation #2 in _data/people/dcraik.yml must contain location.
presentation #4 in _data/people/dcraik.yml must contain location.
presentation #0 in _data/people/fkw888.yml must contain location, project.
presentation #1 in _data/people/fkw888.yml must contain location, project.
presentation #2 in _data/people/fkw888.yml must contain location, project.
presentation #3 in _data/people/fkw888.yml must contain location, project.
presentation #4 in _data/people/fkw888.yml must contain location, project.
presentation #5 in _data/people/fkw888.yml must contain location, project.
presentation #6 in _data/people/fkw888.yml must contain location, project.
presentation #7 in _data/people/fkw888.yml must contain location, project.
presentation #8 in _data/people/fkw888.yml must contain location, project.
presentation #9 in _data/people/fkw888.yml must contain location, project.
presentation #10 in _data/people/fkw888.yml must contain location.
presentation #11 in _data/people/fkw888.yml must contain location, project.
presentation #12 in _data/people/fkw888.yml must contain project.
presentation #14 in _data/people/fkw888.yml must contain location, project.
presentation #15 in _data/people/fkw888.yml must contain location, project.
presentation #16 in _data/people/fkw888.yml must contain location, project.
presentation #17 in _data/people/fkw888.yml must contain location, project.
presentation #18 in _data/people/fkw888.yml must contain location, project.
presentation #19 in _data/people/fkw888.yml must contain location, project.
presentation #20 in _data/people/fkw888.yml must contain location, project.
presentation #21 in _data/people/fkw888.yml must contain location.
presentation #22 in _data/people/fkw888.yml must contain focus-area, project.
presentation #23 in _data/people/fkw888.yml must contain project.
presentation #24 in _data/people/fkw888.yml must contain project.
presentation #25 in _data/people/fkw888.yml must contain location, project.
presentation #26 in _data/people/fkw888.yml must contain location, project.
presentation #27 in _data/people/fkw888.yml must contain location, project.
presentation #28 in _data/people/fkw888.yml must contain location.
presentation #29 in _data/people/fkw888.yml must contain location, project.
presentation #30 in _data/people/fkw888.yml must contain location, project.
presentation #31 in _data/people/fkw888.yml must contain location, project.
presentation #32 in _data/people/fkw888.yml must contain meetingurl, location, focus-area.
presentation #33 in _data/people/fkw888.yml must contain meetingurl, location.
presentation #34 in _data/people/fkw888.yml must contain meetingurl, location, project.
presentation #35 in _data/people/fkw888.yml must contain meetingurl, project.
presentation #36 in _data/people/fkw888.yml must contain location, project.
presentation #37 in _data/people/fkw888.yml must contain location, project.
presentation #38 in _data/people/fkw888.yml must contain project.
presentation #39 in _data/people/fkw888.yml must contain meetingurl, location.
presentation #40 in _data/people/fkw888.yml must contain project.
presentation #41 in _data/people/fkw888.yml must contain project.
presentation #42 in _data/people/fkw888.yml must contain meetingurl, location, project.
presentation #43 in _data/people/fkw888.yml must contain meetingurl, project.
presentation #44 in _data/people/fkw888.yml must contain project.
presentation #46 in _data/people/fkw888.yml must contain project.
presentation #48 in _data/people/fkw888.yml must contain location, project.
presentation #0 in _data/people/matkinso.yml must contain project.
presentation #1 in _data/people/matkinso.yml must contain project.
presentation #2 in _data/people/matkinso.yml must contain project.
presentation #3 in _data/people/matkinso.yml must contain project.
presentation #4 in _data/people/matkinso.yml must contain project.
presentation #5 in _data/people/matkinso.yml must contain project.
presentation #6 in _data/people/matkinso.yml must contain project.
presentation #7 in _data/people/matkinso.yml must contain project.
presentation #0 in _data/people/heikomuller.yml must contain project.
presentation #1 in _data/people/heikomuller.yml must contain project.
presentation #2 in _data/people/heikomuller.yml must contain project.
presentation #0 in _data/people/LincolnBryant.yml must contain location.
presentation #1 in _data/people/LincolnBryant.yml must contain location.
presentation #2 in _data/people/LincolnBryant.yml must contain location.
We could have table row spacing increase on narrow screens.
Right now the page content comes first, and then the team, which means the team may come quite late. Any options?
I've noticed that if you view the list of presentations filtered by person that the shortname
fields do not get resolved to name
fields as is done with by area, by institution, by date.
Example:
should get resolved to
but in the below screenshot it does not
hi @henryiii
could you also sort the presentations (eg, by area) by date (so the list of AS presentations would start with the latest one)? This requires an extra loop and a sort a la
https://github.com/iris-hep/iris-hep.github.io/blob/master/_includes/get_pres_list.html
does anyone know an easy way to add a search box for the website?
Currently the listing of fellows on the main IRIS-HEP page and the fellows page ( https://iris-hep.org/fellows.html ) seem to be sorted alphabetically by title . Can we change the order so they are listed by start date - "newest" fellows first?
The current IRIS-HEP logo with the words "iris hep" (the Iris-hep-4-no-long-name
series) is of decent quality for a small PNG when used on websites. However, when trying to use the image on other pages in a larger context the resolution isn't very good. Would it be possible to get a higher resolution image of it similar to the Iris-hep-5-just-graphic-large.png
that exists?
I created one myself from the SVG that exists in GIMP, but it is several MB in size where the Iris-hep-5-just-graphic-large.png
one is much smaller by comparison (~50 KB
), so I'm not doing this in a smart manner.
Please review the contents of the XCache project page here: https://iris-hep.org/projects/caching.html
Try to have the following
Please review the contents of the SkyHook DM project page here: https://iris-hep.org/projects/skyhookdm.html
Try to have the following
Add a docs page describing how to write a news post, with special features.
Its not possible to connect fellow projects to the iris-hep project that they were a part of.
(also the focus-area tag is often not filled in)
Please review the contents of the ServiceX project page here: https://iris-hep.org/projects/servicex.html
Try to have the following
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.