Skip to content

Eqcd26 website - #860

Merged
bastibock merged 6 commits into
mainfrom
eqcd26_website
Sep 7, 2026
Merged

bastibock merged 6 commits into
mainfrom
eqcd26_website

Conversation

@bastibock

Copy link
Copy Markdown
Contributor

Description

Adds a tab on the documentation to advertise the Eclipse Qrisp Community Day 2026

Related Issues

Closes #
Related to #

Type of Change

  • Feature (new functionality)
  • Change Request (modification of existing functionality)
  • Bug Fix
  • Refactoring (no behavior change)
  • Performance improvement
  • Documentation
  • CI / Build

Breaking Change?

  • Yes
  • No

What was changed?

  • Added a tab on the documentation to advertise the Eclipse Qrisp Community Day 2026
  • fixed two sphinx warnings while building website

How was it tested?

Built docs locally successfully

Test-ID Status
T-001 ✅ / ❌
T-002 ✅ / ❌
T-003 ✅ / ❌
T-004 ✅ / ❌

Screenshots / Output (if applicable)

two screenshots added

Checklist

  • My code follows the project's coding standards
  • I have performed a self-review
  • I have added/updated tests (referencing issue Test-IDs)
  • All tests pass locally and in CI
  • I have updated the documentation
  • I have added a changelog entry to changelog-dev.rst
  • Breaking changes are documented with migration path

Reviewer Notes

I'm not sure about the picture at the bottom.
Could also just delete it.
Bildschirmfoto 2026-09-04 um 12 08 38

@bastibock

bastibock commented Sep 4, 2026 •

Copy link
Copy Markdown
Contributor Author

Sorry, looks like I checked out from the wrong branch and by this added the files that were meant for the progress review branch.
I could delete them here and only add them for the branch they are meant to be in.
But we could also leave them in here, since they don't hurt. It's just a little messier.

EDIT: Nevermind, I cherry-picked the two correct commits for this branch and deleted the others from this branch only.

Should be clean and as intended now.

@@ -36,7 +36,7 @@ class PassManager:
``CircuitPass(my_func)``.

Example:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

If you want to fix the doc here: It should be "Examples"
Otherwise, it won't be displayed in the rendered doc.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Good Catch, thank you!

…ples in docstring

Co-authored-by: René Zander <150177509+renezander90@users.noreply.github.com>
@purva-thakre

purva-thakre commented Sep 4, 2026 •

Copy link
Copy Markdown
Contributor

Since we are not doing a new release of Qrisp, would adding this announcement lead to the documentation having new features that are still on the development version? Related to #818

@@ -0,0 +1,68 @@
.. _community_day:

@purva-thakre purva-thakre Sep 4, 2026 •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

the theme that we use to build the docs also allows us to add announcement banners on all pages of the docs. might be nice to add the banners.

https://pydata-sphinx-theme.readthedocs.io/en/stable/user_guide/announcements.html

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Great idea! Added a banner 😊

@renezander90

renezander90 commented Sep 4, 2026 •

Copy link
Copy Markdown
Contributor

Since we are not doing a new release of Qrisp, would adding this announcement lead to the documentation having new features that are still on the development version? Related to #818

We just had a minor version bump, hence the updated documentation would be consistent with the latest pypi version.
(And there might be another minor bump for the recent fixes for the QuantumFloat).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

By the time the release happens, the day has already passed, or? It doesn't matter though - we need to manually compile the changelog anyway..

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

That is most likely right. We can leave this out. I was mostly just following the process to not get a warning/error that I didn't update the changelog. 😄

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

If we are doing minor releases, we should also update the changelog-dev as needed. use the current file to create the changelog for 0.9.8 and then add a blank changelog file with the template for 0.10.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Yes, in the past be announced the whole stack of changes between two major releases only with the major releases. But, it would make sense to publish a changelog for the minor releases as well going forward. This should be easier now with the changelog-dev.

@purva-thakre

purva-thakre commented Sep 4, 2026 •

Copy link
Copy Markdown
Contributor

Since we are not doing a new release of Qrisp, would adding this announcement lead to the documentation having new features that are still on the development version? Related to #818

We just had a minor version bump, hence the updated documentation would be consistent with the latest pypi version. (And there might be another minor bump for the recent fixes for the QuantumFloat).

Thanks I did not know this, I had to check it on PyPI. BTW is there a reason why we do not update it on github if there is a minor release?
https://github.com/eclipse-qrisp/Qrisp/releases

@@ -0,0 +1,68 @@
.. _community_day:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

minor nit (feel free to ignore): move this document higher up in the toc i.e. before Tutorials.

Image

Comment on lines +65 to +68
.. image:: /_static/EQCD_2026_banner.png
:alt: Eclipse Qrisp Community Day 2026 — 29 October 2026, Fraunhofer FOKUS, Berlin. Organised by Eclipse Foundation and Fraunhofer FOKUS.
:align: center
:width: 100% No newline at end of file

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I agree the image should be at the top of the page.

html_theme_options = {
"announcement": (
"🌟 Join us for the "
'<a href="https://qrisp.eu/general/community_day.html">Eclipse Qrisp Community Day</a>'

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

this currently appears broken. I assume it will be fine after the docs are published?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Yes, exactly. This will be fine after being published.

@renezander90 renezander90 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🎊

@bastibock
bastibock merged commit ac2bdb6 into main Sep 7, 2026
11 checks passed
@bastibock
bastibock deleted the eqcd26_website branch September 7, 2026 09:25
moar55 pushed a commit to moar55/Qrisp that referenced this pull request Oct 7, 2026
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.

4 participants