Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions extralit/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,16 @@ These are the section headers that we use:
- Added `wait` parameter to the `extralit workflows start` CLI to waiting for the workflow to complete and return the final status.
- Added dynamic mimetypes support for document uploads based on file extension or UploadFile types.

### Changed
- **Documentation**: Completed rebranding from Argilla to Extralit across all documentation files
- Updated 18 documentation files with Extralit branding
- Renamed 3 files: `how-to-configure-argilla-on-huggingface.md` → `how-to-configure-extralit-on-huggingface.md`, `how-to-deploy-argilla-with-docker.md` → `how-to-deploy-extralit-with-docker.md`, `repo-visualizer-argilla.svg` → `repo-visualizer-extralit.svg`
- Updated all tutorial notebooks to reference `docs.extralit.ai` instead of `docs.argilla.io`
- Updated HuggingFace Space URLs from `argilla/*` to `extralit/*`
- Updated example code assets from `argilla.io` to `extralit.ai`
- Updated function references from `get_argilla_themed_panel` to `get_extralit_themed_panel`
- Preserved appropriate attribution to Argilla as the foundation project

### Fixed
- Fixed single document uploads via CLI (`extralit documents add`) to start PDF workflow.

Expand Down
4 changes: 2 additions & 2 deletions extralit/docs/admin_guide/custom_fields.md
Original file line number Diff line number Diff line change
Expand Up @@ -87,8 +87,8 @@ dataset.records.log([
ex.Record(
fields={
"image": {
"original": "https://argilla.io/brand-assets/argilla/argilla-logo-color-black.png",
"revision": "https://argilla.io/brand-assets/argilla/argilla-logo-black.png",
"original": "https://extralit.ai/brand-assets/extralit/extralit-logo-color-black.png",
"revision": "https://extralit.ai/brand-assets/extralit/extralit-logo-black.png",
}
}
)]
Expand Down
6 changes: 3 additions & 3 deletions extralit/docs/admin_guide/migrate_from_legacy_datasets.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,9 +46,9 @@ Extralit v2 introduces several important changes to the API that affect how you

To follow this guide, you will need to have the following prerequisites:

- An argilla 1.* server instance running with legacy datasets.
- An argilla >=1.29 server instance running. If you don't have one, you can create one by following this [Extralit guide](../getting_started/quickstart.md).
- The `argilla` sdk package installed in your environment.
- An Argilla 1.* server instance running with legacy datasets (or Extralit <1.29 with legacy datasets).
- An Extralit >=1.29 server instance running. If you don't have one, you can create one by following this [Extralit guide](../getting_started/quickstart.md).
- The `argilla` or `extralit` SDK package installed in your environment for migration.

!!! warning
This guide will recreate all `User`'s' and `Workspace`'s' on a new server. Hence, they will be created with new passwords and IDs. If you want to keep the same passwords and IDs, you can can copy the datasets to a temporary v2 instance, then upgrade your current instance to v2.0 and copy the datasets back to your original instance after.
Expand Down
Loading