-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(pages): new architecture page #9
Conversation
7d78da7
to
98be99a
Compare
@wdavidw Thank you for this redesign and new implementation of the website, much appreciated ! As noted by @rpignolet, i think that extra components (and especially airflow) should not be part of the reference architecture. Also, I don't see our proposal (the old French content) about architecture, features, etc. What do you think ? Thank you again ! |
@rpignolet wrote "Airflow is not a core component currently, we should not have it here.", he didn't mention removing it. My personal take is that extra shall be covered. I have never been in agreement with the notion of core or extra, the segregation is counter-productive. Instead, what we have are different levels of maturity, some levels not being supported because too immature, and eventually a playground. In the example of Airflow, the component is too essential to be considered optional or part of a playground. For the old French content, I would not recommend starting from there. I tried to preserve some of it on the home page and would likely rewrite it if I have time. |
To complement, the component list is not exhaustive, additional services shall enrich the page, including what is in tdp-collection-prerequisites and tdp-collection-extras. |
@wdavidw thank you again ! i suggest discussing this point during our next meeting .. |
No description provided.