Skip to content

Commit

Permalink
feat: Improve landing page; add assets; fix wording in documentation (#3
Browse files Browse the repository at this point in the history
)

Improve landing page; add assets; fix wording in documentation
  • Loading branch information
jimmarino authored Sep 14, 2024
1 parent fceb355 commit 21901b7
Show file tree
Hide file tree
Showing 6 changed files with 1,292 additions and 4 deletions.
20 changes: 20 additions & 0 deletions assets/icons/logo.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
16 changes: 14 additions & 2 deletions content/en/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: Eclipse Dataspace Components
---

{{< blocks/cover title="Enterprise data-sharing at scale" image_anchor="top" height="full" >}}
{{< blocks/cover title="Data-sharing at scale" image_anchor="top" >}}
<a class="btn btn-lg btn-primary me-3 mb-4" href="/documentation/">
Learn More <i class="fas fa-arrow-alt-circle-right ms-2"></i>
</a>
Expand All @@ -11,8 +11,20 @@ GitHub <i class="fab fa-github ms-2 "></i>
</a>
<p class="lead mt-5">EDC is an open source framework hosted by the Eclipse Foundation for building secure, globally-scalable data-sharing services.
EDC provides highly customizable components for creating control planes, data planes, decentralized identity systems,
and federated data catalogs. Backed by leading companies and cloud providers, EDC gives engineers the tools they need
and federated data catalogs. Backed by leading companies and cloud providers, EDC gives developers the tools they need
to deliver innovative solutions for data exchange networks.
</p>
<p class="lead mt-5"><b>Site still under construction, please refer to <a href="https://eclipse-edc.github.io/docs">https://eclipse-edc.github.io/docs</a> for currently released documentation.</b></p>

<img height="500px" width="600px" src="images/edc.schematic.svg">
{{< /blocks/cover >}}

{{< blocks/section color="300" type="row" >}}
{{< /blocks/section >}}

{{< blocks/section color="dark" type="row" >}}
<img height="80px" width="600px" src="images/eclipse.foundation.logo.svg">
<div class="lead mt-4 text-center">
We are an Eclipse Foundation project under the <a href="https://dataspace.eclipse.org/">Dataspace Working Group</a>.
</div>
{{< /blocks/section >}}
Original file line number Diff line number Diff line change
Expand Up @@ -343,7 +343,7 @@ After a contract negotiation has been finalized, a consumer can request data ass

![Transfer Types](transfer-types.svg)

> Pay particular attention to how data is modeled. In particular, model your assets in a way that minimizes the number of contract negotiations and transfer processes that need to be created. For large data sets such as machine-learning data, this is relatively straightforward: an asset can represent each individual data set. Consumers will typically need to transfer the data once or infrequently, so the number of contract negotiations and transfer processes will remain small, typically one contract negotiation and a few transfers.
> Pay careful attention to how data is modeled. In particular, model your assets in a way that minimizes the number of contract negotiations and transfer processes that need to be created. For large data sets such as machine-learning data, this is relatively straightforward: an asset can represent each individual data set. Consumers will typically need to transfer the data once or infrequently, so the number of contract negotiations and transfer processes will remain small, typically one contract negotiation and a few transfers.
>
>Now, let's take as an example a supplier that wishes to expose parts data to their partners. Do not model each part as a separate asset, as that would require at least one contract negotiation and transfer process per part. If there are millions of parts, the number of contract negotiations and transfer processes will quickly grow out of control. Instead, have a single asset represent aggregate data, such as all parts, or a significant subset, such as a part type. Only one contract negotiation will be needed, and if the transfer process is non-finite and kept open, consumers can make multiple parts data requests (over the course of hours, days, months, etc.) without incurring additional overhead.
Expand Down
2 changes: 1 addition & 1 deletion hugo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -126,7 +126,7 @@ offlineSearch = false
prism_syntax_highlighting = false

[params.copyright]
authors = "Docsy Authors | [CC BY 4.0](https://creativecommons.org/licenses/by/4.0) | "
authors = "Eclipse Contributors | [Vector art by Freepik](https://www.freepik.com)"
from_year = 2018

# User interface configuration
Expand Down
13 changes: 13 additions & 0 deletions static/images/eclipse.foundation.logo.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading

0 comments on commit 21901b7

Please sign in to comment.