Skip to content

Commit 36530ea

Browse files
committed
add section about the next steps after creating a Polylith Workspace
1 parent 68ec48a commit 36530ea

File tree

1 file changed

+19
-1
lines changed

1 file changed

+19
-1
lines changed

docs/setup.md

+19-1
Original file line numberDiff line numberDiff line change
@@ -218,9 +218,27 @@ Finally, remove the `src` boilerplate code that was added by uv in the first ste
218218
rm -r src
219219
```
220220

221+
221222
### Pantsbuild (aka Pants)
222223
Have a look in the Pants-specific [example repository](examples.md) for details on the setup.
223224
You will find examples of combining Pants with Polylith, by using the Hatch build backend in the project-specific configurations.
224225

225226

226-
You will find more documentation about the available commands in the [commands](commands.md) section.
227+
## Next steps
228+
You now have the repo structured as a Polylith Workspace. Great!
229+
Add Python code to the Workspace by creating _bases_ and _components_.
230+
The common name is _bricks_ (like LEGO bricks).
231+
There's more about the Workspace and the bricks in the [Polylith Workspace](workspace.md) section.
232+
233+
The Polylith tool includes commands to create _bases_ and _components_.
234+
You will find documentation about commands in the [Commands](commands.md) section.
235+
236+
Example (using uv):
237+
238+
``` shell
239+
# create a base
240+
uv run poly create base --name my_base
241+
242+
# create a component
243+
uv run poly create component --name my_component
244+
```

0 commit comments

Comments
 (0)