[BCN-2026] Add event #15384

edupr91 · 2025-08-03T07:36:10Z

Adding a new event in Barcelona for 2026

Changes in this PR:

BCN-2026: Add welcome, contact and conduct pages
BCN-2026: Add assets and initial logo.

netlify · 2025-08-03T07:36:15Z

✅ Deploy Preview for devopsdays-web ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	`80d8767`
🔍 Latest deploy log	https://app.netlify.com/projects/devopsdays-web/deploys/6894249ef7e787000842d6ed
😎 Deploy Preview	https://deploy-preview-15384--devopsdays-web.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

nimbinatus · 2025-08-04T13:35:02Z

Hi there! I'm noticing some file updates missing from this PR. Did you use the new event script? More information here: https://github.com/devopsdays/devopsdays-web/tree/main/utilities#events

We really recommend using that script to set up a new event as it ensures that all of the files you need to update and set up are present, and you don't need to keep up to date on changes we've made to the build system.

GitHub
devopsdays-web/utilities at main · devopsdays/devopsdays-web
This is the website for devopsdays. Contribute to devopsdays/devopsdays-web development by creating an account on GitHub.

toshywoshy

I do not see a change to the redirect, I suggest you do add this static/_redirects
/barcelona/* /events/2013-barcelona/:splat 302
Would need to change to
/barcelona/* /events/2026-barcelona/:splat 302

toshywoshy · 2025-08-04T13:31:20Z

content/events/2026-barcelona/welcome.md

+            </p>
+        </td>
+        <td width="40%" valign="top" align="center">
+            <img alt="DevOpsDays Barcelona 2026" src="/events/2026-barcelona/logo.png" width="300" height="450" border="0">


Please use {{< event_logo >}} this allows you to remove the static image file

done ✔️

data/events/2026/barcelona/main.yml

toshywoshy · 2025-08-04T13:32:29Z

static/events/2026-barcelona/logo.png

This file is not required anymore, please remove it

File has been deleted

nimbinatus · 2025-08-04T13:36:49Z

data/events/2026/barcelona/main.yml

+#   variable: 2019-01-05T23:59:59+02:00
+# Note: we allow 2026-MM-DD for backward compatibility, but it can lead to unexpected behaviors (like your event disappearing from the front page during your last day)
+
+startdate: ""


Just a note: Since these dates aren't populated, you won't see your logo on the main page. Don't panic! You can find your event listed in the left sidebar under "TBD". Once you have a date here, your logo will appear with the others on the main page :)

yep. i noticed that while changing the main file 😃
Thanks for the note 👌

nimbinatus · 2025-08-04T13:38:57Z

static/events/2026-barcelona/logo.png

You won't need this one moving forward as the build now pulls from the assets/events/2026-barcelona/logo.png instead :)

If you want to use the logo in your welcome page and it's not loading without this file, use the shortcode {{< event_logo >}} instead of trying to use HTML (more info in the theme docs).

done ✔️

nimbinatus · 2025-08-04T13:39:54Z

Ha, sorry for the double review! @toshywoshy and I must be reviewing at the same time :)

edupr91 · 2025-08-04T13:55:11Z

eughh yeah I did not see the utilities folder ^^'
Between today and tomorrow morning, I will review the changes.

Sorry for the trouble :-)

toshywoshy

Please change the CITY and YYYY to your city name and year

toshywoshy · 2025-08-05T09:32:28Z

content/events/2026-barcelona/yyyy-city/welcome.md

@@ -0,0 +1,87 @@
+++
+Title = "devopsdays CITY YYYY"


Please change this, to use your city and year

Done ✔️

toshywoshy · 2025-08-05T09:32:51Z

content/events/2026-barcelona/yyyy-city/welcome.md

+++
+Title = "devopsdays CITY YYYY"
+Type = "welcome"
+aliases = ["/events/yyyy-city/"]


Again here year-city, so the slug gets created properly

Done ✔️

toshywoshy · 2025-08-05T09:33:28Z

content/events/2026-barcelona/yyyy-city/welcome.md

+Title = "devopsdays CITY YYYY"
+Type = "welcome"
+aliases = ["/events/yyyy-city/"]
+Description = "devopsdays CITY YYYY"


Here again add your city and year

Done ✔️

toshywoshy · 2025-08-05T09:33:59Z

content/events/2026-barcelona/yyyy-city/contact.md

+++
+Title = "Contact"
+Type = "event"
+Description = "Contact information for devopsdays CITY YYYY"


Again here chnge the city and the year

toshywoshy · 2025-08-05T09:34:03Z

content/events/2026-barcelona/yyyy-city/location.md

+++
+Title = "Location"
+Type = "event"
+Description = "Location for devopsdays CITY YYYY"


Again here chnge the city and the year

Done ✔️

toshywoshy · 2025-08-05T09:34:09Z

content/events/2026-barcelona/yyyy-city/propose.md

+++
+Title = "Propose"
+Type = "event"
+Description = "Propose a talk for devopsdays CITY YYYY"


Again here chnge the city and the year

Done ✔️

toshywoshy · 2025-08-05T09:34:46Z

content/events/2026-barcelona/yyyy-city/registration.md

+++
+Title = "Registration"
+Type = "event"
+Description = "Registration for devopsdays CITY YYYY"


However this file is not used at present, to avoid to remember it later, please change the city and the year

Done ✔️

edupr91 · 2025-08-07T04:04:36Z

Thanks for the notes. I understood the files under yyyy-city as templates for pages, but yeah, now I see the point of updating the files to avoid future trouble.
Thanks again 😃

phrawzty · 2025-08-13T10:16:21Z

Hello @edupr91 @nimbinatus and @toshywoshy.

What's up with the /yyyy-city/ subdirectory? It's not at all standard.

@edupr91 Did you use the create_new_event.sh script when creating this event? If not, why not? If yes, why did you change the output afterwards?

Can somebody please explain using clear and exact language what the purpose of this organisational structure us? What is the goal of this structure? What problem does it solve? Why is this event being implemented differently than literally every other event?

Thank you.

toshywoshy · 2025-08-13T10:36:49Z

Well, my point was that the slug entry in the file on that line needs to be changed, not the directory.
Hugo will build the markdown files, the front matter currenty has yyyy-city in place of 2025-barcelona, so Hugo will build this with the current generic alias in place of the correct year-city alias as we want.
I see that @edupr91 move these files in place of changing the entry on those lines I indicated to be correct.

edupr91 · 2025-08-18T20:01:24Z

Hello @phrawzty,

Thank you for your questions. I've reviewed my steps and can now provide clarity on the recent changes.

Addressing the Questions

Did you use the create_new_event.sh script? No, I did not.
Why not? When I began my work, I used the instructions in the CONTRIBUTING.md file. I wasn't aware of the utility scripts until @nimbinatus and @toshywoshy pointed them out.
What's up with the /yyyy-city/ subdirectory, and why did you change the output? After discovering the script, I used it to comply with the standard format. However, when I ran the script for an event that already had a directory, it created a new subdirectory named /yyyy-city/ within it. I didn't initially recognise this as an issue and proceeded with the changes, which is what led to the non-standard output.

I apologise for the misunderstanding on my part.

Moving Forward

To resolve this, I propose closing this pull request and creating a new one from scratch, using only the create_new_event.sh script. This will ensure all changes are clean and follow the expected standards.

Additionally, I would like to suggest two improvements to prevent this from happening in the future:

Add a line about the utility scripts to the CONTRIBUTING.md file to make them more discoverable for new contributors.
Add a check to the create_new_event.sh script to validate whether an event's folder already exists. If it does, the script should exit with a clear error message instead of creating a new subdirectory.

Please let me know if these changes sound good. I can create the related issues if you agree.

FloorD · 2025-08-22T13:23:48Z

Hello @phrawzty,

Thank you for your questions. I've reviewed my steps and can now provide clarity on the recent changes.

Addressing the Questions

Did you use the create_new_event.sh script? No, I did not.

Why not? When I began my work, I used the instructions in the CONTRIBUTING.md file. I wasn't aware of the utility scripts until @nimbinatus and @toshywoshy pointed them out.

What's up with the /yyyy-city/ subdirectory, and why did you change the output? After discovering the script, I used it to comply with the standard format. However, when I ran the script for an event that already had a directory, it created a new subdirectory named /yyyy-city/ within it. I didn't initially recognise this as an issue and proceeded with the changes, which is what led to the non-standard output.

I apologise for the misunderstanding on my part.

Moving Forward

To resolve this, I propose closing this pull request and creating a new one from scratch, using only the create_new_event.sh script. This will ensure all changes are clean and follow the expected standards.

Additionally, I would like to suggest two improvements to prevent this from happening in the future:

Add a line about the utility scripts to the CONTRIBUTING.md file to make them more discoverable for new contributors.

Add a check to the create_new_event.sh script to validate whether an event's folder already exists. If it does, the script should exit with a clear error message instead of creating a new subdirectory.

Please let me know if these changes sound good. I can create the related issues if you agree.

@toshywoshy wdyt about David's proposal? I've updated the member list for barcelona@

edupr91 · 2025-08-25T18:54:55Z

New PR created. #15442

toshywoshy · 2025-09-03T16:45:08Z

Sorry, did not see the updates here
Yes, we need better scripts or other ways to create a new event, updating and maintaining event details.
These scripts should validate things already so it makes it easier for reviewers to approve.
As for suggestion to add this to the CONTRIBUTING.md, I think we haven't done so as we never really got enough feedback if the scripts work for more then "It runs on my laptop", so we need more people using and providing feedback

nimbinatus · 2025-09-03T19:53:46Z

I've merged the other PR, and I've opened a new issue at #15457. Let's move the general conversation about the utilities script there. Sorry for all of the confusion, folks!

David Castañeda added 5 commits July 31, 2025 05:15

BCN initial commit

fa6b83f

Add logo as asset to be used in the welcome page

6f4b584

Update Ana's info in contact page

8485092

Fix logo height

382bfa9

David andd Almudena bio upgrades

e4eda0e

edupr91 requested a review from a team as a code owner August 3, 2025 07:36

toshywoshy requested changes Aug 4, 2025

View reviewed changes

nimbinatus reviewed Aug 4, 2025

View reviewed changes

David Castañeda and others added 3 commits August 5, 2025 06:43

add_new_event script minor changes

1ee8cbd

Merge branch 'main' into main

e716ca2

disable location page - for now

a9cfd81

toshywoshy requested changes Aug 5, 2025

View reviewed changes

Update templates

80d8767

phrawzty added question do-not-merge labels Aug 13, 2025

edupr91 mentioned this pull request Aug 25, 2025

[BCN-2026] Init Barcelona 2026 #15442

Merged

nimbinatus mentioned this pull request Aug 29, 2025

Update to make utility script easier #15457

Closed

nimbinatus closed this Sep 3, 2025

[BCN-2026] Add event #15384

[BCN-2026] Add event #15384

Uh oh!

Conversation

edupr91 commented Aug 3, 2025

Changes in this PR:

Uh oh!

netlify bot commented Aug 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for devopsdays-web ready!

Uh oh!

nimbinatus commented Aug 4, 2025 • edited by unfurl-links bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

toshywoshy left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

nimbinatus commented Aug 4, 2025

Uh oh!

edupr91 commented Aug 4, 2025

Uh oh!

toshywoshy left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

edupr91 commented Aug 7, 2025

Uh oh!

phrawzty commented Aug 13, 2025

Uh oh!

toshywoshy commented Aug 13, 2025

Uh oh!

edupr91 commented Aug 18, 2025

Uh oh!

FloorD commented Aug 22, 2025

Uh oh!

edupr91 commented Aug 25, 2025

Uh oh!

toshywoshy commented Sep 3, 2025

netlify bot commented Aug 3, 2025 •

edited

Loading

nimbinatus commented Aug 4, 2025 •

edited by unfurl-links bot

Loading