Skip to content

Feature/issue 30 gradio UI#159

Open
nicooxxx wants to merge 5 commits into
climateandtech:mainfrom
nicooxxx:feature/issue-30-gradio-ui
Open

Feature/issue 30 gradio UI#159
nicooxxx wants to merge 5 commits into
climateandtech:mainfrom
nicooxxx:feature/issue-30-gradio-ui

Conversation

@nicooxxx

@nicooxxx nicooxxx commented Jul 2, 2026

Copy link
Copy Markdown
Collaborator

Gradio UI for the FactChecker is implemented in this PR.

The current UI is documented in the README.

The UI uses custom CSS for component styling and a centralized theme with global variables (e.g. colors, fonts, and spacing) to ensure a consistent design and make future customization easier.

This PR focuses on the UI structure and styling only. The underlying functionality is not implemented yet and will be added in follow-up PRs.

@suung

suung commented Jul 2, 2026

Copy link
Copy Markdown
Collaborator

@nicooxxx great, thank you. Could you maybe add screenshots showcasing the UI a bit here in the PR? Then people can review the design without running the code

Comment thread .gradio/certificate.pem
@@ -0,0 +1,31 @@
-----BEGIN CERTIFICATE-----

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@nicooxxx should this be here?
If yes, what is it for?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Its the self signed certificate which Gradio creates when run locally.
And shouldn't be there, so i will remove it

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

I removed the sensitive data from the current state of the branch, so the latest commit no longer contains the sensitive file.
I was planning to remove it from the earlier commit history as well, but my experience with more advanced Git operations such as rewriting history is still limited. I didn't want to make changes that could accidentally affect the branch or the repository without checking with you first.

Comment thread factchecker/app/app.py
css += f.read() + "\n"

# Just testfunction acts as dummy
def claim(claim, scientific_source):

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@nicooxxx This is a test function to test the data, how can we integrate the real fact checking flow?

Here is from the old #37 branch the entrypoint to gradio https://github.com/climateandtech/factchecker/pull/37/changes#r3512893784

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

The current code is mainly a UI showcase. This function is only a dummy/test function so I could see how the UI behaves and adjust the layout.

The next step would be to replace the dummy function with the real fact-checking flow from the old #37 branch and connect the Gradio submit handler to the actual FactChecker entrypoint.

@nicooxxx

nicooxxx commented Jul 2, 2026

Copy link
Copy Markdown
Collaborator Author

@nicooxxx great, thank you. Could you maybe add screenshots showcasing the UI a bit here in the PR? Then people can review the design without running the code

@suung there are screenshots in the README

@suung

suung commented Jul 2, 2026

Copy link
Copy Markdown
Collaborator

@nicooxxx great, thank you. Could you maybe add screenshots showcasing the UI a bit here in the PR? Then people can review the design without running the code

@suung there are screenshots in the README

@nicooxxx thanks, I found them.. It looks visually very cool. I think we should align which of the features from the #30 branch we port here

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.

2 participants