refactor: Rework the use case pages - #266
Merged
Merged
Conversation
danielvallance
temporarily deployed
to
pull-requests
August 21, 2026 16:52 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
danielvallance
force-pushed
the
danielvallance/use_case_docs_rework
branch
from
August 21, 2026 17:08
5b506cb to
a049a7f
Compare
danielvallance
temporarily deployed
to
pull-requests
August 21, 2026 17:08 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
danielvallance
temporarily deployed
to
pull-requests
August 21, 2026 17:10 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
danielvallance
force-pushed
the
danielvallance/use_case_docs_rework
branch
from
August 24, 2026 08:45
a049a7f to
e8d3cc4
Compare
danielvallance
temporarily deployed
to
pull-requests
August 24, 2026 08:45 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
danielvallance
force-pushed
the
danielvallance/use_case_docs_rework
branch
from
August 24, 2026 13:18
e8d3cc4 to
e405855
Compare
danielvallance
temporarily deployed
to
pull-requests
August 24, 2026 13:18 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
danielvallance
force-pushed
the
danielvallance/use_case_docs_rework
branch
from
August 24, 2026 15:22
e405855 to
38db5a7
Compare
danielvallance
temporarily deployed
to
pull-requests
August 24, 2026 15:22 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
danielvallance
force-pushed
the
danielvallance/use_case_docs_rework
branch
from
August 25, 2026 10:27
38db5a7 to
b091fc2
Compare
danielvallance
temporarily deployed
to
pull-requests
August 25, 2026 10:28 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
danielvallance
force-pushed
the
danielvallance/use_case_docs_rework
branch
from
August 25, 2026 10:33
b091fc2 to
13d4a75
Compare
danielvallance
temporarily deployed
to
pull-requests
August 25, 2026 10:33 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
danielvallance
force-pushed
the
danielvallance/use_case_docs_rework
branch
from
August 25, 2026 10:42
13d4a75 to
61283d0
Compare
danielvallance
temporarily deployed
to
pull-requests
August 25, 2026 10:42 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
danielvallance
force-pushed
the
danielvallance/use_case_docs_rework
branch
from
August 25, 2026 11:56
61283d0 to
585911d
Compare
danielvallance
temporarily deployed
to
pull-requests
August 25, 2026 11:57 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
danielvallance
force-pushed
the
danielvallance/use_case_docs_rework
branch
from
August 25, 2026 16:51
585911d to
60c4c6e
Compare
danielvallance
temporarily deployed
to
pull-requests
August 25, 2026 16:51 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
danielvallance
force-pushed
the
danielvallance/use_case_docs_rework
branch
from
September 3, 2026 10:01
5362223 to
7073feb
Compare
danielvallance
temporarily deployed
to
pull-requests
September 3, 2026 10:01 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
danielvallance
force-pushed
the
danielvallance/use_case_docs_rework
branch
from
September 3, 2026 11:15
7073feb to
08a2d70
Compare
danielvallance
temporarily deployed
to
pull-requests
September 3, 2026 11:15 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
danielvallance
force-pushed
the
danielvallance/use_case_docs_rework
branch
from
September 3, 2026 11:49
08a2d70 to
e89d325
Compare
danielvallance
temporarily deployed
to
pull-requests
September 3, 2026 11:49 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
danielvallance
force-pushed
the
danielvallance/use_case_docs_rework
branch
from
September 3, 2026 11:52
e89d325 to
9ea174e
Compare
danielvallance
temporarily deployed
to
pull-requests
September 3, 2026 11:53 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
danielvallance
force-pushed
the
danielvallance/use_case_docs_rework
branch
from
September 3, 2026 12:31
9ea174e to
6656b19
Compare
danielvallance
temporarily deployed
to
pull-requests
September 3, 2026 12:31 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
danielvallance
force-pushed
the
danielvallance/use_case_docs_rework
branch
from
September 3, 2026 12:57
6656b19 to
d2c9ba5
Compare
danielvallance
temporarily deployed
to
pull-requests
September 3, 2026 12:57 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
There was a problem hiding this comment.
🟡 Changes recommended
Several pages present enterprise or preview-only capabilities without preserving their limited-access qualifications.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Review details
Suppressed comments (1)
pages/use-cases/serverless-databases.mdx:15
- Branching and checkpoints are presented here as immediately available headline workflows, but
pages/features/branching.mdx:7-9andpages/features/checkpoints.mdx:7-9say they are limited-access enterprise features and are still coming to the hosted platform. The rework removes the previous Limited Access cautions, so hosted users can reach the deployment CTA expecting capabilities they cannot use. Add a visible availability notice to this page.
<ValueCard title="Test migrations on a clone of production" metric="few ms downtime on the original">
[Branch](/features/branching) a running database (memory and [volume](/platform/volumes) state included) and run the risky migration against the copy.
</ValueCard>
<ValueCard title="Restore from a known good snapshot" metric="restore in < 10 ms">
[Checkpoints](/features/checkpoints) keep a history of full instance state, so rolling back is a restore rather than a rebuild.
- Files reviewed: 15/15 changed files
- Comments generated: 10
- Review effort level: Balanced
Comment on lines
+33
to
+36
| <FlowArrow label="outbound" /> | ||
| <FlowBox accent title="Network shield" chip="third-party API"> | ||
| Filters traffic, injects the secrets; servers never hold them | ||
| </FlowBox> |
Comment on lines
+16
to
+20
| tags={[ | ||
| { label: "shield", href: "/features/network-shield" }, | ||
| { label: "branching", href: "/features/branching" }, | ||
| { label: "checkpointing", href: "/features/checkpoints" }, | ||
| ]} |
Comment on lines
+14
to
+15
| <ValueCard title="Clone the environment" metric="clone in < 10 ms"> | ||
| [Branch](/features/branching) a running desktop to hand someone an identical, already-configured session. |
Comment on lines
+56
to
+57
| <FeatureRow title="Network shield" href="/features/network-shield"> | ||
| Restrict what the environment can reach and inject the secrets it needs. |
Comment on lines
+15
to
+19
| <ValueCard title="Genuinely secure sandboxes" metric="own kernel · secrets never enter the sandbox"> | ||
| Every sandbox is a hardware-isolated microVM with its own kernel, not a container sharing the host's. | ||
| Its traffic leaves through a [shield](/features/network-shield) microVM that filters egress and holds your credentials, so untrusted code can use an API without ever seeing the key. | ||
| </ValueCard> | ||
| <ValueCard title="Branch, checkpoint, run as many as you need" metric="branch & restore in < 10 ms · platform is built for scale"> |
The aim of this rework is to more visually demonstrate the value adds to someone who is not familiar with Unikraft Cloud by using clear concise language, diagrams, and a clear call to action. Closes: FIELD-711 Closes: FIELD-712 Closes: FIELD-713 Closes: FIELD-714 Signed-off-by: Daniel Vallance <daniel@unikraft.com>
danielvallance
force-pushed
the
danielvallance/use_case_docs_rework
branch
from
September 3, 2026 13:12
d2c9ba5 to
f202962
Compare
danielvallance
temporarily deployed
to
pull-requests
September 3, 2026 13:12 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
aabedraba
self-requested a review
September 3, 2026 13:14
aabedraba
approved these changes
Sep 3, 2026
aabedraba
left a comment
aabedraba
left a comment
Contributor
There was a problem hiding this comment.
My favorite new section of the docs! 😍✅
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The aim of this rework is to more visually
demonstrate the value adds to someone who
is not familiar with Unikraft Cloud by using
clear concise language, diagrams, and a clear
call to action.