-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Edit Docusaurus README.mds #14325
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
Edit Docusaurus README.mds #14325
Conversation
Documentation preview for f5f6eed will be available when this CircleCI job More info
|
.circleci/config.yml
Outdated
@@ -78,6 +78,7 @@ jobs: | |||
command: | | |||
yarn install | |||
yarn build-api-docs:no-r | |||
yarn update-api-modules |
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.
missed this in CI update
@@ -831,87 +831,24 @@ We use [taplo](https://taplo.tamasfe.dev/) to enforce consistent TOML formatting | |||
|
|||
### Writing Docs | |||
|
|||
First, install dependencies for building docs as described in [Environment Setup and Python configuration](#environment-setup-and-python-configuration). |
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.
old docs guide moved from CONTRIBUTING.md -> docs/api_reference/README.md
. since editing the API docs basically involves editing docstrings (and requires python + doc dependencies etc), i want to focus more on the main docs in this section.
``` | ||
|
||
If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the `gh-pages` branch. | ||
1. Run `yarn build-api-docs` in order to build the API reference and copy the generated HTML to `static/api_reference`. |
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.
Can we combine them into a single make task?
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.
done! combined them into yarn build-api-docs
a. To speed up the build locally, you can run `yarn build-api-docs:no-r` to skip building R documentation | ||
2. Run `yarn convert-notebooks` to convert `.ipynb` files to `.mdx` files. The generated files are git-ignored. | ||
3. **⚠️ Important!** Run `export DOCS_BASE_URL=/docs/latest` (or wherever the docs are expected to be served). This configures the [Docusaurus baseUrl](https://docusaurus.io/docs/api/docusaurus-config#baseUrl), and the site may not render correctly if this is improperly set. | ||
4. Finally, run `yarn build`. This generates static files in the `build` directory, which can then be served. |
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.
Can we also add yarn serve
as an optional step? This command allows testing prod-only features such as redirect.
``` | ||
$ USE_SSH=true yarn deploy | ||
``` | ||
This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server. |
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.
Let's add a note here saying some features might be disabled in this mode.
Example: https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-client-redirects
Signed-off-by: Daniel Lok <[email protected]>
Signed-off-by: Daniel Lok <[email protected]>
Signed-off-by: Daniel Lok <[email protected]>
Signed-off-by: Daniel Lok <[email protected]>
Signed-off-by: Daniel Lok <[email protected]>
Signed-off-by: Daniel Lok <[email protected]>
Signed-off-by: Daniel Lok <[email protected]>
Signed-off-by: Daniel Lok <[email protected]>
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.
Left some comments, otherwise LGTM!
Signed-off-by: Daniel Lok <[email protected]>
f931e90
to
f5f6eed
Compare
Signed-off-by: Daniel Lok <[email protected]> Signed-off-by: k99kurella <[email protected]>
Signed-off-by: Daniel Lok <[email protected]> Signed-off-by: k99kurella <[email protected]>
🛠 DevTools 🛠
Install mlflow from this PR
Checkout with GitHub CLI
Related Issues/PRs
#xxxWhat changes are proposed in this pull request?
This PR adds instructions for building the new Docusaurus docs!
How is this PR tested?
Does this PR require documentation update?
Release Notes
Is this a user-facing change?
What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/artifacts
: Artifact stores and artifact loggingarea/build
: Build and test infrastructure for MLflowarea/deployments
: MLflow Deployments client APIs, server, and third-party Deployments integrationsarea/docs
: MLflow documentation pagesarea/examples
: Example codearea/model-registry
: Model Registry service, APIs, and the fluent client calls for Model Registryarea/models
: MLmodel format, model serialization/deserialization, flavorsarea/recipes
: Recipes, Recipe APIs, Recipe configs, Recipe Templatesarea/projects
: MLproject format, project running backendsarea/scoring
: MLflow Model server, model deployment tools, Spark UDFsarea/server-infra
: MLflow Tracking server backendarea/tracking
: Tracking Service, tracking client APIs, autologgingInterface
area/uiux
: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/docker
: Docker use across MLflow's components, such as MLflow Projects and MLflow Modelsarea/sqlalchemy
: Use of SQLAlchemy in the Tracking Service or Model Registryarea/windows
: Windows supportLanguage
language/r
: R APIs and clientslanguage/java
: Java APIs and clientslanguage/new
: Proposals for new client languagesIntegrations
integrations/azure
: Azure and Azure ML integrationsintegrations/sagemaker
: SageMaker integrationsintegrations/databricks
: Databricks integrationsHow should the PR be classified in the release notes? Choose one:
rn/none
- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/breaking-change
- The PR will be mentioned in the "Breaking Changes" sectionrn/feature
- A new user-facing feature worth mentioning in the release notesrn/bug-fix
- A user-facing bug fix worth mentioning in the release notesrn/documentation
- A user-facing documentation change worth mentioning in the release notesShould this PR be included in the next patch release?
Yes
should be selected for bug fixes, documentation updates, and other small changes.No
should be selected for new features and larger changes. If you're unsure about the release classification of this PR, leave this unchecked to let the maintainers decide.What is a minor/patch release?
Bug fixes, doc updates and new features usually go into minor releases.
Bug fixes and doc updates usually go into patch releases.