> I think it would be wise to revisit all pages with code examples and check those are still valid.
Yeah - we have the whole "Example refurbish" initiative here https://cwiki.apache.org/confluence/display/AIRFLOW/Examples+Refurbish page describing things that we **should** do with our examples. I think after airflow 3.1 we can make it an ongoing effort to make a cleanup of those for 3.2. J. On Tue, Sep 16, 2025 at 3:42 AM Josef Šimánek <[email protected]> wrote: > út 16. 9. 2025 v 0:12 odesílatel Kaxil Naik <[email protected]> napsal: > > > > Hello folks, > > > > Happy weekday. > > > > We need community help to update documentation screenshots to reflect new > > features and UI improvements in Airflow 3.1.0 before the first release > > candidate (targeting later this week). > > I think it would be wise to revisit all pages with code examples and > check those are still valid. During the last few weeks, I have > collected various outdated pages not valid with Airflow 3 examples > anymore mentioning removed configurations and vice versa. Happy to > contribute to this also, I'll start contributing my findings soon. > > > Details in https://github.com/apache/airflow/issues/55521 > > > > This is a great opportunity for contributors to get familiar with Airflow > > 3.1.0's exciting new features including: > > > > 🆕 New Features to Document: > > - HITL (Human-in-the-Loop) Workflows with approval interfaces > > - Internationalization support with RTL layouts > > - Enhanced Calendar and Gantt views with filtering > > - React Plugin System for custom dashboards > > - Deadline Alerts (experimental) > > - Inference Execution with streaming APIs > > > > 📚 Core Documentation Updates: > > - UI Guide comprehensive refresh > > - DAGs, DAG Runs, Dynamic Task Mapping > > - Data-Aware Scheduling, Connections, Variables > > - And many more core concept pages > > > > What we need: > > - High-quality screenshots (1080p+) in both light and dark modes > > - Consistent browser interface and zoom levels > > - Screenshots organized per guidelines in the issue > > > > How to contribute: > > 1. Pick any unchecked item from the comprehensive checklist > > 2. Comment on the issue to avoid duplicate work > > 3. Take screenshots following the quality standards > > 4. Submit PR with updated documentation and images > > > > This is perfect for new contributors who want to explore Airflow 3.1.0's > > capabilities while making a valuable documentation contribution! > > > > Thanks, looking forward to contributions. > > > > Regards, > > Kaxil > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
