Deuxfleurs/garage
31
61
Fork 80
Code Issues 91 Pull requests 13 Releases 30 Wiki Activity

Create a more *product focused* landing page #116

Merged
lx merged 3 commits from feature/improve-doc into main 2021-12-06 16:20:49 +00:00
Conversation 1 Commits 3 Files changed 16 +309 -112
quentin commented 2021-10-04 14:45:30 +00:00
Owner
Copy link

I wanted to create a more appealing home page for our documentation.
I see this proposition as a transition, between our quite technical and verbose page and our future standalone website for garage.

Here is a preview:

Preview of the new home page

I wanted to create a more appealing home page for our documentation. I see this proposition as a transition, between our quite technical and verbose page and our future standalone website for garage. Here is a preview: ![Preview of the new home page](https://git.deuxfleurs.fr/attachments/778b946c-bf31-4bcb-a28e-6974aec6cc83)
Screenshot 2021-10-04 at 16-43-54 The Garage Data Store - Garage Documentation.png
337 KiB
❤️ 1
trinity-1686a approved these changes 2021-12-06 13:46:03 +00:00
trinity-1686a left a comment
Owner
Copy link

f

f
doc/book/src/design/related_work.md Outdated
@ -45,0 +59,4 @@
Due to its industry oriented design, Ceph is also far from being *Simple* to operate and from being *Self-contained & lightweight* which makes it hard to integrate it in an hyperconverged infrastructure.
In a certain way, Ceph and MinIO are closer together than they are from Garage or OpenStack Swift.
**[Pithos](https://github.com/exoscale/pithos)**
trinity-1686a commented 2021-12-06 13:44:03 +00:00
Owner
Copy link

missing : before end of bold (to be coherent with other links)

missing `:` before end of bold (to be coherent with other links)
doc/book/src/design/related_work.md Outdated
@ -48,3 +66,4 @@
They built a closed-source version 2 that does not store blobs in the database (only metadata) but did not communicate further on it.
We considered there v2's design but concluded that it does not fit both our *Self-contained & lightweight* and *Simple* properties. It makes the development, the deployment and the operations more complicated while reducing the flexibility.
**[Riak CS](https://docs.riak.com/riak/cs/2.1.1/index.html)**
trinity-1686a commented 2021-12-06 13:45:08 +00:00
Owner
Copy link

same

same
doc/book/src/design/related_work.md Outdated
@ -51,1 +69,4 @@
**[Riak CS](https://docs.riak.com/riak/cs/2.1.1/index.html)**
*Not written yet*
**[IPFS](https://ipfs.io/) :**
trinity-1686a commented 2021-12-06 13:45:29 +00:00
Owner
Copy link

there is as space before the :

there is as space before the `:`
lx force-pushed feature/improve-doc from fb33f68f6a to 3dfe465bf9 2021-12-06 14:29:18 +00:00 Compare
lx force-pushed feature/improve-doc from 3dfe465bf9 to 66e7c06571 2021-12-06 15:10:49 +00:00 Compare
lx force-pushed feature/improve-doc from 252ab1ac45 to 224c89ad6e 2021-12-06 15:33:12 +00:00 Compare
lx added 1 commit 2021-12-06 16:18:56 +00:00
S3 compatibility target
Some checks reported errors
continuous-integration/drone/push Build is passing
Details
continuous-integration/drone/pr Build is passing
Details
continuous-integration/drone/tag Build is passing
Details
continuous-integration/drone Build encountered an error
Details
4b369347c0
lx commented 2021-12-06 16:19:14 +00:00
Owner
Copy link

fix #167

fix #167
lx changed title from WIP: Create a more *product focused* landing page to Create a more *product focused* landing page 2021-12-06 16:20:41 +00:00
lx merged commit 4b369347c0 into main 2021-12-06 16:20:49 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
trinity-1686a
Labels
Clear labels   
action
check-aws
The behaviour should be checked against AWS S3

  
action
discussion-needed
We need to discuss if the feature is desirable and/or better specify the envisioned behavior or technical implementation

  
action
for-external-contributors
Core team does not plan working on this in the near future however an external contribution will be reviewed & merged

  
action
for-newcomers
An issue that should be newcomer friendly.

  
action
more-info-needed
More information is needed to investigate this issue

  
action
need-funding
This issue represents lots of work, we need to find money to pay our core team work

  
action
triage-required
It's not very clear what we want to do with this issue yet, more thoughts is required

  
kind
correctness
Issues of theoretical correctness that may impact edge-case scenarios

  
kind/experimental

PRs implementing experimental features / features used only for debugging

  
kind
ideas
For abstract ideas/proposal to make Garage better, to better communicate our not yet achieved aims

  
kind
improvement
Feature requests that do not fall in other categories

  
kind
performance
Deceptive performance observed OR idea to improve performances

  
kind
testing
Functional tests, integration tests, Jepsen, etc.

  
kind
usability
Propositions to make Garage easier to operate, by improving error reporting, CLI, etc.

  
kind
wrong-behavior
Unintended behavior

  
prio
critical
Could impact integrity or availability of production clusters

  
prio
low
For issues that we don't want to spend time on until made absolutely necessary

  
scope
admin-api
Issues concerning the administration API

  
scope
background-healing
Background healing covers repair tasks, anti-entropy, merkle trees, etc. ; everything related to replicating data appropriately.

  
scope
build
Issues with Nix, Drone, Rust Compiler, etc.

  
scope
documentation

  
scope
k8s
Kubernetes related, including Helm Charts

  
scope
layout
Linked to the cluster layout and storage management

  
scope
metadata
Metadata Engine (LMDB, sqlite, etc.)

  
scope
ops
Operations related to operations/maintenance issue, tooling related (like CLI missing info ; impossible, too dangerous, too complicated migration, etc.)

  
scope
rpc
Linked to RPC

  
scope
s3-api
Related to the S3 API (especially compatibility issues).

  
scope
security
Cryptography-related, auth-related, authorization-related issues

  
scope
telemetry
OpenTelemetry (traces, metrics, etc.)

No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind/experimental
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Deuxfleurs/garage#116
No description provided.
Delete branch "feature/improve-doc"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?