add VR blog post#73
Conversation
|
Hi @j-atkins could you have a look if this worked out? |
for more information, see https://pre-commit.ci
j-atkins
left a comment
There was a problem hiding this comment.
Blog post looks good, thanks for adding!! I've added a suggestion below for the phrasing. Also note I added a commit which corrects the date to 2026 (it was 2025) so that the posts appear in order.
P.S. this branch was behind the main branch (following Erik's updates to the website) so I have updated it to now be adding your commits ahead of main. A good reminder to always make sure you sync with main before branching off and add new bits 😉
|
Hi Jamie,
Great. Suggestion more than welcomed.
What else do I have to do so the blogpost appears online in the website?
All noted regarding main :) — it is a steep learning curve, this branching business. But I am enjoying getting to know this world a lot.
Best,
Gonçalo
From: Jamie Atkins ***@***.***>
Date: Friday, 22 May 2026 at 16:29
To: Parcels-code/virtualship.parcels-code.org ***@***.***>
Cc: Borges Simoes de Albergaria Dias, G. (Goncalo) ***@***.***>; Author ***@***.***>
Subject: Re: [Parcels-code/virtualship.parcels-code.org] add VR blog post (PR #73)
CAUTION: This email originated from outside of Utrecht University. Do not click links or open attachments unless you recognize the sender and know the content is safe.
@j-atkins commented on this pull request.
Blog post looks good, thanks for adding!! I've added a suggestion below for the phrasing. Also note I added a commit which corrects the date to 2026 (it was 2025) so that the posts appear in order.
P.S. this branch was behind the main branch (following Erik's updates to the website) so I have updated it to now be adding your commits ahead of main. A good reminder to always make sure you sync with main before branching off and add new bits 😉
________________________________
In src/posts/VRheadsetNIOZ/index.md<#73 (comment)>:
@@ -0,0 +1,16 @@
+---
+title: 'VR headset for NIOZ’s library'
+date: '2026-05-22'
+authors:
+ - name: Gonçalo Albergaria
+ github: GoncaloAlbergaria
+summary: 'VirtualShip delivers a VR heaset to NIOZ'
+---
+
+Yesterday, 21 May 2026, our team travelled from Utrecht to deliver to NIOZ Texel a Meta Quest S3 headset containing the VR/360° educational videos developed within VirtualShip.
+After meeting with several departments, Emma Daniels, post doc, and Gonçalo Albergaria, research officer, wrapped up the outing on a celebratory note, meeting Daan van Loon, a staunch defender of Open Science and the institute’s librarian, to bestow the library with a VR headset and VirtualShip explanatory booklet.
This would be clearer in my opinion
⬇️ Suggested change
…-After meeting with several departments, Emma Daniels, post doc, and Gonçalo Albergaria, research officer, wrapped up the outing on a celebratory note, meeting Daan van Loon, a staunch defender of Open Science and the institute’s librarian, to bestow the library with a VR headset and VirtualShip explanatory booklet.
+After meeting with several departments, Emma Daniels (Postdoc) and Gonçalo Albergaria (Research Officer) wrapped up the outing on a celebratory note, meeting Daan van Loon, a staunch defender of Open Science and the institute’s librarian, to bestow the library with a VR headset and VirtualShip explanatory booklet.
—
Reply to this email directly, view it on GitHub<#73 (review)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/B7GDYWICTV6NZTQ6QLQEBDL44BP3LAVCNFSM6AAAAACZJIUNF6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHM2DGNBWGI3DINZQHA>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.
|
|
Hi @GoncaloAlbergaria, I've added the suggested change as a commit (which you'll see in the thread in this pull request/PR). As the PR owner you would usually incorporate these yourself but I just did it now because it was a quick one. Now that someone (in this case me) has approved the PR; if you're ready to go (and all the checks are successful, i.e. green ticks) you can press "Merge pull request". This will then merge your branch to main and the site will automatically deploy from there 🙂 |
No description provided.