recommend manual publishing (#1260)

* recommend manual publishing

* woops

Author: adhami3310

docs/custom-components/command-reference.md

@@ -22,10 +22,9 @@ Options:
   --help  Show this message and exit.
 
 Commands:
-  build    Build a custom component.
   init     Initialize a custom component.
-  publish  Publish a custom component.
-""")
+  build    Build a custom component.
+  share    Collect more details on the published package for gallery.""")
 ```
 
 ## reflex component init
@@ -140,54 +139,9 @@ Options:
 
 ## reflex component publish
 
-To publish to a package index, a user is required to already have an account with them. As of **0.4.3**, Reflex only supports uploading to PyPI and TestPyPI. Those indices are separate PyPI and TestPyPI should have sufficient documentation on the account creation and how to generate API tokens. We also have a [short guide]({custom_components.overview.path}) covering this topic.
-
-The publish process starts with a build if needed. If the distribution files for the version specified in pyproject.toml file already exist, the command prompts the user to confirm rebuilding the files nor not. After making sure the distribution files are ready, the command proceeds to upload them to the specified python package index.
-
-```python eval
-doccmdoutput(
-    command="reflex component publish --help",
-    output="""
-reflex component publish --help
-Usage: reflex component publish [OPTIONS]
-
-  Publish a custom component. Must be run from the project root directory
-  where the pyproject.toml is.
-
-  Args:     repository: The name of the Python package repository, such pypi,
-  testpypi.     token: The token to use for authentication on python package
-  repository. If token is provided, no username/password should be provided at
-  the same time.     username: The username to use for authentication on
-  python package repository.     password: The password to use for
-  authentication on python package repository.     loglevel: The log level to
-  use.
+To publish to a package index, a user is required to already have an account with them. As of **0.7.5**, Reflex does not handle the publishing process for you. You can do so manually by first running `reflex component build` followed by `twine upload` or `uv publish` or your choice of a publishing utility.
 
-  Raises:     Exit: If arguments provided are not correct or the publish
-  fails.
-
-Options:
-  -r, --repository TEXT           The name of the repository. Defaults to
-                                  pypi. Only supports pypi and testpypi (Test
-                                  PyPI) for now.
-  -t, --token TEXT                The API token to use for authentication on
-                                  python package repository. If token is
-                                  provided, no username/password should be
-                                  provided at the same time
-  -u, --username TEXT             The username to use for authentication on
-                                  python package repository. Username and
-                                  password must both be provided.
-  -p, --password TEXT             The password to use for authentication on
-                                  python package repository. Username and
-                                  password must both be provided.
-  --build / --no-build            Whether to build the package before
-                                  publishing. If the package is already built,
-                                  set this to False.  [default: build]
-  --loglevel [debug|info|warning|error|critical]
-                                  The log level to use.  [default:
-                                  LogLevel.INFO]
-  --help                          Show this message and exit.
-""")
-```
+You can then share your build on our website with `reflex component share`.
 
 ## reflex component build
 

docs/custom-components/overview.md

@@ -8,11 +8,10 @@ from pcweb.pages.docs.custom_components import custom_components as custom_compo
 
 Reflex users create many components of their own: ready to use high level components, or nicely wrapped React components. With **Custom Components**, the community can easily share these components now.
 
-Release **0.4.3** introduces a series of `reflex component` commands that help developers wrap react components, test, and publish them as python packages. As shown in the image below, there are already a few custom components published on PyPI, such as `reflex-spline`, `reflex-webcam`. 
+Release **0.4.3** introduces a series of `reflex component` commands that help developers wrap react components, test, and publish them as python packages. As shown in the image below, there are already a few custom components published on PyPI, such as `reflex-spline`, `reflex-webcam`.
 
 Check out the custom components gallery [here]({custom_components_gallery.path}).
 
-
 ```python eval
 rx.center(
   rx.image(src="/custom_components/pypi_reflex_custom_components.png", width="400px", border_radius="15px", border="1px solid"),
@@ -29,7 +28,8 @@ Follow these steps to publish the custom component as a python package:
 
 1. `reflex component init`: creates a new custom component project from templates.
 2. dev and test: developer implements and tests the custom component.
-3. `reflex component publish`: builds and uploads the package to a python package index.
+3. `reflex component build`: builds the package.
+4. `twine upload` or `uv publish`: uploads the package to a python package index.
 
 ### Initialization
 
@@ -64,7 +64,11 @@ After finishing the custom component implementation, the user is encouraged to f
 ### Publish
 
 ```bash
-reflex component publish
+reflex component build
 ```
 
-Once ready to publish, execute `reflex component publish` with the credentials in the command options (either `--username` and `--password` together or `--token`). First the command builds the distribution files if they are not already built. The end result is a `dist` folder containing the distribution files. The user does not need to do anything manually with these distribution files. The the command proceeds to publish those files. The same version of the package can only be published once. If already exists, the publish ends in error. The user can go to the `pyproject.toml` file and update the version number as desired. After the `publish` command finishes successfully, the package is uploaded to PyPI. 🎉
+Once you're ready to publish your package, run `reflex component build` to build the package. The command builds the distribution files if they are not already built. The end result is a `dist` folder containing the distribution files. The user does not need to do anything manually with these distribution files.
+
+In order to publish these files as a Python package, you need to use a publishing utility. Any would work, but we recommend either [Twine](https://twine.readthedocs.io/en/stable/) or (uv)[https://docs.astral.sh/uv/guides/package/#publishing-your-package]. Make sure to keep your package version in pyproject.toml updated.
+
+You can also share your components with the rest of the community at our website using the command `reflex component share`. See you there!

docs/custom-components/prerequisites-for-publishing.md

@@ -10,7 +10,7 @@ image_style = {
 }
 ```
 
-In order to publish a Python package, an account with the package index is required. As of **0.4.3**, Reflex only supports publishing to PyPI and TestPyPI. PyPI is short for **Python Package Index**, the official third-party software repository for Python. TestPyPI is a separate instance of index that allows users to test the distribution and installation of the package before publishing it to the real index.
+In order to publish a Python package, you need to use a publishing utility. Any would work, but we recommend either [Twine](https://twine.readthedocs.io/en/stable/) or (uv)[https://docs.astral.sh/uv/guides/package/#publishing-your-package].
 
 ## PyPI
 
@@ -22,7 +22,7 @@ rx.center(
 )
 ```
 
-A user can use username and password to authenticate with PyPI when publishing. Reflex does not store your PyPI credentials. If an API token is preferred, it can be generated in the account settings.
+A user can use username and password to authenticate with PyPI when publishing.
 
 ```python eval
 rx.center(
@@ -37,7 +37,3 @@ rx.center(
   rx.image(src="/custom_components/pypi_api_tokens.png", style=image_style, width="700px", loading="lazy"),
 )
 ```
-
-## TestPyPI
-
-TestPyPI has the same look and feel as PyPI.