AletheiaFact/aletheia

Use getStaticProps in static pages

Open

#1,054 opened on Oct 16, 2023

View on GitHub
 (0 comments) (0 reactions) (0 assignees)TypeScript (19 forks)auto 404
good first issuetech

Repository metrics

Stars
 (53 stars)
PR merge metrics
 (PR metrics pending)

Description

Background Information

Some pages are always static and because we run a Custom Nextjs Server we do not get automated static generation. In order to achieve that we need to explicitly define that for the static pages.

What

List of pages that are static:

  • 400s and 500s errors
  • Code of Conduct
  • About
  • Privacy Policy

Contributor guide

Research direction
For each static page listed (400s and 500s errors, Code of Conduct, About, Privacy Policy), add the getStaticProps export that returns props. Typically, this is an async function that returns an object with props. For pages with no dynamic data, you can return an empty props object. Ensure the pages are correctly located under the pages directory and that getStaticProps is exported at the top level of the page module.
Tech stack
typescriptnextjsreact
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaScriptReactNext.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80