From f20f6182de95f731e67e251792bf43f574af09cd Mon Sep 17 00:00:00 2001 From: William Entriken Date: Tue, 9 Mar 2021 22:47:06 -0500 Subject: [PATCH] Update eip-1.md --- EIPS/eip-1.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/EIPS/eip-1.md b/EIPS/eip-1.md index f0ae480de8625..cfbcef5a98d3b 100644 --- a/EIPS/eip-1.md +++ b/EIPS/eip-1.md @@ -207,6 +207,10 @@ EIPs may also have a `superseded-by` header indicating that an EIP has been rend References to other EIPs should follow the format `EIP-N` where `N` is the EIP number you are referring to. Each EIP that is referenced in an EIP **MUST** be accompanied by a relative markdown link the first time it is referenced, and **MAY** be accompanied by a link on subsequent references. The link **MUST** always be done via relative paths so that the links work in this GitHub repository, forks of this repository, the main EIPs site, mirrors of the main EIP site, etc. For example, you would link to this EIP with `[EIP-1](./eip-1.md)`. +## Linking to outside sources + +EIPs **MUST NOT** link to external domains. + ## Auxiliary Files Images, diagrams and auxiliary files should be included in a subdirectory of the `assets` folder for that EIP as follows: `assets/eip-N` (where **N** is to be replaced with the EIP number). When linking to an image in the EIP, use relative links such as `../assets/eip-1/image.png`.