Merge pull request #1342 from joe-rlo/develop

feat(news): add newsletter sign-up and past issues

.github/ISSUE_TEMPLATE/bug_report.md

@@ -4,14 +4,14 @@ about: Create a report to help us improve
 title: ''
 labels: bug
 assignees: ''
-
 ---
 
 **Describe the bug**
 A clear and concise description of what the bug is.
 
 **To Reproduce**
 Steps to reproduce the behavior:
+
 1. Go to '...'
 2. Click on '....'
 3. Scroll down to '....'
@@ -24,15 +24,17 @@ A clear and concise description of what you expected to happen.
 If applicable, add screenshots to help explain your problem.
 
 **Desktop (please complete the following information):**
- - OS: [e.g. iOS]
- - Browser [e.g. chrome, safari]
- - Version [e.g. 22]
+
+- OS: [e.g. iOS]
+- Browser [e.g. chrome, safari]
+- Version [e.g. 22]
 
 **Smartphone (please complete the following information):**
- - Device: [e.g. iPhone6]
- - OS: [e.g. iOS8.1]
- - Browser [e.g. stock browser, safari]
- - Version [e.g. 22]
+
+- Device: [e.g. iPhone6]
+- OS: [e.g. iOS8.1]
+- Browser [e.g. stock browser, safari]
+- Version [e.g. 22]
 
 **Additional context**
 Add any other context about the problem here.

.github/ISSUE_TEMPLATE/epic.md

@@ -22,12 +22,13 @@ assignees: Assign the likely EM once this epic is ready for Feedback or Ready fo
 ## Why ?
 
 - **Background:**
- 
+
   _(Link to Hypothesis doc or any relevant supportive information)_
 
 - **Move the Needle:**
 
   _(list the OKRs and KPIs which this epic should affect)_
+
   1. If you can imagine some data that we should start tracking now, detail that here.
   2. If we are already tracking the relevant metrics, link those dashboards here.
   3. List any hypotheses this Epic aims to prove/reject.
@@ -40,10 +41,10 @@ assignees: Assign the likely EM once this epic is ready for Feedback or Ready fo
 
   _(Describe in the form of User Stories, the complete set of statements that must be true in order for this body of work to be considered complete.)_
 
-  1. As a Founder, when I land on near.org I should be able to find DevHub or Horizon links within 3 seconds. 
+  1. As a Founder, when I land on near.org I should be able to find DevHub or Horizon links within 3 seconds.
   2. As a web3 enthauastic, when I click on `Get Started` I should be taken to...
   3. As a developer when I recieve a web push notification, clicking on the notification should take me directly to the relevant content.
-  4. As a user, when I search for blah, I should find blah, organized by blah. 
+  4. As a user, when I search for blah, I should find blah, organized by blah.
 
   </p>
 

.github/ISSUE_TEMPLATE/feature_request.md

@@ -4,7 +4,6 @@ about: Suggest an idea for this project
 title: ''
 labels: ''
 assignees: ''
-
 ---
 
 **Is your feature request related to a problem? Please describe.**

.github/ISSUE_TEMPLATE/secondary-focus-area.md

@@ -5,7 +5,6 @@ about: This issue serves to help us propose and organize support for impactful w
 title: "\U0001F525  [Secondary Focus Area] <Add a brief Title>"
 labels: ''
 assignees: ''
-
 ---
 
 **Motivation**

.github/workflows/continuous-integration-workflow.yml

@@ -40,4 +40,3 @@ jobs:
         run: pnpm install
       - name: Run lint check
         run: pnpm run build
-

.github/workflows/promote-develop-to-main.yml

@@ -4,7 +4,7 @@ on:
   schedule:
     - cron: '0 0 * * 2,4'
 
-permissions: 
+permissions:
   pull-requests: write
 
 jobs:
@@ -19,4 +19,4 @@ jobs:
         run: |
           gh pr create --base main --head develop -f -a gagdiez -a shelegdmitriy --title "2x weekly promotion of develop to main"
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/prs_must_have_labels.yml

@@ -10,7 +10,6 @@ on:
       - unlabeled
 
 jobs:
-
   check_labels:
     name: Check labels
     runs-on: ubuntu-latest

.github/workflows/release_notes.yml

@@ -1,24 +1,24 @@
 name: Automatic Github Releases
 
-on: 
+on:
   push:
     branches:
-      - "main"
+      - 'main'
 
 jobs:
   update_release_draft:
     runs-on: ubuntu-latest
     permissions:
       contents: write
     steps:
-    - name: Get current date
-      id: date
-      run: echo "tag=$(date +'%m-%d-%Y')"  >> "$GITHUB_OUTPUT"
-    - uses: actions/checkout@v4
-    - uses: ncipollo/release-action@v1.14.0
-      with:
-        generateReleaseNotes: true
-        tag: ${{ steps.date.outputs.tag }}
-        makeLatest: true
-        allowUpdates: false
-        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      - name: Get current date
+        id: date
+        run: echo "tag=$(date +'%m-%d-%Y')"  >> "$GITHUB_OUTPUT"
+      - uses: actions/checkout@v4
+      - uses: ncipollo/release-action@v1.14.0
+        with:
+          generateReleaseNotes: true
+          tag: ${{ steps.date.outputs.tag }}
+          makeLatest: true
+          allowUpdates: false
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/stale.yml

@@ -2,7 +2,7 @@ name: Close Stale Pull Requests
 
 on:
   schedule:
-    - cron: '0 0 * * 5'  # Run at midnight on Fridays
+    - cron: '0 0 * * 5' # Run at midnight on Fridays
 
 permissions:
   issues: write
@@ -21,4 +21,4 @@ jobs:
           days-before-pr-stale: 45
           days-before-close: 0
           close-issue-message: 'This issue has been automatically closed because it has been inactive for more than 180 days. Please reopen and prioritize this for development if it is essential.'
-          close-pr-message: 'This pull request has been automatically closed because it has been inactive for more than 45 days. Please reopen and see this PR through its review if it is essential.'
+          close-pr-message: 'This pull request has been automatically closed because it has been inactive for more than 45 days. Please reopen and see this PR through its review if it is essential.'

.github/workflows/update-sprint-board.yml

@@ -1,6 +1,6 @@
 on:
   schedule:
-    # Runs "at 05:00, only on Saturday" 
+    # Runs "at 05:00, only on Saturday"
     - cron: '0 5 * * 6'
 
 jobs:
@@ -9,12 +9,12 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: blombard/move-to-next-iteration@master
-      with:
-        owner: near
-        number: 92
-        token: ${{ secrets.CG_PROJECT_WORKFLOW_SECRET }}
-        iteration-field: sprint
-        iteration: current
-        new-iteration: next
-        excluded-statuses: "Done"
+      - uses: blombard/move-to-next-iteration@master
+        with:
+          owner: near
+          number: 92
+          token: ${{ secrets.CG_PROJECT_WORKFLOW_SECRET }}
+          iteration-field: sprint
+          iteration: current
+          new-iteration: next
+          excluded-statuses: 'Done'

.prettierrc

@@ -3,4 +3,4 @@
   "trailingComma": "all",
   "singleAttributePerLine": false,
   "printWidth": 120
-}
+}

CODE_OF_CONDUCT.md

@@ -14,22 +14,22 @@ appearance, race, religion, or sexual identity and orientation.
 Examples of behavior that contributes to creating a positive environment
 include:
 
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
 
 Examples of unacceptable behavior by participants include:
 
-* The use of sexualized language or imagery and unwelcome sexual attention or
- advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
- address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
- professional setting
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
 
 ## Our Responsibilities
 

CONTRIBUTING.md

@@ -1,31 +1,30 @@
-Thank you for your interest in contributing to the Blockchain Operating System reference gateway - Near Discovery.  We welcome contributions from everyone.  Below are various bits of information to help you get started.  If you require additional help, please start a [Discussion](https://github.com/near/near-discovery/discussions).
+Thank you for your interest in contributing to the Blockchain Operating System reference gateway - Near Discovery. We welcome contributions from everyone. Below are various bits of information to help you get started. If you require additional help, please start a [Discussion](https://github.com/near/near-discovery/discussions).
 
 ## Next Steps
 
 To learn more about how `near-discovery` works, checkout the guide to setup local development [here](https://github.com/near/near-discovery/blob/develop/README.md).
 
-
 If you are looking for relatively simple tasks to familiarise yourself with
 `near-discovery`, take a look at the issues labeled `good first issue`
-[here](https://github.com/near/near-discovery/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22).  If you see
+[here](https://github.com/near/near-discovery/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22). If you see
 one that looks interesting and is unassigned or has not been actively worked on
 in some time, please go ahead and start working towards creating your first pull request.
 
 If you have an idea for an enhancement to the Near Discovery, please submit a [feature request](https://github.com/near/near-discovery/issues/new?assignees=&labels=&projects=&template=feature_request.md&title=)
 
 ## Pull Requests
 
-All the contributions to `near-discovery` happen via Pull Requests.  Please follow the
+All the contributions to `near-discovery` happen via Pull Requests. Please follow the
 following steps when creating a PR:
 
 1. Fork the `near-discovery` repository and create a new branch to do you work there.
-2. The branch can contain any number of commits.  When merged, all commits will
+2. The branch can contain any number of commits. When merged, all commits will
    be squashed into a single commit.
 3. Thoroughly test your changes.
 4. When ready, create a pull request against the `develop` branch of `near-discovery`.
 5. Feel free to submit draft PRs to get early feedback and to make sure you are
    on the right track.
-6. The PR name should follow the template: `<type>: <name>`.  Where `type` is:
+6. The PR name should follow the template: `<type>: <name>`. Where `type` is:
    - `fix` for bug fixes;
    - `feat` for new features;
    - `refactor` for changes that reorganize code without adding new content;
@@ -38,9 +37,9 @@ following steps when creating a PR:
 ## After the PR is submitted
 
 1. When all the comments from the reviewer(s) have been addressed, the reviewer should
-approve the PR.
+   approve the PR.
 2. An approved PR will be merged automatically into `develop`, which is continuously deployed to [beta.near.org](https://beta.near.org)
 
-
 ## Release Schedule
+
 Changes from `develop` are promoted to the `main` branch weekly, on Thursdays.

README.md

@@ -24,10 +24,9 @@ To start local component development you need to follow this steps:
 
 2. Navigate to [near-discovery-components](https://github.com/near/near-discovery-components) and follow [Local development with BOS-Loader](https://github.com/near/near-discovery-components/blob/develop/CONTRIBUTING.md#local-development-with-bos-loader) section.
 
-3. *(optional)* Make a copy of `".env.example"` called `".env.local"`. **`NEXT_PUBLIC_NETWORK_ID`** allows you to choose working environment.
-
-*Note:* The **`NEXT_PUBLIC_NETWORK_ID`** value should be the same as chosen working environment in `near-discovery-components`. More about [environments](https://github.com/near/near-discovery-components/blob/develop/CONTRIBUTING.md#testing-across-multiple-environments).
+3. _(optional)_ Make a copy of `".env.example"` called `".env.local"`. **`NEXT_PUBLIC_NETWORK_ID`** allows you to choose working environment.
 
+_Note:_ The **`NEXT_PUBLIC_NETWORK_ID`** value should be the same as chosen working environment in `near-discovery-components`. More about [environments](https://github.com/near/near-discovery-components/blob/develop/CONTRIBUTING.md#testing-across-multiple-environments).
 
 ## Local VM Development
 

commitlint.config.js

@@ -1,3 +1,3 @@
 module.exports = {
-	extends: ['@commitlint/config-conventional']
-};
+  extends: ['@commitlint/config-conventional'],
+};

next.config.js

@@ -5,7 +5,7 @@ const nextConfig = {
   reactStrictMode: true,
   images: {
     domains: ['ipfs.near.social'],
-  },  
+  },
   experimental: {
     optimizePackageImports: ['@phosphor-icons/react'],
   },

package.json

@@ -110,4 +110,4 @@
       "path": "./node_modules/cz-conventional-changelog"
     }
   }
-}
+}