Update documentation branding: change copyright, links, and config se…

[Anaa1101]

This PR addresses issue #514 by making the following changes:
Completed:

• Changed "Twitter" to "X" in index.html with correct link
• Updated copyright notice to "2025 Apache 2.0 License by contributors" and reduced font size
• Updated project name in conf.py from 'pretix' to 'eventyay'
• Set logo_only to False (eventyay uses text-based branding like the website)
• All links verified (blog, GitHub, issue reporting)

Questions for maintainers:

• The first task was marked DONE but I found many remaining "pretix" references in config.rst and other technical documentation files. Should these be changed? Many appear to be code paths/technical references.
• I could not locate eventyay logo or favicon files. The website uses text-based branding. Should I add logo/favicon files, or leave it as text-based?

Summary by Sourcery

Update documentation and configuration to reflect eventyay branding, replacing pretix references, adjusting social media links and legal notices

Enhancements:

• Rebrand project name in conf.py and templates from pretix to eventyay
• Set logo_only to False for text-based branding in documentation
• Update social media label and link from Twitter to X
• Reduce footer font size and update copyright to 2025 Apache 2.0 License by contributors

Documentation:

• Verify and correct all external links in documentation templates

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR rebrands the documentation by updating project metadata in the Sphinx config, revising landing page links and text to reflect the switch from Twitter to X, and adjusting footer styling for consistent branding.

Class diagram for updated Sphinx documentation config

classDiagram
    class conf_py {
        - project: str
        - copyright: str
        + master_doc: str
    }
    conf_py : project = "eventyay"
    conf_py : copyright = "2025 Apache 2.0 License by contributors"

Loading

File-Level Changes

Change	Details	Files
Rebrand project metadata in Sphinx config	Set project identifier to 'eventyay' Replace copyright notice with '2025 Apache 2.0 License by contributors'	doc/conf.py
Update documentation landing page links and text	Correct descriptive text typo Rename social link from 'Twitter' to 'X' and adjust link URL Update link description to reference 'X'	doc/_templates/index.html
Adjust footer styling	Reduce copyright text font size via inline styling	doc/_themes/pretix_theme/footer.html

Possibly linked issues

• Adjust design of documentation #514: PR updates documentation branding by changing project name from 'pretix' to 'eventyay', updating copyright, and verifying links.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey there - I've reviewed your changes - here's some feedback:

• Fix the typo in index.html (“gateway tso” → “gateway to”).
• Run a global search for “pretix” and update any remaining references in docs and theme directory names.
• Consider renaming the “_themes/pretix_theme” folder (or adding an Eventyay logo/favicon) to fully reflect the new branding.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Fix the typo in index.html (“gateway tso” → “gateway to”).
- Run a global search for “pretix” and update any remaining references in docs and theme directory names.
- Consider renaming the “_themes/pretix_theme” folder (or adding an Eventyay logo/favicon) to fully reflect the new branding.

## Individual Comments

### Comment 1
<location> `doc/_templates/index.html:112` </location>
<code_context>
                 <strong>Project website</strong>
             </a>
-            <p>eventyay.com is your gateway to the eventyay project, offering premier commercial hosting services all in one place.</p>
+            <p>eventyay.com is your gateway tso the eventyay project, offering premier commercial hosting services all in one place.</p>
         </div>
     </div>
</code_context>

<issue_to_address>
**issue (typo):** Typo in 'tso' should be 'to'.

```suggestion
            <p>eventyay.com is your gateway to the eventyay project, offering premier commercial hosting services all in one place.</p>
```
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

issue (typo): Typo in 'tso' should be 'to'.

Suggested change

	<p>eventyay.com is your gateway tso the eventyay project, offering premier commercial hosting services all in one place.</p>
	<p>eventyay.com is your gateway to the eventyay project, offering premier commercial hosting services all in one place.</p>

[mariobehling]

Hi, thanks for working on the project. The next version of the system is being developed in the "enext" branch. All PRs should be made against this branch. Thanks!

[Anaa1101]

I've changed the base branch to enext as requested, but there are now merge conflicts showing in multiple files. Since my PR only modified documentation files (index.html, conf.py, and copyright notices), I'm not sure how to proceed with these conflicts. Could you advise on the best way to resolve this? Thanks!

[Saksham-Sirohi]

hi @Anaa1101 you can copy the files you have made changes to to a new place and then use git fetch origin and then use git reset --hard origin/enext on the branch this will reset your branch to enext thereafter, you can choose to cherry-pick(this may or may not work properly) or commit your changes after making commits on the right branch a force push shall do the trick.

Also, please move that style change to the stylesheet file. If you need the guide on how to set up the enext branch, you will find the setup guide here: https://github.com/fossasia/eventyay-tickets/tree/enext

[Saksham-Sirohi]

This change should go inside pretix.css; it should be inside static/css within the same directory.