-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a template/pattern for a sustainability page for WordCamp sites #46
Comments
Also drupalcon 2023 and its travel page |
Hallo @LittleBigThing, I hope this could be helpful to create a template :) I collected some ideas here. 1. Introduction
2. General Tips for Attendees
3. Sustainable Practices by Organizers
4. Local Sustainability Initiatives
5. General Section
6. Specific Section for Each WordCamp
7. Translation and Accessibility
|
I love this example, @ramonfincken. Thank you so much for sharing. I think that sustainability page makes a great job summarizing first what the Organizing team has done to make the event more sustainable and then invites the attendee to add their help on top of that. I think it is the perfect example to use it as a reference and work with WCEU25 Organizing team to create a version that makes a good template and even work with them on the final version for their site. |
Thank you @CeliGaroe ! But .. it gets even better -> https://wordpress.slack.com/files/U2PLRUPDF/F07CE8W14GN/screencapture-kuonicongress-eventsair-drupalcon-barcelona-2024-registration-link-site-register-2024-07-16-10_59_24.png the link should open in your make WordPress slack |
@ramonfincken I love the DrupalCon form, even if we could just implement the "how are you getting to WordCamp?" part it'd be a big step forward. |
Thanks @BenjaminZekavica for the nice summary. Combining that with the examples from the Drupal community, I'd propose/prefer a basic 2-part structure:
For 1, there could be a general part that is almost copy/paste-able for every event, complemented by the more unique (or upcoming) actions, specific for that event. Point 2 could be based on our events handbook’s tips for attendees page, presented in a more visual way (see Drupal examples again). Since the travel page is often quite long, it should be a separate page, linked from the tips for attendees (and vica versa). |
What should we do first? Create a layout in a Google Doc as a reference or talk with WCEU 2025 organizers to know their feedback before hand? I vote for creating a proposal first (just organized ideas). |
I've created a very basic pattern based on the Handbook and the previous comments and attached it to this comment. |
Hi @mardelnet! Thank you very much for your help, but I think you didn't got the idea of this issue right (or we didn't explain it correctly). Either way, the purpose of this template is to include the efforts made by the WCEU organizers to make the WordCamp more sustainable. It shouldn't include our 'sustainable events Handbook' recommendations, but the efforts of the organization and the request of colaboration to attendees, something similar to this example. On the other hand, I think it would be better to organize first the information in a collaborative document and then talk to the WCEU 2025 organization so we can fit the template better to their efforts, their needs, and the WordPress Theme and Styles they are using here. Let me know if something is not clear. Thanks! |
Thank you, @CeliGaroe! It's much clearer now. Please let me know how to proceed, and count on me for anything else. |
I'd like to propose to create a page/template for WordCamp websites about sustainability. This could contain information about
I see a couple of advantages:
We might create a pattern out of it that can be re-used and perhaps be published in the pattern library as well (although not sure about updates there).
We've been seeing other open source projects investing to surface sustainability, especially when organising events. We should definitely follow up on this (in my opinion).
The text was updated successfully, but these errors were encountered: