Skip to content

Adding events#100

Merged
lwjohnst86 merged 28 commits into
mainfrom
adding-events
Jun 8, 2026
Merged

Adding events#100
lwjohnst86 merged 28 commits into
mainfrom
adding-events

Conversation

@CHRTJO1112

@CHRTJO1112 CHRTJO1112 commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

Description

I've added the events page to the main website after Daniel's request.

I have not added the images folder from the events repository, as none of the current images were in use.

This PR needs a quick review.

@lwjohnst86

Copy link
Copy Markdown
Member

@CHRTJO1112 @danielwitte I'm confused. We have the events website already at https://github.com/dp-next/events. Did you mean, make a link to that events page from this website?

@CHRTJO1112

Copy link
Copy Markdown
Contributor Author

Hi @lwjohnst86, in this pull request we have moved the events content to the main website so it appears as an option in the navbar, rather than existing as a separate website. Daniel's idea was to gather all relevant information in one place to avoid having it fragmented across multiple websites.

@lwjohnst86

Copy link
Copy Markdown
Member

If we put a link to the events page on the navbar without moving the content over, we can prevent fragmenting things. There was a reason we made the events page separately since we wanted the landing page to be for others, while the events page was for us. Or has that reason changed? @danielwitte

@danielwitte

Copy link
Copy Markdown
Contributor

Now that the participant-focused info has been moved to a separate page, I think we can think of the main DP-Next page as focused both (partly) on interested external viewers and (mostly ) on us. Items such as our outputs, the newsletters and events should be easily and seamlessly accessible from the main DP-Next page through the top level menus. On those respective pages, the style should be consistent and it should be as easy to navigate back. I don't mind if they are managed as separate pages/repos or not, as long as the navigation flow is seamless both out and back.

@lwjohnst86 lwjohnst86 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since it is mostly a move over, I just added comments on what files need to be kept/deleted.

Comment thread events/_quarto.yml Outdated
Comment thread events/copier-answers.yml Outdated
Comment thread events/custom-styles.scss Outdated
Comment thread events/download Outdated
Comment thread events/events.Rproj Outdated
Comment thread events/LICENSE.md Outdated
Comment thread events/README.md Outdated
@CHRTJO1112

Copy link
Copy Markdown
Contributor Author

@lwjohnst86
Thanks for the cleanup!

@lwjohnst86 lwjohnst86 merged commit 1ea0edb into main Jun 8, 2026
1 check passed
@lwjohnst86 lwjohnst86 deleted the adding-events branch June 8, 2026 20:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants