-
-
Notifications
You must be signed in to change notification settings - Fork 88
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
Integrating Nuclia Widget #792
base: nuclia
Are you sure you want to change the base?
Conversation
This reverts commit b4533ea.
Removed run on requirements-initial.txt
…o nuclia_widget
…o nuclia_widget
…o nuclia_widget
…o nuclia_widget
Here's that git command from Volto that builds only when docs change: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
First round of review, mostly just formatting and style.
I have not yet commented on design of the Nuclia widget, as I was waiting for some dust to settle. Better late than never. In general it would be good to reproduce as close as practical the existing search results listing, as @ksuess put significant thought and effort into its style and usability: https://training.plone.org/search.html?q=schema
If there are other things that you see, let's chat first. These are the obvious things that caught my eye. I really like the infinite scroll loading of results as needed, and "chat with your docs" feature. |
I made some changes locally and here is how the results look now: ==================================================================================
Issues:
I am still working to find a better logic for the above two issues to work out. Additional:
Do we want any of these? |
|
❌ Deploy Preview for plone-training failed. Why did it fail? →
|
git config --global user.email [email protected] | ||
git add . | ||
git commit -m "Nuclia Sync: Updated docs" --allow-empty | ||
git push |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So everytime there is a commit on main, we run the job, which makes a commit on main.
It looks like an infinite loop :)
Maybe the job should have a condition like if the last changes are only about our 2 generated json files, we stop.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ebrehault I have put the check for nuclia_sync.json
only. This should work, right?
Final items to work on:
|
CC: @stevepiercy
Here is a draft for Nuclia widget integration into training.
Some of the issues to be solved: