diff --git a/.github/workflows/CI.yml b/.github/workflows/CI.yml
index 8edcef150..f49cef86f 100644
--- a/.github/workflows/CI.yml
+++ b/.github/workflows/CI.yml
@@ -48,8 +48,11 @@ jobs:
       - uses: julia-actions/setup-julia@v1
         with:
           version: '1'
-      - uses: julia-actions/julia-buildpkg@v1
+      - name: Build and add versions
+        run: julia --project=docs -e 'using Pkg; Pkg.add([PackageSpec(path = "."), PackageSpec(name = "GeoMakie", rev = "master"), PackageSpec(name = "DimensionalData", rev = "main"), PackageSpec(name = "Rasters", rev = "la/compacts")])'
       - uses: julia-actions/julia-docdeploy@v1
+        with:
+          install-package: false
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
       - run: |
diff --git a/benchmarks/benchmark_plots.jl b/benchmarks/benchmark_plots.jl
index e9255120c..b0f5432a4 100644
--- a/benchmarks/benchmark_plots.jl
+++ b/benchmarks/benchmark_plots.jl
@@ -68,7 +68,7 @@ end
 function plot_trials(
         gp::Makie.GridPosition,
         results;
-        theme = merge(deepcopy(Makie.CURRENT_DEFAULT_THEME), MakieThemes.bbc()),
+        theme = MakieThemes.bbc(),
         legend_position = Makie.automatic, #(1, 1, TopRight()),
         legend_orientation = :horizontal,
         legend_halign = 1.0,
diff --git a/docs/Project.toml b/docs/Project.toml
index 268f76249..fccffcc39 100644
--- a/docs/Project.toml
+++ b/docs/Project.toml
@@ -8,17 +8,23 @@ CoordinateTransformations = "150eb455-5306-5404-9cee-2592286d6298"
 DataFrames = "a93c6f00-e57d-5684-b7b6-d8193f3e46c0"
 DataInterpolations = "82cc6244-b520-54b8-b5a6-8a565e85f1d0"
 DataStructures = "864edb3b-99cc-5e75-8d2d-829cb0a9cfe8"
+DisplayAs = "0b91fe84-8a4c-11e9-3e1d-67c38462b6d6"
 Distributions = "31c24e10-a181-5473-b8eb-7969acd0382f"
 Documenter = "e30172f5-a6a5-5a46-863b-614d45cd2de4"
 DocumenterVitepress = "4710194d-e776-4893-9690-8d956a29c365"
 DoubleFloats = "497a8b3b-efae-58df-a0af-a86822472b78"
+Downloads = "f43a241f-c20a-4ad4-852c-f6b1247861c6"
+ExactPredicates = "429591f6-91af-11e9-00e2-59fbe8cec110"
 FlexiJoins = "e37f2e79-19fa-4eb7-8510-b63b51fe0a37"
 GADM = "a8dd9ffe-31dc-4cf5-a379-ea69100a8233"
-ExactPredicates = "429591f6-91af-11e9-00e2-59fbe8cec110"
+GeoDataFrames = "62cb38b5-d8d2-4862-a48e-6a340996859f"
 GeoDatasets = "ddc7317b-88db-5cb5-a849-8449e5df04f9"
+GeoFormatTypes = "68eda718-8dee-11e9-39e7-89f7f65f511f"
 GeoInterface = "cf35fbd7-0cd7-5166-be24-54bfbe79505f"
 GeoInterfaceMakie = "0edc0954-3250-4c18-859d-ec71c1660c08"
 GeoJSON = "61d90e0f-e114-555e-ac52-39dfb47a3ef9"
+GeoMakie = "db073c08-6b98-4ee5-b6a4-5efafb3259c6"
+GeoParquet = "e99870d8-ce00-4fdd-aeee-e09192881159"
 GeometryBasics = "5c1252a2-5f33-56bf-86c9-59e7332b4326"
 GeometryOps = "3251bfac-6a57-4b6d-aa61-ac1fef2975ab"
 LibGEOS = "a90b1aa1-3769-5649-ba7e-abc5a9d163eb"
@@ -34,3 +40,4 @@ Proj = "c94c279d-25a6-4763-9509-64d165bea63e"
 Random = "9a3f8284-a2c9-5f02-9a11-845980a1fd5c"
 Shapefile = "8e980c4a-a4fe-5da2-b3a7-4b4b0353a2f4"
 Statistics = "10745b16-79ce-11e8-11f9-7d13ad32a3b2"
+Weave = "44d3d7a6-8a23-5bf8-98c5-b353f8df5ec9"
diff --git a/docs/make.jl b/docs/make.jl
index 19efdfc6a..80f6b6246 100644
--- a/docs/make.jl
+++ b/docs/make.jl
@@ -95,11 +95,12 @@ makedocs(;
         "Introduction" => "introduction.md",
         "API Reference" => "api.md",
         "Tutorials" => [
+            "Creating Geometry" => "tutorials/creating_geometry.md",
             "Spatial Joins" => "tutorials/spatial_joins.md",
         ],
         "Explanations" => [
-            "Paradigms" => "paradigms.md",
-            "Peculiarities" => "peculiarities.md",
+            "Paradigms" => "explanations/paradigms.md",
+            "Peculiarities" => "explanations/peculiarities.md",
         ],
         "Source code" => literate_pages,
     ],
diff --git a/docs/src/explanations/crs.md b/docs/src/explanations/crs.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/docs/src/paradigms.md b/docs/src/explanations/paradigms.md
similarity index 100%
rename from docs/src/paradigms.md
rename to docs/src/explanations/paradigms.md
diff --git a/docs/src/peculiarities.md b/docs/src/explanations/peculiarities.md
similarity index 100%
rename from docs/src/peculiarities.md
rename to docs/src/explanations/peculiarities.md
diff --git a/docs/src/explanations/winding_order.md b/docs/src/explanations/winding_order.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/docs/src/tutorials/creating_geometry.md b/docs/src/tutorials/creating_geometry.md
new file mode 100644
index 000000000..f3cc6f640
--- /dev/null
+++ b/docs/src/tutorials/creating_geometry.md
@@ -0,0 +1,339 @@
+# Creating Geometry
+
+In this tutorial, we're going to:
+1. [Create and plot geometries](@ref creating-geometry)
+2. [Plot geometries on a map using `GeoMakie` and coordinate reference system (`CRS`)](@ref plot-geometry)
+3. [Create geospatial geometries with coordinate reference system information](@ref geom-crs)
+4. [Assign attributes to geospatial geometries](@ref attributes)
+5. [Save geospatial geometries to common geospatial file formats](@ref save-geometry)
+
+
+
+First, we load some required packages.
+
+````@example creating_geometry
+# Geospatial packages from Julia
+import GeoInterface as GI
+import GeometryOps as GO
+import GeoFormatTypes as GFT
+using GeoJSON # to load some data
+# Packages for coordinate transformation and projection
+import CoordinateTransformations
+import Proj
+# Plotting
+using CairoMakie
+using GeoMakie
+using DisplayAs # hide
+Makie.set_theme!(Makie.MAKIE_DEFAULT_THEME) # hide
+````
+
+## [Creating and plotting geometries](@id creating-geometry)
+
+Let's start by making a single `Point`.
+
+````@example creating_geometry
+point = GI.Point(0, 0)
+````
+
+Now, let's plot our point.
+
+````@example creating_geometry
+fig, ax, plt = plot(point)
+````
+
+Let's create a set of points, and have a bit more fun with plotting.
+
+````@example creating_geometry
+x = [-5, 0, 5, 0];
+y = [0, -5, 0, 5];
+points = GI.Point.(zip(x,y));
+plot!(ax, points; marker = '✈', markersize = 30)
+fig
+````
+
+`Point`s can be combined into a single `MultiPoint` geometry. 
+
+````@example creating_geometry
+x = [-5, -5, 5, 5];
+y = [-5, 5, 5, -5];
+multipoint = GI.MultiPoint(GI.Point.(zip(x, y)));
+plot!(ax, multipoint; marker = '☁', markersize = 30)
+fig
+````
+
+Let's create a `LineString` connecting two points.
+
+````@example creating_geometry
+p1 = GI.Point.(-5, 0);
+p2 = GI.Point.(5, 0);
+line = GI.LineString([p1,p2])
+plot!(ax, line; color = :red)
+fig
+````
+
+Now, let's create a line connecting multiple points (i.e. a `LineString`).
+This time we get a bit more fancy with point creation.
+
+````@example creating_geometry
+r = 2;
+k = 10;
+ϴ = 0:0.01:2pi;
+x = r .* (k + 1) .* cos.(ϴ) .- r .* cos.((k + 1) .* ϴ);
+y = r .* (k + 1) .* sin.(ϴ) .- r .* sin.((k + 1) .* ϴ);
+lines = GI.LineString(GI.Point.(zip(x,y)));
+plot!(ax, lines; linewidth = 5)
+fig
+````
+
+We can also create a single `LinearRing` trait, the building block of a polygon.
+A `LinearRing` is simply a `LineString` with the same beginning and endpoint, i.e., an arbitrary closed shape composed of point pairs.
+
+A `LinearRing` is composed of a series of points.
+
+````@example creating_geometry
+ring1 = GI.LinearRing(GI.getpoint(lines));
+````
+
+Now, let's make the `LinearRing` into a `Polygon`.
+
+````@example creating_geometry
+polygon1 = GI.Polygon([ring1]);
+````
+
+Now, we can use GeometryOps and CoordinateTransformations to shift `polygon1` up, to avoid plotting over our earlier results.  This is done through the [GeometryOps.transform](@ref) function.
+
+````@example creating_geometry
+xoffset = 0.;
+yoffset = 50.;
+f = CoordinateTransformations.Translation(xoffset, yoffset);
+polygon1 = GO.transform(f, polygon1);
+plot!(polygon1)
+fig
+````
+
+Polygons can contain "holes". The first `LinearRing` in a polygon is the exterior, and all subsequent `LinearRing`s are treated as holes in the leading `LinearRing`.
+
+`GeoInterface` offers the `GI.getexterior(poly)` and `GI.gethole(poly)` methods to get the exterior ring and an iterable of holes, respectively.
+
+````@example creating_geometry
+hole = GI.LinearRing(GI.getpoint(multipoint))
+polygon2 = GI.Polygon([ring1, hole])
+````
+
+Shift `polygon2` to the right, to avoid plotting over our earlier results.
+
+````@example creating_geometry
+xoffset = 50.;
+yoffset = 0.;
+f = CoordinateTransformations.Translation(xoffset, yoffset);
+polygon2 = GO.transform(f, polygon2);
+plot!(polygon2)
+fig
+````
+
+`Polygon`s can also be grouped together as a `MultiPolygon`.
+
+````@example creating_geometry
+r = 5;
+x = cos.(reverse(ϴ)) .* r .+ xoffset;
+y = sin.(reverse(ϴ)) .* r .+ yoffset;
+ring2 =  GI.LinearRing(GI.Point.(zip(x,y)));
+polygon3 = GI.Polygon([ring2]);
+multipolygon = GI.MultiPolygon([polygon2, polygon3])
+````
+
+Shift `multipolygon` up, to avoid plotting over our earlier results.
+
+````@example creating_geometry
+xoffset = 0.;
+yoffset = 50.;
+f = CoordinateTransformations.Translation(xoffset, yoffset);
+multipolygon = GO.transform(f, multipolygon);
+plot!(multipolygon)
+fig
+````
+
+Great, now we can make `Points`, `MultiPoints`, `Lines`, `LineStrings`, `Polygons` (with holes), and `MultiPolygons` and modify them using [`CoordinateTransformations`] and [`GeometryOps`].
+
+## [Coordinate reference systems (CRS) and you](@id geom-crs) 
+
+In geospatial sciences we often have data in one [Coordinate Reference System (CRS)](https://en.wikipedia.org/wiki/Spatial_reference_system) (`source`) and would like to display it in different (`destination`) `CRS`. `GeoMakie` allows us to do this by automatically projecting from `source` to `destination` CRS.
+
+Here, our `source` CRS is common geographic (i.e. coordinates of latitude and longitude), [WGS84](https://epsg.io/4326).
+
+````@example creating_geometry
+source_crs1 = GFT.EPSG(4326)
+````
+
+Now let's pick a `destination` CRS for displaying our map. Here we'll pick [natearth2](https://proj.org/en/9.4/operations/projections/natearth2.html).
+
+````@example creating_geometry
+destination_crs = "+proj=natearth2"
+````
+
+Let's add land area for context. First, download and open the [Natural Earth](https://www.naturalearthdata.com) global land polygons at 110 m resolution.`GeoMakie` ships with this particular dataset, so we will access it from there.
+
+````@example creating_geometry
+land_path = GeoMakie.assetpath("ne_110m_land.geojson")
+````
+
+!!! note
+    Natural Earth has lots of other datasets, and there is a Julia package that provides an interface to it called [NaturalEarth.jl](https://github.com/JuliaGeo/NaturalEarth.jl).
+
+Read the land `MultiPolygon`s as a `GeoJSON.FeatureCollection`.
+
+````@example creating_geometry
+land_geo = GeoJSON.read(land_path)
+````
+
+We then need to create a figure with a `GeoAxis` that can handle the projection between `source` and `destinaton` CRS. For GeoMakie, `source` is the CRS of the input and `dest` is the CRS you want to visualize in.
+
+````@example creating_geometry
+fig = Figure(size=(1000, 500));
+ga = GeoAxis(
+    fig[1, 1];
+    source = source_crs1,
+    dest = destination_crs,
+    xticklabelsvisible = false,
+    yticklabelsvisible = false,
+);
+nothing #hide
+````
+
+Plot `land` for context.
+
+````@example creating_geometry
+poly!(ga, land_geo, color=:black)
+fig
+````
+
+Now let's plot a `Polygon` like before, but this time with a CRS that differs from our `source` data
+
+````@example creating_geometry
+plot!(multipolygon; color = :green)
+fig
+````
+
+But what if we want to plot geometries with a different `source` CRS on the same figure?
+
+To show how to do this let's create a geometry with coordinates in UTM (Universal Transverse Mercator) zone 10N [EPSG:32610](https://epsg.io/32610).
+
+````@example creating_geometry
+source_crs2 = GFT.EPSG(32610)
+````
+
+Create a polygon (we're working in meters now, not latitude and longitude)
+````@example creating_geometry
+r = 1000000;
+ϴ = 0:0.01:2pi;
+x = r .* cos.(ϴ).^3 .+ 500000;
+y = r .* sin.(ϴ) .^ 3 .+5000000;
+DisplayAs.setcontext(y, :compact => true, :displaysize => (10, 40),) # hide
+````
+
+Now create a `LinearRing` from `Points`
+
+````@example creating_geometry
+ring3 = GI.LinearRing(Point.(zip(x, y)))
+````
+
+Now create a `Polygon` from the `LineRing` 
+
+````@example creating_geometry
+polygon3 = GI.Polygon([ring3])
+````
+
+Now plot on the existing GeoAxis. 
+
+!!! note
+    The keyword argument `source` is used to specify the source `CRS` of that particular plot, when plotting on an existing `GeoAxis`.
+
+````@example creating_geometry
+plot!(ga,polygon3; color=:red, source = source_crs2)
+fig
+````
+
+Great, we can make geometries and plot them on a map... now let's export the data to common geospatial data formats. To do this we now need to create geometries with embedded `CRS` information, making it a geospatial geometry. All that's needed is to include `; crs = crs` as a keyword argument when constructing the geometry.
+
+Let's do this for a new `Polygon`
+````@example creating_geometry
+r = 3;
+k = 7;
+ϴ = 0:0.01:2pi;
+x = r .* (k + 1) .* cos.(ϴ) .- r .* cos.((k + 1) .* ϴ);
+y = r .* (k + 1) .* sin.(ϴ) .- r .* sin.((k + 1) .* ϴ);
+ring4 = GI.LinearRing(Point.(zip(x, y)))
+````
+
+But this time when we create the `Polygon` we beed to specify the `CRS` at the time of creation, making it a geospatial polygon
+
+````@example creating_geometry
+geopoly1 = GI.Polygon([ring4], crs = source_crs1)
+````
+
+!!! note
+    It is good practice to only include CRS information with the highest-level geometry. Not doing so can bloat the memory footprint of the geometry. CRS information _can_ be included at the individual `Point` level but is discouraged.
+
+And let's create second `Polygon` by shifting the first using CoordinateTransformations
+
+````@example creating_geometry
+xoffset = 20.;
+yoffset = -25.;
+f = CoordinateTransformations.Translation(xoffset, yoffset);
+geopoly2 = GO.transform(f, geopoly1);
+````
+
+## [Creating a table with attributes and geometry](@id attributes)
+
+Typically, you'll also want to include attributes with your geometries. Attributes are simply data that are attributed to each geometry. The easiest way to do this is to create a table with a `:geometry` column. Let's do this using [`DataFrames`](https://github.com/JuliaData/DataFrames.jl).
+
+````@example creating_geometry
+using DataFrames
+df = DataFrame(geometry=[geopoly1, geopoly2])
+````
+
+Now let's add a couple of attributes to the geometries.  We do this using [DataFrames' `!` mutation syntax](https://dataframes.juliadata.org/stable/man/getting_started/#The-DataFrame-Type) that allows you to add a new column to an existing data frame.
+
+````@example creating_geometry
+df[!,:id] = ["a", "b"]
+df[!, :name] = ["polygon 1", "polygon 2"]
+df
+````
+
+## [Saving your geospatial data](@id save-geometry)
+
+There are Julia packages for most commonly used geographic data formats.  Below, we show how to export that data to each of these.
+
+We begin with [GeoJSON](https://github.com/JuliaGeo/GeoJSON.jl), which is a [JSON](https://en.wikipedia.org/wiki/JSON) format for geospatial feature collections.  It's human-readable and widely supported by most web-based and desktop geospatial libraries.
+
+````@example creating_geometry
+import GeoJSON
+fn = "shapes.json"
+GeoJSON.write(fn, df)
+````
+
+Now, let's save as a [`Shapefile`](https://github.com/JuliaGeo/Shapefile.jl).  Shapefiles are actually a set of files (usually 4) that hold geometry information, a CRS, and additional attribute information as a separate table.  When you give `Shapefile.write` a file name, it will write 4 files of the same name but with different extensions.
+
+````@example creating_geometry
+import Shapefile
+fn = "shapes.shp"
+Shapefile.write(fn, df)
+````
+
+Now, let's save as a [`GeoParquet`](https://github.com/JuliaGeo/GeoParquet.jl).  GeoParquet is a geospatial extension to the [Parquet](https://parquet.apache.org/) format, which is a high-performance data store.  It's great for storing large amounts of data in a single file.
+
+````@example creating_geometry
+import GeoParquet
+fn = "shapes.parquet"
+GeoParquet.write(fn, df, (:geometry,))
+````
+
+Finally, if there's no Julia-native package that can write data to your desired format (e.g. `.gpkg`, `.gml`, etc), you can use [`GeoDataFrames`](https://github.com/evetion/GeoDataFrames.jl). This package uses the [GDAL](https://gdal.org/) library under the hood which supports writing to nearly all geospatial formats.
+
+````@example creating_geometry
+import GeoDataFrames
+fn = "shapes.gpkg"
+GeoDataFrames.write(fn, df)
+````
+
+And there we go, you can now create mapped geometries from scratch, manipulate them, plot them on a map, and save them in multiple geospatial data formats.
\ No newline at end of file
diff --git a/src/methods/orientation.jl b/src/methods/orientation.jl
index d584d9998..b0bf868dc 100644
--- a/src/methods/orientation.jl
+++ b/src/methods/orientation.jl
@@ -19,17 +19,19 @@ export isclockwise, isconcave
 """
     isclockwise(line::Union{LineString, Vector{Position}})::Bool
 
-Take a ring and return true or false whether or not the ring is clockwise or
-counter-clockwise.
+Take a ring and return `true` if the line goes clockwise, or `false` if the line goes
+counter-clockwise.  "Going clockwise" means, mathematically,
 
-## Example
-
-```jldoctest
-import GeoInterface as GI, GeometryOps as GO
+```math
+\\left(\\sum_{i=2}^n (x_i - x_{i-1}) \\cdot (y_i + y_{i-1})\\right) > 0
+```
 
-ring = GI.LinearRing([(0, 0), (1, 1), (1, 0), (0, 0)])
-GO.isclockwise(ring)
+## Example
 
+```julia
+julia> import GeoInterface as GI, GeometryOps as GO
+julia> ring = GI.LinearRing([(0, 0), (1, 1), (1, 0), (0, 0)]);
+julia> GO.isclockwise(ring)
 # output
 true
 ```