chore: update welcome page

Author: 0xzeriph

sites/ef/docs/interop/chain-specific-addresses.md

@@ -33,4 +33,4 @@ To bring these standards to life we collaborated with Unruggable on an [onchain
 
 We also developed a dedicated typescript package for easy integration of interoperable addresses, `@wonderland/interop-addresses`
 
-> 📌 To learn more, feel free to check our [documentation](https://docs.interop.wonderland.xyz/addresses), explore the [landing page](https://interopaddress.com/) and interact with the [demo app](https://interop.wonderland.xyz/addresses).
+> 📌 To learn more, feel free to check our [documentation](https://docs.interop.wonderland.xyz/addresses), explore the [landing page](https://interopaddress.com/) and interact with the [demo app](https://interop.wonderland.xyz/addresses).

sites/ef/docs/interop/cross-chain-token-standards.md

@@ -99,4 +99,4 @@ Finally, although custom verification mechanisms offer benefits, default configu
 - [Axelar Latency](https://docs.axelar.dev/learn/txduration/)
 - [Wormhole Consistency Levels](https://wormhole.com/docs/products/reference/consistency-levels/)
 - [LayerZero Scan](https://layerzeroscan.com/)
-- [Chainlink CCIP Directory](https://docs.chain.link/ccip/directory/mainnet)
+- [Chainlink CCIP Directory](https://docs.chain.link/ccip/directory/mainnet)

sites/ef/docs/interop/deep-dives.md

@@ -6,4 +6,4 @@ By the end of these deep dives, you should be able to answer:
 
 - Why did [`ERC-5792`](https://eips.ethereum.org/EIPS/eip-5792) see almost no adoption despite solving a real problem?
 - What stops bridges from adopting a shared messaging standard like [`ERC-7786`](https://eips.ethereum.org/EIPS/eip-7786)?
-- Why did cross-chain token standards attract early interest but fail to unify the ecosystem?
+- Why did cross-chain token standards attract early interest but fail to unify the ecosystem?

sites/ef/docs/interop/erc-5792-eip-7702.md

@@ -67,4 +67,4 @@ These lessons are relevant to the decisions the EF is making today, as it looks
 - The OIF requires adoption by multiple stakeholders (interop providers, solvers, wallets, apps); we can expect that will take time, and will not happen organically (i.e. without concerted effort).
 - The OIF is also a “substitute” for existing interop providers, and does not provide a “step change” in crosschain functionality. We can therefore expect stickiness to preclude adoption by some wallets and apps who have already integrated existing providers.
 - [Frame Transactions](https://eips.ethereum.org/EIPS/eip-8141) introduce another flexible gadget for post-quantum readiness, and to enable account abstraction; this may encounter some of the same challenges as ERC-7702, if too many implementation details are left up to the tooling, wallet & app layer.
-- As we are working with teams across the ecosystem, we need to bear in mind that both wallets and apps are increasingly verticalised, and we should proactively engage with the infrastructure providers building embedded wallets to keep them in the loop.
+- As we are working with teams across the ecosystem, we need to bear in mind that both wallets and apps are increasingly verticalised, and we should proactively engage with the infrastructure providers building embedded wallets to keep them in the loop.

sites/ef/docs/interop/glossary.md

@@ -11,4 +11,4 @@
 | **Intent** | What the user wants to do, expressed as "send X tokens from chain A to chain B" |
 | **Solver** | An actor that fulfills intents. They compete to offer the best price |
 | **Open Intents Framework (OIF)** | Modular infrastructure for intent layers: origination, fulfillment, settlement and rebalancing. Collaborative effort between the EF, Hyperlane, OpenZeppelin, Wonderland and others |
-| **Interoperable Address** | An address that carries its chain info with it, following [ERC-7930](https://eips.ethereum.org/EIPS/eip-7930) |
+| **Interoperable Address** | An address that carries its chain info with it, following [ERC-7930](https://eips.ethereum.org/EIPS/eip-7930) |

sites/ef/docs/interop/intro-interop.md

@@ -12,4 +12,4 @@ In this context, the Open Intents [initiative emerged](https://blog.ethereum.org
 
 ## What this handbook covers
 
-The handbook reviews Wonderland's Interoperability focus areas, summarising the key problems we have been working on, linking to documentation to learn more and start building. Our work has involved research efforts to better understand the adoption of standards focused on interoperability and user experience, the outputs of which are also included.
+The handbook reviews Wonderland's Interoperability focus areas, summarising the key problems we have been working on, linking to documentation to learn more and start building. Our work has involved research efforts to better understand the adoption of standards focused on interoperability and user experience, the outputs of which are also included.

sites/ef/docs/intro/welcome.md

@@ -4,13 +4,19 @@ title: Welcome
 sidebar_label: Welcome
 ---
 
-# Welcome
+# Welcome to the Ethereum Foundation Handbook
 
-This is your documentation site. Start by editing this page and adding your content.
+Whether you want to understand how interoperability works, build with the tooling we've developed, figure out why some standards take off and others don't, or are curious about privacy on Ethereum, this guide is for you.
 
-## Quick Start
+Ethereum is a decentralized network where anyone can build applications and move value without intermediaries. Interoperability and privacy are problems we're working to solve. This handbook helps you get there.
 
-1. Edit this file to add your content
-2. Update `sidebars.ts` to organize your navigation
-3. Add more pages in the `docs/` directory
-4. Customize `docusaurus.config.ts` with your project details 
+You'll find:
+
+- An overview of interoperability on Ethereum
+- Standards and tooling for chain-specific addresses and cross-chain operations
+- Research into why some EIPs succeed and others don't
+- A privacy toolkit for wallets, covering trust assumptions and privacy pools
+
+This is a living document. It grows as the work evolves.
+
+Welcome aboard 🛠️

sites/ef/docusaurus.config.ts

@@ -36,6 +36,8 @@ const localConfig: Config = {
           // Please change this to your repo.
           // Remove this to remove the 'edit this page' links.
           editUrl: "https://github.com/defi-wonderland/handbook/tree/main/sites/ef",
+          showLastUpdateTime: true,
+          showLastUpdateAuthor: true,
           remarkPlugins: [remarkMath],
           rehypePlugins: [rehypeKatex],
         },

sites/ef/src/css/local.css

@@ -84,10 +84,7 @@
   .menu__link[href^="/docs/interop"]::before,
 .theme-doc-sidebar-item-category
   .menu__list-item-collapsible
-  .menu__link[href="/docs/interop/"]::before,
-.theme-doc-sidebar-item-category
-  .menu__list-item-collapsible
-  .menu__link[href="/docs/interop/coming-soon"]::before {
+  .menu__link[href="/docs/interop/"]::before {
   content: "";
   background-image: url("/img/icons/cube-transparent.svg");
   background-size: 1rem 1rem;
@@ -218,10 +215,7 @@
   .menu__link[href^="/docs/interop"],
 .theme-doc-sidebar-item-category
   .menu__list-item-collapsible
-  .menu__link[href="/docs/interop/"],
-.theme-doc-sidebar-item-category
-  .menu__list-item-collapsible
-  .menu__link[href="/docs/interop/coming-soon"] {
+  .menu__link[href="/docs/interop/"] {
   font-family:
     "Inter",
     system-ui,