Expose raw .md files somewhere

[fubuloubu]

It'd be nice if the raw EIP markdown docs were hosted somewhere more accessible to an LLM to read them. Typically the suggestion is basically to expose it via adding .md to the end of whatever page that it's on (I believe most LLMs will try doing this when reading the html page)

Just kind of opening this for discussion here, it might be very interesting for developer or security tooling to leverage this site as a data source (think automated "vibe" EIP validation checks or security analysis vs. spec EIPs)

I saw that there was some consideration for a new build platform here (#9332), but this is more of a generic requirement to consider for how to site gets hosted, with new or existing build tooling

[fubuloubu]

Also, very random side thought: would be cool to use agents to augment the EIP editor role, since they are mostly concerned with well-formed-ness and adherence to the process, vs. judgement calls on content. It could also be used to automatically suggest similar EIPs, or collect the coversation from eth magicians.

IDK just thinking out loud here haha

[abcoathup]

raw EIP markdown docs were hosted somewhere more accessible
Assume we just need a copy from https://github.com/ethereum/EIPs/tree/master/EIPS

Forkcast now has an EIP directory (but doesn't keep the markdown locally that I could see): https://forkcast.org/eips (@wolovim)
Also https://eip.tools/

augment the EIP editor role

Anything to improve the ease/speed of the process for EIPs would be great. I am not an editor, I just manually assign EIP/RIP/ERC numbers, an unpaid task that is ripe for automation.

[wolovim]

is there significant upside to making it available elsewhere in addition to the raw .md from github? e.g., https://github.com/ethereum/EIPs/raw/refs/heads/master/EIPS/eip-7805.md

[fubuloubu]

is there significant upside to making it available elsewhere in addition to the raw .md from github? e.g., https://github.com/ethereum/EIPs/raw/refs/heads/master/EIPS/eip-7805.md

I have seem some autodoc plugins for particular docs building frameworks add links to the raw content e.g. https://raw.githubusercontent.com/ethereum/EIPs/refs/heads/master/EIPS/eip-7805.md

For example on https://shibuya.lepture.com/install:

---

I have no idea what "best practice" is (nor if there is one), but this suggestion is more about efficient auto-discovery by LLMs vs. just knowing you can give them a link (which anyone competent with github knows about the raw content links which they can give)

[fubuloubu]

Okay, here's a similar issue:

I have no idea why this would fail to fetch. That link works fine for me. Does the domain server block cloud-based queries?