Create Automated Event Creation Tutorial

[gokceuludogan]

This PR adds the first draft of a step-by-step tutorial for creating event content using github issue automation. The guide includes screenshots for each stage of the flow.

Files

• content/tutorials/automated_events.md
• Images under content/_static/tutorials/issue-automation/

Open questions & proposal

Separate tutorials for Events vs News?

I'd suggest having different pages, as:

• Fields and validation differ (e.g., required image for news).
• Keeps each page short, scannable.

Tutorials structure

Which tutorial categories will we host beyond website content, and how should we organize them? Should we keep separate subfolders for each category?
For the current tutorial, an example path could be tutorials/website/automated-content/.

Notes on screenshots & examples

Current screenshots use example data. Once new content is uploaded, we might replace them with real screenshots.

[doganulus]

This needs to mention (+) buttons on the main page.

[doganulus]

We may simplify this feature and tutorial more.

• Add a title seems unnecessary. Event title can be the title.
• Bilingual emphasis is unnecessary.
• The tutorial is too technical. The user doesn't care about markdown or pipeline behind. It must be rewritten from that perspective.

[gokceuludogan]

I believe this task is beginner-friendly. Could we assign it to our new undergraduate interns involved in the new program?