Merge pull request #3 from WeatherStack:mrbisquit/new-contributing-docs

Added some contribution info + new domain

Author: MrBisquit

docs/core/getting-started/contributing.mdx

@@ -0,0 +1,66 @@
+---
+title: "Contributing"
+---
+
+This is a short guide to get you started with contributing to the WeatherStack Core project.
+If this is your first (or one of your first) times contributing to an OSS (Open Source Software)
+project, please read the [new contributors guide](/docs/getting-started/new-contributors) before
+continuing any further.
+
+:::tip
+This is not the easiest project to get started with, as you need a lot of in-depth knowledge
+beforehand, look at the [new contributors guide](/docs/getting-started/new-contributors) to
+see what new contributors can add!
+:::
+
+## Prerequisites
+- Knowledge with CMake, C, and C++
+- Git (Gittyup option but recommended)
+- A compiler of sorts
+  - **Windows**: MinGW CLang
+  - **Linux**: CLang
+- An IDE
+
+## Building WS Core
+1. Pull the repository
+```bash
+git pull https://github.com/WeatherStack/core.git
+```
+2. Build
+<br />
+**Windows**:
+```batch
+build_win.bat build (Debug/Release) "path/to/vcpkg/toolchain/file.cmake"
+```
+**Linux**:
+```bash
+build_linux.sh build (Debug/Release)
+```
+3. Binaries will appear in the newly created `bin` directory
+
+## Contributing to WS Core
+1. Find an unassigned (and not blocked) task in the
+[project](https://github.com/orgs/WeatherStack/projects/2), or
+[issues tab](https://github.com/WeatherStack/core/issues)
+2. Comment and ask for the issue to be assigned to you, and wait for a response from
+maintainers
+3. Fork the repository, if you haven't already
+4. Create a new branch in the fork you just created, and name it something like
+`username/add-cool-feature`, keep it small, and adding your username is optional
+5. Make the first commit
+6. Optionally, create a draft PR stating what you will add to the PR, and the issue it
+links to
+7. Finish the task
+8. Create (if you didn't do step 6), and submit the PR, filling in the PR contents
+with what you changed
+:::tip
+PRs with no description have a high likelyness of being rejected without any review
+:::
+9. Wait for a review
+10. Make any changes requested by other contributors, or maintainers, then resubmit,
+and back to step 9
+
+:::note
+If you no longer want to work on a task, please comment and ask to be removed so that it can
+be taken by another contributor
+:::

docs/core/getting-started/index.mdx

@@ -0,0 +1,3 @@
+---
+title: "Getting Started"
+---

docs/core/index.md

@@ -3,4 +3,10 @@ title: "WeatherStack Core"
 sidebar_position: 3
 ---
 
-This is the core server for the entire project, this is what glues everything together.
+WeatherStack Core sits at lowest point of the Weather Stack, this is what manages data,
+connections, configurations, and other stuff.
+
+## Related documentation
+- APIs
+  - [WeatherStack Core External API](/docs/apis/core_external_api/)
+  - [WeatherStack Core Internal API](/docs/apis/core_internal_api/)

docusaurus.config.ts

@@ -15,7 +15,7 @@ const config: Config = {
   },
 
   // Set the production url of your site here
-  url: 'https://weatherstack.wtdawson.info',
+  url: 'https://www.weatherstack.org',
   // Set the /<baseUrl>/ pathname under which your site is served
   // For GitHub pages deployment, it is often '/<projectName>/'
   baseUrl: '/',
@@ -77,16 +77,20 @@ const config: Config = {
           customCss: './src/css/custom.css',
         },
         gtag: {
-          trackingID: 'G-820QPNTNHE',
+          trackingID: 'G-3RFWVE7HCR',
           anonymizeIP: true,
         }
       } satisfies Preset.Options,
     ],
   ],
 
+  headTags: [
+
+  ],
+
   themeConfig: {
     // Replace with your project's social card
-    image: 'img/weatherstack-social-card.jpg',
+    image: 'img/weatherstack-social-card.png',
     navbar: {
       title: 'WeatherStack',
       logo: {