Release new frontend changes with Spanish chapters 0 & 1#67
Merged
Conversation
Tweak README
Add Gradio Chapter
Update translation template to include sections
Fix Spanish section 1 with new frontend
Add build step for Spanish content
Co-authored-by: lewtun <[email protected]>
Add quality test to main branch
Chapter 1 translated to spanish
lewtun
changed the title
|
The documentation is not available anymore as the PR was closed or merged. |
Member
Author
|
English and Spanish builds look good 🔥
|
GITbaburin
pushed a commit
to GITbaburin/course
that referenced
this pull request
May 17, 2026
Release new frontend changes with Spanish chapters 0 & 1
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds all the changes on the
mainbranch torelease. This includes:@Pierrci just to double check: if I merge this, I expect that
doc-builderwill build the content and push it to thedoc-buildrepo here. Do I need to do anything else or will this automatically render on https://huggingface.co/course ?