Nice! On Wed, Oct 7, 2026 at 8:36 AM Blain David <[email protected]> wrote: > > Good initiative, this is getting more important these days for agents, so > sites should indeed adapt to those as well. > > Funny think is I did exactly the same with our internal airflow documentation > site so our agents can easily read it as well. > > General (Internal Property) > ________________________________ > From: Sameer Mesiah <[email protected]> > Sent: Wednesday, October 7, 2026 01:01 > To: [email protected] <[email protected]> > Subject: Re: [CONTRIBUTION OPPORTUNITY] llms.txt and Markdown docs for coding > agents for Airflow site > > EXTERNAL MAIL: Indien je de afzender van deze e-mail niet kent en deze niet > vertrouwt, klik niet op een link of open geen bijlages. Bij twijfel, stuur > deze e-mail als bijlage naar [email protected]<mailto:[email protected]>. > > I understand. I don't believe I should have much issue getting a committer > to help me with all of that. In case I am not able to get a committer to > assist me, I will inform you and we can hand it to someone who is a > committer or has that assistance. > > Thanks, > Sameer. > > On Tue, 6 Oct 2026 at 23:53, Kaxil Naik <[email protected]> wrote: > > > Absolutely happy for you to take it as long as you can pair with a commiter > > because of the testing requirements I mentioned in the previous email and > > the GitHub issue. > > > > *It needs a committer, or a contributor pairing with one: testing the > > airflow-site change on staging, publishing docs and checking the live > > rollout all need committer access.* > > > > On Tue, 6 Oct 2026 at 23:39, Sameer Mesiah <[email protected]> wrote: > > > > > Hi Kaxil, > > > > > > I can pick this up if you are okay with it. > > > > > > On Tue, 6 Oct 2026 at 23:28, Kaxil Naik <[email protected]> wrote: > > > > > > > Hi all, > > > > > > > > More and more people write Dags with coding agents (Claude Code, > > Cursor, > > > > Copilot, Codex), and those agents read our docs as HTML. A provider > > guide > > > > page is about 150 KB of HTML for about 20 KB of content, and fetch > > tools > > > > often summarise it down to a paragraph, code samples included. Pydantic > > > AI, > > > > Ray, Camel, Astronomer and most of the popular sites & project publish > > an > > > > llms.txt index plus a Markdown copy of each page. We publish neither. > > > > > > > > I've opened an issue with a plan and a working proof of concept, > > starting > > > > with the Common AI provider docs: > > > > > > > > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fairflow%2Fissues%2F74376&data=05%7C02%7Cdavid.blain%40infrabel.be%7C8b25c7e9d32b4dfa939808df23fdc912%7Cb82bc314ab8e4d6fb18946f02e1f27f2%7C0%7C0%7C639269245055449115%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=rHwv1AaT41G789YkOXh7cINsukGuOc7fUn0%2FItMXHyo%3D&reserved=0<https://github.com/apache/airflow/issues/74376> > > > > > > > > It has three parts: > > > > > > > > 1. Docs build: generate page.html.md next to every page, plus llms.txt > > > and > > > > llms-full.txt, using sphinx-llm and a small extension. The proof of > > > concept > > > > builds cleanly for Common AI with no change in build time. > > > > 2. Publishing: a couple of guards in breeze so stable/ always has the > > > > Markdown copies. > > > > 3. Serving: Claude Code, Cursor, Copilot and OpenCode already send > > > "Accept: > > > > text/markdown" on every fetch. A short .htaccess rule in airflow-site > > can > > > > answer those requests with the Markdown copy, so agents get it from the > > > > URLs they already use. I tested this on airflow.staged.apache.org; > > ASF's > > > > Fastly cache keeps the HTML and Markdown answers apart. > > > > > > > > *I won't have time to build this or to review it, so it needs an owner > > > who > > > > can see it through, including reviews.* The issue lists what's done, > > > what's > > > > left, and the rollout constraints. It needs a committer, or a > > contributor > > > > pairing with one: testing the airflow-site change on staging, > > publishing > > > > docs and checking the live rollout all need committer access. > > > > > > > > This would be a high impact change, so thanks in advance for whoever > > > picks > > > > it up. > > > > > > > > Regards, > > > > Kaxil > > > > > > > > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
