Merge pull request #13306 from meteor/feature/prepare-v3-docs

Prepare V3 docs to the domain change

CONTRIBUTING.md

@@ -72,7 +72,7 @@ Current Core Team:
 
 ### Tracking project work
 
-Right now, the best place to track the work being done on Meteor is to take a look at the latest release milestone [here](https://github.com/meteor/meteor/milestones).  Also, the [Meteor Roadmap](https://docs.meteor.com/roadmap.html) contains high-level information on the current priorities of the project.
+Right now, the best place to track the work being done on Meteor is to take a look at the latest release milestone [here](https://github.com/meteor/meteor/milestones).  Also, the [Meteor Roadmap](https://docs.meteor.com/about/roadmap.html) contains high-level information on the current priorities of the project.
 
 ## Reporting a bug in Meteor
 <a name="reporting-bug"></a>
@@ -134,7 +134,7 @@ for more details on proposing changes to core code.
 Feature requests are tracked in the [Discussions](https://github.com/meteor/meteor/discussions).
 
 Meteor is a big project with [many sub-projects](https://github.com/meteor/meteor/tree/devel/packages).
-Community is welcome to help in all the sub-projects. We use our [roadmap](https://docs.meteor.com/roadmap.html) to communicate the high-level features we're currently prioritizing.
+Community is welcome to help in all the sub-projects. We use our [roadmap](https://docs.meteor.com/about/roadmap.html) to communicate the high-level features we're currently prioritizing.
 
 Every additional feature adds a maintenance cost in addition to its value. This
 cost starts with the work of writing the feature or reviewing a community pull
@@ -207,7 +207,7 @@ For more information about how to work with Meteor core, take a look at the [Dev
 
 ### Proposing your change
 
-You'll have the best chance of getting a change into core if you can build consensus in the community for it or if it is listed in the [roadmap](https://docs.meteor.com/roadmap.html). Start by creating a well specified Discussion [here](https://github.com/meteor/meteor/discussions).
+You'll have the best chance of getting a change into core if you can build consensus in the community for it or if it is listed in the [roadmap](https://docs.meteor.com/about/roadmap.html). Start by creating a well specified Discussion [here](https://github.com/meteor/meteor/discussions).
 
 Help drive discussion and advocate for your feature on the Github ticket (and perhaps the forums). The higher the demand for the feature and the greater the clarity of it's specification will determine the likelihood of a core contributor prioritizing your feature by flagging it with the `ready` label.
 

History.md

@@ -2,4 +2,4 @@
 
 This content was moved to [history.md](./docs/history.md).
 
-Previously the changelog was available to be edited here but it was always published in [https://docs.meteor.com/changelog.html](https://docs.meteor.com/changelog.html).
+Previously the changelog was available to be edited here but it was always published in [https://docs.meteor.com/history.html](https://docs.meteor.com/history.html).

README.md

@@ -107,4 +107,4 @@ To uninstall Meteor:
     rm -rf ~/.meteor 
     sudo rm /usr/local/bin/meteor
     ```
-To find more information about installation, [read here](https://docs.meteor.com/install.html#uninstall).
+To find more information about installation, [read here](https://docs.meteor.com/about/install.html#uninstall).

v3-docs/docs/.vitepress/theme/Layout.vue

@@ -1,4 +1,5 @@
 <script setup lang="ts">
+import NotFound from './NotFound.vue'
 import { useData, useRouter } from 'vitepress'
 import DefaultTheme from 'vitepress/theme'
 import { nextTick, provide } from 'vue'
@@ -50,7 +51,11 @@ provide('toggle-appearance', async ({ clientX: x, clientY: y }: MouseEvent) => {
 </script>
 
 <template>
-  <DefaultTheme.Layout />
+  <DefaultTheme.Layout >
+    <template #not-found>
+      <NotFound />
+    </template>
+  </DefaultTheme.Layout>
 </template>
 
 <style>

v3-docs/docs/.vitepress/theme/NotFound.vue

@@ -0,0 +1,96 @@
+<script setup>
+import { useRouter } from "vitepress";
+import { ref, onMounted } from "vue";
+
+// Dynamically construct the redirect URL based on the current path
+const router = useRouter();
+const redirectUrl = ref("");
+
+onMounted(() => {
+  redirectUrl.value = `https://v2-docs.meteor.com${router.route.path}`;
+});
+</script>
+
+<template>
+  <div class="custom-404-container">
+    <h1 class="custom-404-title">404</h1>
+    <p class="custom-404-subtitle">Page Not Found</p>
+    <hr class="custom-404-divider" />
+    <p class="custom-404-message">
+      It looks like you're trying to access a page that doesn't exist. If you
+      were looking for something from the older version of our documentation,
+      you might find it here:
+      <a :href="redirectUrl" target="_blank" class="custom-404-link">{{
+        redirectUrl
+      }}</a
+      >.
+    </p>
+    <a href="/" class="custom-404-button">Take me home</a>
+  </div>
+</template>
+
+<style scoped>
+.custom-404-container {
+  text-align: center;
+  padding: 100px 20px;
+  color: #fff;
+  height: 100%;
+  display: flex;
+  flex-direction: column;
+  justify-content: center;
+  align-items: center;
+}
+
+.custom-404-title {
+  font-size: 72px;
+  font-weight: bold;
+  margin-bottom: 20px;
+}
+
+.custom-404-subtitle {
+  font-size: 24px;
+  margin-bottom: 20px;
+  letter-spacing: 2px;
+}
+
+.custom-404-divider {
+  width: 10%;
+  margin: 20px auto;
+  border: 0.5px solid #4a4a4a;
+}
+
+.custom-404-message {
+  margin: 0 auto;
+  max-width: 500px;
+  font-size: 14px;
+  font-weight: 500;
+  color: var(--vp-c-text-2);
+}
+
+.custom-404-button {
+  margin-top: 16px;
+  display: inline-block;
+  border: 1px solid var(--vp-c-brand-1);
+  border-radius: 16px;
+  padding: 3px 16px;
+  font-size: 14px;
+  font-weight: 500;
+  color: var(--vp-c-brand-1);
+  transition: border-color 0.25s, color 0.25s;
+}
+
+.custom-404-link {
+  color: #ff4c4c;
+  text-decoration: underline;
+  transition: color 0.3s ease;
+}
+
+.custom-404-link:hover {
+  color: #ff7878;
+}
+
+.custom-404-button:hover {
+  background-color: #ff4c4c;
+  color: #fff;
+}
+</style>