Skip to content
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

docs(images): improve SEO in documentation #2122

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
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
4 changes: 2 additions & 2 deletions content/docs/get-started-with-neon/dev-experience.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ Discover how Neon's features can streamline your development process, reduce ris

Neon's branching feature lets you branch your data like you branch code. Neon branches are full database copies, including both schema and data. You can instantly create database branches for integration with your development workflows.

![Branching workflows](/docs/get-started-with-neon/branching_workflow.jpg)
![Neon Postgres database branching workflow](/docs/get-started-with-neon/branching_workflow.jpg)

You can build your database branching workflows using the Neon CLI, Neon API, or GitHub Actions. For example, this example shows how to create a development branch from `main` with a simple CLI command:

Expand Down Expand Up @@ -53,7 +53,7 @@ To help you find the correct restore point, Neon provides a [Time Travel Assist]

The [Neon serverless driver](https://neon.tech/docs/serverless/serverless-driver), which currently has over [100K weekly downloads](https://www.npmjs.com/package/@neondatabase/serverless), is a low-latency Postgres driver designed for JavaScript and TypeScript applications. It enables you to query data from edge and serverless environments like **Vercel Edge Functions** or **Cloudflare Workers** over HTTP or WebSockets instead of TCP. This capability is particularly useful for achieving reduced query latencies, with the potential to achieve [sub-10ms Postgres query times](https://neon.tech/blog/sub-10ms-postgres-queries-for-vercel-edge-functions) when querying from Edge or serverless functions. But don't take our word for it. Try it for yourself with Vercel's [Functions + Database Latency app](https://db-latency.vercel.app/). This graph shows latencies for Neon's serverless driver:

![Vercel's Functions Database Latency app](/docs/get-started-with-neon/latency_distribution_graph.png)
![Vercel's Functions Database Latency graph displaying latency distribution for Neon database queries](/docs/get-started-with-neon/latency_distribution_graph.png)

## Postgres extension support

Expand Down
8 changes: 4 additions & 4 deletions content/docs/get-started-with-neon/signing-up.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ After signing up, you'll start with a `main` branch and the empty database `neon

</div>
<div style={{ flex: '1 1 0', marginTop: '-1.25rem' }}>
![sign_up](/docs/get-started-with-neon/sign_up_reduced.png "no-border")
![Neon Sign_up](/docs/get-started-with-neon/sign_up_reduced.png "no-border")
</div>
</div>

Expand All @@ -58,10 +58,10 @@ After you sign up, you are guided through some onboarding steps that ask you to

<div style={{ display: 'flex' }}>
<div style={{ flex: '0 0 45%', paddingRight: '20px', marginTop: '.75em'}}>
![onboarding](/docs/get-started-with-neon/onboarding.png "no-border")
![Neon Onboarding](/docs/get-started-with-neon/onboarding.png "no-border")
</div>
<div style={{ flex: '0 0 55%', display: 'flex', alignItems: 'center' }}>
![quickstart](/docs/get-started-with-neon/quickstart.png "no-border")
![Neon Quickstart](/docs/get-started-with-neon/quickstart.png "no-border")
</div>
</div>

Expand Down Expand Up @@ -107,7 +107,7 @@ Your default branch `main` now has a table with some data.

Now that you have some data to play with, let's take a look at it on the **Tables** page in the Neon Console. The **Tables** page, powered by [Drizzle Studio](https://orm.drizzle.team/drizzle-studio/overview), provides a visual interface for exploring and modifying data directly from the console. The integration with Drizzle Studio provides the ability to add, update, and delete records, filter data, add or remove columns, drop or truncate tables, and export data in `.json` and `.csv` formats.

![Tables page Drizzle integration](/docs/relnotes/tables_page_drizzle.png)
![Neon Tables Page Drizzle Integration](/docs/relnotes/tables_page_drizzle.png)

For a detailed guide on how to interact with your data using the **Tables** page, visit [Managing your data with interactive tables](/docs/guides/tables).

Expand Down
2 changes: 1 addition & 1 deletion content/docs/get-started-with-neon/workflow-primer.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ postgresql://database_name_owner:[email protected]

You can create all of your branches from the default branch, or set up a dedicated branch that you use as a base. The first approach is simpler, while the second provides greater data isolation.

![database workflow A B](/docs/get-started-with-neon/database_workflow_AB.jpg)
![Neon Database Branch Workflow](/docs/get-started-with-neon/database_workflow_AB.jpg)

## Create branch methods

Expand Down