Skip to content

Conversation

@skrawcz
Copy link
Contributor

@skrawcz skrawcz commented Dec 28, 2025

This is to help move things to a better
spot with all the content under dagworks.io still.

Changes

  • add ecosystem page

How I tested this

  • locally

Notes

Checklist

  • PR has an informative and human-readable title (this will be pulled into the release notes)
  • Changes are limited to a single goal (no scope creep)
  • Code passed the pre-commit check & code is left cleaner/nicer than when first encountered.
  • Any change in functionality is tested
  • New functions are documented (with a description, list of inputs, and expected output)
  • Placeholder code is flagged / future TODOs are captured in comments
  • Project documentation has been updated if adding/changing functionality.

Copy link
Contributor

@jernejfrank jernejfrank left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, just couple of thoughts that might make sense


Articles covering Apache Hamilton use cases, design patterns, reference architectures, and best practices.

**Note**: Maintained by DAGWorks Inc.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would add the same note as above for the dataflow hub.


Video tutorials, talks, and meetup recordings about Apache Hamilton.

**Note**: Hosted by DAGWorks Inc.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here too, would add the same note as dataflow hub

3. Ensure your resource is relevant to Apache Hamilton users
4. Your resource must be properly licensed and actively maintained

### Support & Questions
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe good to add the Apache mailing list here how to reach us?

This is to help move things to a better
spot with all the content under dagworks.io still.
@skrawcz skrawcz force-pushed the stefan/add-eco-system-page branch from ca2c86f to 158d1bc Compare December 30, 2025 00:07
@skrawcz skrawcz deployed to github-pages December 30, 2025 00:07 — with GitHub Actions Active
@skrawcz skrawcz merged commit f3ff012 into main Dec 30, 2025
1 check passed
@skrawcz skrawcz deleted the stefan/add-eco-system-page branch December 30, 2025 11:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants