push-protocol · corlard3y · Jan 8, 2024 · Jan 8, 2024 · Jan 8, 2024 · Jan 8, 2024
diff --git a/blog/2021-03-31-announcing-the-epns-push-token-generation-event/index.md b/blog/2021-03-31-announcing-the-epns-push-token-generation-event/index.md
@@ -18,7 +18,7 @@ import { ImageText } from '@site/src/css/SharedStyling';
 
 <!--truncate-->
 
-> Note: EPNS has been rebranded to Push. The latest token design is available at [https://docs.push.org/hub/pusheconomics/push-token-economics](https://docs.push.org/hub/pusheconomics/push-token-economics)
+> Note: EPNS has been rebranded to Push. The latest token design is available at [https://push.org/docs/tokenomics/deepdive/$push/](https://push.org/docs/tokenomics/deepdive/$push/)
 
 Since we announced our seed round last fall, we’ve been heads down continuing to build the world’s first decentralized notification protocol for Ethereum. We’re fast approaching mainnet launch, so we’re taking the time today to explain to the community what they can expect for the $PUSH token generation event (TGE).
 

diff --git a/blog/2021-03-31-push-token-economics/index.md b/blog/2021-03-31-push-token-economics/index.md
@@ -18,7 +18,7 @@ import { ImageText } from '@site/src/css/SharedStyling';
 
 <!--truncate-->
 
-> **Update:** Push Protocol (Previously EPNS) and $PUSH is evolving, The evolved version of Pusheconomics can be found here: [https://docs.push.org/pusheconomics/push-token-economics](https://docs.push.org/pusheconomics/push-token-economics)
+> **Update:** Push Protocol (Previously EPNS) and $PUSH is evolving, The evolved version of Pusheconomics can be found here: [https://push.org/docs/tokenomics/deepdive/$push/](https://push.org/docs/tokenomics/deepdive/$push/)
 
 Ethereum Push Notification Service (EPNS) is a protocol for decentralized notifications on the Ethereum blockchain. EPNS enables applications and users to create and subscribe to notification channels, enabling blockchain-native communication between apps and users. The Web3 ecosystem today communicates through channels like email, Medium, Twitter, Discord, WeChat, and more. For rapidly-evolving use cases like DeFi, these forms of communication struggle to scale. EPNS protocol lets applications send push notifications to users regarding updates, account information, product drops, and more. Users can also set up custom notifications in response to on-chain events to better monitor investments, transactions, app security, protocol performance, and more.
 

diff --git a/blog/2022-10-27-push-monthly-blocks-september/index.md b/blog/2022-10-27-push-monthly-blocks-september/index.md
@@ -23,7 +23,7 @@ Hi <b>Push</b> frens!✨ This one is a very special Monthly Blocks edition as it
 Let’s jump into the good stuff immediately. The development team have been making strides in all areas in preparation for many good news to come very soon!
 
 - Wallet-to-Wallet integration tests & design in progress
-- Developer docs for mono-repo SDK and SNS have been added to [Push Documentation](https://docs.push.org/) hub along with a starter kit for Devs to build on top of Push SDK
+- Developer docs for mono-repo SDK and SNS have been added to [Push Documentation](https://push.org/docs) hub along with a starter kit for Devs to build on top of Push SDK
 - UI enhancements to the Push dApp is in progress and soon to be ready!
 - Configuration of push nodes to receive and process w2w based notifications in progress.
 - Optimization and standardization of Push Node is in the works as well.

diff --git a/blog/2022-12-21-deeper-look-into-push-chat/index.md b/blog/2022-12-21-deeper-look-into-push-chat/index.md
@@ -52,7 +52,7 @@ Once the network becomes fully decentralized, Push Nodes will be incentivized to
 
 <i>Read about Push Economics here:</i><br/><br/>
 
-[Push Token Economics](https://docs.push.org/hub/pusheconomics/push-token-economics?source=post_page-----90fdea8d9e8e--------------------------------)
+[Push Token Economics](https://push.org/docs/tokenomics/deepdive/$push/)
 
 
 ## How Does a User Send a Message Using Their Account Address?

diff --git a/blog/2023-02-15-building-a-better-ux-in-bnb/index.md b/blog/2023-02-15-building-a-better-ux-in-bnb/index.md
@@ -22,9 +22,9 @@ We’re extremely excited to announce Push has officially added BNB Chain to its
 With this announcement, we’re excited to introduce our BNB launch Collaborators who are collaborating with Push on various use cases to bring web3 native notification and messaging to users across the BNB ecosystem.
 
 ### Push and BNB: Decentralized communication to power web3 UX
-Using Push, BNB dapp developers can begin adding notification services to their dapps, building custom communication channels, and enabling wallet-to-wallet communication for users (check out [this guide](https://docs.push.org/developers/developer-guides/create-your-notif-channel/enabling-channel-on-other-chains/bnb-chain-binance-channel-setup) for getting started). For end-users, this means enhanced capacity to stay updated on critical information relevant to their favorite dapps.
+Using Push, BNB dapp developers can begin adding notification services to their dapps, building custom communication channels, and enabling wallet-to-wallet communication for users (check out [this guide](https://push.org/docs/notifications/tutorials/enabling-channel-on-other-chains/) for getting started). For end-users, this means enhanced capacity to stay updated on critical information relevant to their favorite dapps.
 
-The BNB notification ecosystem will be available through the primary Push Protocol app: [app.push.org](http://app.push.org/). For users, you can follow this [user guide](https://docs.push.org/users/basics/how-to-start-using-push-notifications) to begin opting-in to channels.
+The BNB notification ecosystem will be available through the primary Push Protocol app: [app.push.org](http://app.push.org/). For users, you can follow this [user guide](https://push.org/docs/notifications/s) to begin opting-in to channels.
 
 This integration is a major step forward in Push’s mission to provide seamless and decentralized web3 communication and we are thrilled to have eight new frens from BNB joining our mission.
 

diff --git a/blog/2023-02-21-getting-started-with-push-sdk/index.md b/blog/2023-02-21-getting-started-with-push-sdk/index.md
@@ -289,7 +289,7 @@ function MydApp() {
 
 That’s it! You now know how to use the components of the <b>@pushprotocol/uiweb</b> API to add push notification functionality to your application.
 
-We’ll cover the other parts of the SDK in the coming posts. More reference material is available in the [Push Protocol SDK documentation](https://docs.push.org/developers/developer-tooling/push-sdk).
+We’ll cover the other parts of the SDK in the coming posts. More reference material is available in the [Push Protocol SDK documentation](https://push.org/docs/).
 
 In addition, try out the [Push SDK sandbox](https://github.com/ethereum-push-notification-service/push-sdk-sandbox).
 

diff --git a/blog/2023-03-01-push-sdk/index.md b/blog/2023-03-01-push-sdk/index.md
@@ -151,7 +151,7 @@ That’s it! You now know how to use the main features of the Push Protocol Sock
 
 We’ll cover other parts of the Push SDK in coming posts so stay tuned!
 
-- [Push Protocol SDK documentation here](https://docs.push.org/developers/developer-tooling/push-sdk/sdk-packages-details/pushprotocol-socket) — if you’d like more reference material to chew on.
+- [Push Protocol SDK documentation here](https://push.org/docs/) — if you’d like more reference material to chew on.
 - [Push SDK on GitHub](https://github.com/ethereum-push-notification-service/push-sdk)
 - [Our Discord](https://discord.gg/pushprotocol) — we’ve got devs ready to give your project whatever support and consultation you need.
 - [Push developer docs](/docs/ "Push developer docs") to get started on building right away!

diff --git a/blog/2023-03-14-liquidity-rewards-v2/index.md b/blog/2023-03-14-liquidity-rewards-v2/index.md
@@ -26,7 +26,7 @@ In this article, we will discuss the extension and improvements made to the Push
 
 With V2 of Push Protocol and the introduction of fee pool staking, $PUSH stakers will now be able to claim fee pool rewards in addition to staking rewards for providing liquidity.
 
-You can find a more detailed breakdown regarding Push Tokenomics and the Push Fee Pool <a href="https://docs.push.org/hub/pusheconomics/push-token-economics#push-fee-pool"><b>here</b></a>.
+You can find a more detailed breakdown regarding Push Tokenomics and the Push Fee Pool <a href="https://push.org/docs/tokenomics/deepdive/$push/#push-fee-pool"><b>here</b></a>.
 
 This new strategy will improve liquidity rewards at levels above the ones observed during the first iteration of the program.
 

diff --git a/blog/2023-03-24-recreating-web2-communication-in-in-web3/index.md b/blog/2023-03-24-recreating-web2-communication-in-in-web3/index.md
@@ -68,7 +68,7 @@ Once the verification transaction is approved on the Binance Chain, the alias ad
 
 It’s worth noting that delegate addresses are also useful for ensuring notifications can be sent out from wallets other than the one that created the channel. The channel creator is the only person able to add or remove delegates at any time. The communication channels’ chat feature also allows users to whitelist addresses, block addresses, and prevent spam messages. These features help ensure that communication channels remain secure and relevant to their subscribers.
 
-To learn more about Channel Aliases and Delegates, you can refer to [Push documentation here](https://docs.push.org/developers/concepts/create-your-notif-channel/what-is-a-channel-alias).
+To learn more about Channel Aliases and Delegates, you can refer to [Push documentation here](https://push.org/docs/notifications/concepts/push-notifications-for-web3/#what-is-a-channel-alias).
 
 ## Conclusion
 Communication channels play a crucial role in enabling decentralized applications and services to communicate with their users. Push Protocol offers a chain-agnostic solution that enables communication across ecosystems and networks. Following the straightforward steps outlined in this section, you can easily set up a communication channel on one of the compatible chains and communicate seamlessly.

diff --git a/blog/2023-04-13-push-at-ethglobal-tokyo/index.md b/blog/2023-04-13-push-at-ethglobal-tokyo/index.md
@@ -43,7 +43,7 @@ Push は、オープンなコミュニケーションのミドルウェアであ
 
 さらに、チャンネルのオーナーは、通知送信権限を他の任意のウォレットアドレスに委任することもできます。これにより、選択されたウォレットアドレスがチャンネルを代表して通知を送信できます。ただし、チャンネルのオーナーはいつでも委任を取り消すことができます。
 
-👉 https://docs.push.org/developers/developer-tooling/push-sdk
+👉 https://push.org/docs/
 
 ### Push Chat
 
@@ -58,7 +58,7 @@ Push Chat SDKの統合は非常に簡単で、以下の機能に分かれます
 - 特定のチャットの個々のメッセージの取得
 - チャットへの返信
 
-👉 https://docs.push.org/developers/developer-guides/integrating-push-chat
+👉 https://push.org/docs/chat/ui-components/integrate-push-chat/
 
 ### Push Group Chat
 
@@ -166,4 +166,4 @@ IPFSに何かをアップロードしたとき、またはバリデーターが
 
 Push ChatとPush Notificationsの仕組みに興味がある場合は、是非[discordチャンネル](https://discord.com/invite/pushprotocol)に参加し、あなたが何をビルドしているのかを教えてください。Pushチームは、あなたがそれを実現するために必要なすべての開発者リソースを提供できます。
 
-すぐにビルドを開始するには、<a href="https://docs.push.org/developers"><b>こちら</b></a>のPush開発者ドキュメントにアクセスしてください。
+すぐにビルドを開始するには、<a href="https://push.org/docs/"><b>こちら</b></a>のPush開発者ドキュメントにアクセスしてください。
diff --git a/blog/2023-04-19-understanding-delivery-nodes/index.md b/blog/2023-04-19-understanding-delivery-nodes/index.md
@@ -100,5 +100,5 @@ With all these services working together, messages can be sent from one wallet t
 
 To begin building with Push Delivery Nodes, read up on our documentation specifically for it here:
 
-👉👉👉https://docs.push.org/developers/developer-guides/receiving-notifications/receiving-via-delivery-node
+👉👉👉https://push.org/docs/notifications/tutorials/integrate-notifications-via-delivery-node/
 
diff --git a/blog/2023-05-25-realtime-analytics-push-alchemy/index.md b/blog/2023-05-25-realtime-analytics-push-alchemy/index.md
@@ -76,7 +76,7 @@ const alchemyApiKey = "your_alchemy_api_key";
 const provider = new ethers.providers.AlchemyProvider("mainnet", alchemyApiKey);
 ```
 
-Now, we can initialize Push Protocol. Follow the [official documentation](https://docs.push.org/developers) for more details. The official PUSH-SDK packages are also available [here](https://www.npmjs.com/~pushprotocol).
+Now, we can initialize Push Protocol. Follow the [official documentation](https://push.org/docs/) for more details. The official PUSH-SDK packages are also available [here](https://www.npmjs.com/~pushprotocol).
 
 Here is a sample workflow to integrate Push Protocol:
 

diff --git a/blog/2023-05-31-push-v2/index.md b/blog/2023-05-31-push-v2/index.md
@@ -30,7 +30,7 @@ Push Protocol is thrilled to announce the successful completion of the security
 
 ## What’s next?
 - Push Protocol v2 tentative launch date is late June, 2023 along with [yield farming v2 for fee pool and Uniswap v2 LP pool](https://snapshot.org/?utm_source=Twitter&utm_medium=Post&utm_campaign=RockstarsOfPushWeek17%2618Post#/pushdao.eth/proposal/0x54092053eff30c3c304e45b575881945192e710bc9b3914bfe1d1eadcda3f114).
-- This marks the beginning of [protocol fees](https://docs.push.org/hub/pusheconomics/push-token-economics#push-fee-pool) incentivizing and rewarding token holders and crypto wallets.
+- This marks the beginning of [protocol fees](https://push.org/docs/tokenomics/deepdive/$push/#push-fee-pool) incentivizing and rewarding token holders and crypto wallets.
 - Push v2 has cleared Chainsafe audit. However, owing to the core and critical features of v2, the team has decided to launch it after 4 weeks.
 - This gives team enough time to run white hat contests among major platform(s) to ensure v2 is battle tested.
 - Prior to the tentative launch in late June, 2023, there will be an open, incentivized bug bounty program available to the community. More information coming soon.
@@ -47,15 +47,15 @@ In simple terms, this means PUSH holders can now stake and earn PUSH rewards dir
 ### What’s the Fee Pool?
 Before delving into how the Core v2 staking works, let’s take a step back to quickly recap the concept of the Protocol Fee Pool.
 
-Protocol Feel Pool was introduced in the Version 1.5 of Push smart contracts. Fee Pool is a term used to signify small fees charged by the protocol actions like channel creation, channel reactivation, channel detail modification. They don’t affect users and for users, everything is always feeless, with the exception of few features for super users as [outlined here](https://docs.push.org/hub/pusheconomics/push-token-economics#push-fee-pool).
+Protocol Feel Pool was introduced in the Version 1.5 of Push smart contracts. Fee Pool is a term used to signify small fees charged by the protocol actions like channel creation, channel reactivation, channel detail modification. They don’t affect users and for users, everything is always feeless, with the exception of few features for super users as [outlined here](https://push.org/docs/tokenomics/deepdive/$push/#push-fee-pool).
 
 In other words, for every crucial transaction on the Core contract, it takes a small fee amount and stores it in what we call a <b>Push Fee Pool</b>.
 
 The protocol fee is currently set to be equal to <b>10 PUSH tokens</b>. This value, however, can be changed by the community later using on-chain governance.
 
 <blockquote><i><b>Note:</b> This is not an additional fee that is charged on top of channel creation fees. Instead, the protocol fee is simply deducted from the same amount that a channel creator chooses to stake in the protocol.
 For example, if you chose to stake 50 PUSH during channel creation, 10 of those 50 PUSH tokens go into Protocol Fee Pool, while the remaining goes into Channel Pool Funds that are claimable by channel owners anytime they choose to deactivate their channel.*
-Read more about Fee Pool and how it operates over here: https://docs.push.org/hub/pusheconomics/push-token-economics#push-fee-pool.</i></blockquote>
+Read more about Fee Pool and how it operates over here: https://push.org/docs/tokenomics/deepdive/$push/#push-fee-pool.</i></blockquote>
 
 ## The Fee Pool Staking
 With the introduction of [version 1.5 of the core contract](https://medium.com/push-protocol/introducing-push-protocol-v1-5-80eb39b55424), we laid the foundation for the fee pool and the vision of incentivizing PUSH holders. However, the current version represents a substantial leap towards realizing this vision.

diff --git a/...otifications/04-tutorials/07-Tutorial-Integrate-Notifications-Delivery-Node.mdx b/...otifications/04-tutorials/07-Tutorial-Integrate-Notifications-Delivery-Node.mdx
@@ -16,12 +16,7 @@ Do check out [integrating notifications section](/docs/notifications/build/integ
 
 ## Overview
 
-Push delivery Nodes is a Whitelabel solution to enable any app, either mobile, desktop, or extension, to allow Web3 push notifications to their app.
-
-<head>
-  <title>Integrate Notifications via Delivery Node | Tutorial | Push Notifications |
-    Push Documentation</title>
-</head>
+# Push delivery Nodes is a Whitelabel solution to enable any app, either mobile, desktop, or extension, to allow Web3 push notifications to their app.
 
 import ReactPlayer from "react-player";
 

diff --git a/docs/notifications/04-tutorials/08-Tutorial-Integrate-Notifications-AWS-SNS.mdx b/docs/notifications/04-tutorials/08-Tutorial-Integrate-Notifications-AWS-SNS.mdx
@@ -16,11 +16,6 @@ Notifications via AWS SNS is more of a Web2.5 approach than Web3. Do check out [
 
 SNS module for Push delivery node allows any developer to receive notifications, chats, or any other form of web3 communication directly to the platform they are building with the help of webhooks.
 
-<head>
-  <title>Integrate Notifications via AWS SNS | Tutorial | Push Notifications | Push
-    Documentation</title>
-</head>
-
 Hosted SNS Module is a mid-level solution that eliminates all the heavy load of running a node or syncing information and gives you webhooks that you implement to start receiving notifications, chats, or any other web3 communication in your software.
 
 ## Integration process

diff --git a/src/pages/faq.tsx b/src/pages/faq.tsx
@@ -244,7 +244,7 @@ const Notifs = [
         <Span>
           Additionally, wallets should check out{' '}
           <AMod
-            href="https://docs.push.org/hub/pusheconomics/push-token-economics"
+            href="https://push.org/docs/tokenomics/deepdive/$push/"
             target={'_blank'}
           >
             fee pool of Push which re-imagines and incentivises their contribution
@@ -649,7 +649,7 @@ const Token = [
         <Span>
           Read in detail 👉{' '}
           <AMod
-            href="https://docs.push.org/hub/pusheconomics"
+            href="https://push.org/docs/tokenomics/"
             target={'_blank'}
           >
             Pusheconomics

diff --git a/src/segments/Footer.tsx b/src/segments/Footer.tsx
@@ -173,7 +173,7 @@ function Footer() {
                   </FooterAnchorSecondary>
 
                   <FooterAnchorSecondary
-                    href="https://docs.push.org/governance"
+                    href="https://push.org/docs/dao"
                     title={t('footer.links-section.governance-column.guides-link')}
                     target="_blank"
                   >
Original file line number	Diff line number	Diff line change
Expand Up		@@ -100,5 +100,5 @@ With all these services working together, messages can be sent from one wallet t

		To begin building with Push Delivery Nodes, read up on our documentation specifically for it here:

		👉👉👉https://docs.push.org/developers/developer-guides/receiving-notifications/receiving-via-delivery-node
		👉👉👉https://push.org/docs/notifications/tutorials/integrate-notifications-via-delivery-node/