Page MenuHomeElementl

website top-level headlines update
ClosedPublic

Authored by sandyryza on Feb 10 2021, 8:54 PM.

Details

Summary

We've gotten feedback from a few different directions that it's difficult to understand what Dagster is/does from our top-level messaging. Here's one example:

I guess the description under that header -- "Pipelines are built from ... data processing and infrastructure components. Dagster's web interface lets anyone inspect these objects and discover how to use them," -- is kind of unclear to me as I don't really understand what these components are? I think I'm confused on how you would have a component that is used to build the pipeline and process data, but then can be used for something else, which is what the last sentence there is kind of implying to me. Like, wouldn't "how you use them" just be to process data?

On a re-read, I definitely sympathize. Here's an attempt to update the three headlines on our website to be more specific.

In particular, I sought to:

  • Specifically talk about "pipelines" of "computations" rather than "components".
  • Connect each of the headlines to one of (my view of) our core value props: (1) orchestration of diverse compute, (2) testability, (3) linking assets with compute.

Maybe this is already slated for bulldozing as part of a larger messaging push?

image.png (1×2 px, 311 KB)

Test Plan

manual inspection

Diff Detail

Branch
tlm (branched from master)
Lint
No Lint Coverage
Unit
No Test Coverage
Build Status
Buildable 27208
Build 55046: arc lint + arc unit

Event Timeline

sandyryza created this revision.
sandyryza retitled this revision from top-level-messaging to website top-level headlines update.Feb 10 2021, 9:08 PM
sandyryza edited the summary of this revision. (Show Details)
sandyryza added reviewers: schrockn, catherinewu, max.
sandyryza edited the summary of this revision. (Show Details)
pages/index.tsx
58

The other changes sound good to me. I'm not sure about this line...

I think "[typed] data flow between reusable, logical components" is nice to keep.

Maybe "Locally develop pipelines in-process, then flexibly deploy via our Kubernetes integration or on your custom infrastructure"

pages/index.tsx
58

"Locally develop pipelines in-process, then flexibly deploy via our Kubernetes integration or on your custom infrastructure" - I love it. Will replace.

My interpretation of the the feedback we got was that "data flow between reusable, logical components" is too abstract to convey useful information. I also think we should downplay reusability in our core messaging - in most cases, writing reusable solids is not the right pattern.

"My interpretation of the the feedback we got was that "data flow between reusable, logical components" is too abstract to convey useful information. I also think we should downplay reusability in our core messaging - in most cases, writing reusable solids is not the right pattern."

I agree with this. I think we do have a reusability message but it is subtle (resources, shared infra and libraries) and I agree the reusable solid thing doesn't resonate at the top-level

This revision is now accepted and ready to land.Feb 19 2021, 8:09 PM