Maintenance updates docs (#176)

* Revisit link checker, update broken link

* Update api3-docs name

* Update ignore files

* Avoid search suggestions from ignored files

* Revert "Update ignore files"

This reverts commit 56e65d6.

* Avoid vitepress-docs reference

Author: Siegrift

.vscode/settings.json

@@ -83,6 +83,5 @@
   ],
   "editor.defaultFormatter": "esbenp.prettier-vscode",
   "editor.formatOnSave": true,
-  "search.useIgnoreFiles": false,
   "editor.rulers": [80]
 }

docs/.vitepress/config.js

@@ -72,7 +72,7 @@ export default {
     },
     siteTitle: 'Documentation',
     socialLinks: [
-      { icon: 'github', link: 'https://github.com/api3dao/oev-docs' },
+      { icon: 'github', link: 'https://github.com/api3dao/api3-docs' },
       {
         icon: 'discord',
         link: 'https://discord.gg/api3dao',

docs/dapps/integration/security-considerations.md

@@ -24,7 +24,7 @@ Like all smart contracts, Api3ReaderProxyV1 carries this inherent risk.
 
 We propose three methods to assess the smart contract risk.
 You can refer to the related [audit reports.](https://github.com/api3dao/contracts?tab=readme-ov-file#security)
-A more practical approach is to refer to [our historical TVS](https://defillama.com/oracles/API3) to understand the _battle-testedness_ of our data feeds.
+A more practical approach is to refer to [our historical TVS](https://defillama.com/oracles/Api3) to understand the _battle-testedness_ of our data feeds.
 Additionally, you are welcome to review the contracts behind [Api3ReaderProxyV1](/dapps/integration/contract-integration.md#api3readerproxyv1), specifically [Api3ServerV1](https://github.com/api3dao/contracts/blob/main/contracts/api3-server-v1/Api3ServerV1.sol) and [Api3ServerV1OevExtension](https://github.com/api3dao/contracts/blob/main/contracts/api3-server-v1/Api3ServerV1OevExtension.sol).
 Our [contract developer docs](https://github.com/api3dao/contracts/tree/main/docs) provide additional context for understanding the design decisions behind these contracts.
 

firebase-deploy.sh

@@ -19,8 +19,8 @@ cd docs/.vitepress/dist
 # if you are deploying to a custom domain
 # echo 'www.example.com' > CNAME
 
-# Use this section if you want to push to a depoyment branch.
-# api3dao/vitepress-docs uses the main branch as default.
+# Use this section if you want to push to a deployment branch.
+# api3dao/api3-docs uses the main branch as default.
 # git init must start with a main branch so firebase-pages will
 # "hang" off of it.
 # git init --initial-branch=main
@@ -32,7 +32,7 @@ cd docs/.vitepress/dist
 
 # If you are deploying to https://<USERNAME>.github.io/<REPO>
 # NEVER push to main, use main:firebase-pages.
-# git push -f git@github.com:wkande/vitepress-docs.git main:firebase-pages
+# git push -f git@github.com:wkande/api3-docs.git main:firebase-pages
 
 cd -
 

libs/link-validator-ignore.json

@@ -1,9 +1,8 @@
 [
   "https://basescan.org",
-  "https://defillama.com/oracles/API3",
+  "https://defillama.com/oracles/Api3",
   "https://etherscan.io",
-  "https://github.com/api3dao/oev-docs",
-  "https://github.com/api3dao/oev-v1-compound-bot",
+  "https://medium.com/api3/oracle-extractable-value-oev-13c1b6d53c5b",
   "https://oev.rpc.api3.org",
   "https://orbitlending.io/",
   "https://www.coinbase.com/blog/introducing-the-coinbase-price-oracle",

package.json

@@ -1,5 +1,5 @@
 {
-  "name": "oev-docs",
+  "name": "api3-docs",
   "version": "1.0.0",
   "main": "index.js",
   "license": "MIT",