-
Notifications
You must be signed in to change notification settings - Fork 200
chore: folder and slug instructions on readme #333
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
a04007f
2d6c05a
e309f45
fbbeb3c
79bb1a0
b2d3f0a
e934f09
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -1,77 +1,292 @@ | ||||||
| # Keploy's blog with Next.js and WordPress | ||||||
| <p align="center"> | ||||||
| <img src="https://keploy.io/docs/img/keploy-logo-dark.svg" alt="Keploy Logo" width="200"/> | ||||||
| </p> | ||||||
|
|
||||||
| ## Configuration | ||||||
|
|
||||||
| ### Step 1. Prepare your WordPress site | ||||||
|
|
||||||
| First, you need a WordPress site. There are many solutions for WordPress hosting or you could use a Local by flywheel for setting up WordPress locally. | ||||||
| <h1 align="center">Keploy Blog</h1> | ||||||
|
|
||||||
| Once the site is ready, you'll need to install the [WPGraphQL](https://www.wpgraphql.com/) plugin. It will add GraphQL API to your WordPress site, which we'll use to query the posts. Follow these steps to install it: | ||||||
| <p align="center"> | ||||||
| <b>The official blog for <a href="https://keploy.io">Keploy</a> — live at <a href="https://keploy.io/blog">keploy.io/blog</a></b> | ||||||
| </p> | ||||||
|
|
||||||
| - Download the [WPGraphQL repo](https://github.com/wp-graphql/wp-graphql) as a ZIP archive. | ||||||
| - Inside your WordPress admin, go to **Plugins** and then click **Add New**. | ||||||
| - Click the **Upload Plugin** button at the top of the page and upload the WPGraphQL plugin. | ||||||
| - Once the plugin has been added, activate it from either the **Activate Plugin** button displayed after uploading or from the **Plugins** page. | ||||||
| <p align="center"> | ||||||
| <a href="https://nextjs.org"><img src="https://img.shields.io/badge/Next.js-18-black?logo=next.js" alt="Next.js"/></a> | ||||||
| <a href="https://www.typescriptlang.org"><img src="https://img.shields.io/badge/TypeScript-4.7-blue?logo=typescript" alt="TypeScript"/></a> | ||||||
| <a href="https://tailwindcss.com"><img src="https://img.shields.io/badge/TailwindCSS-3.x-38bdf8?logo=tailwindcss" alt="Tailwind"/></a> | ||||||
| <a href="https://www.wpgraphql.com"><img src="https://img.shields.io/badge/WordPress-GraphQL-21759b?logo=wordpress" alt="WPGraphQL"/></a> | ||||||
| </p> | ||||||
|
|
||||||
| #### GraphQL | ||||||
| --- | ||||||
|
|
||||||
| The [WPGraphQL](https://www.wpgraphql.com/) plugin also gives you access to a GraphQL IDE directly from your WordPress Admin, allowing you to inspect and play around with the GraphQL API. | ||||||
| ## What is this? | ||||||
|
|
||||||
| ### Step 2. Populate Content | ||||||
| A **Next.js (Pages Router)** blog application that powers the [Keploy Blog](https://keploy.io/blog). Content is authored in a headless **WordPress** instance and fetched at build time via the **WPGraphQL** plugin. The site is statically generated with **Incremental Static Regeneration (ISR)**, revalidating every 10 seconds for near-instant page loads and always-fresh content. | ||||||
|
||||||
| A **Next.js (Pages Router)** blog application that powers the [Keploy Blog](https://keploy.io/blog). Content is authored in a headless **WordPress** instance and fetched at build time via the **WPGraphQL** plugin. The site is statically generated with **Incremental Static Regeneration (ISR)**, revalidating every 10 seconds for near-instant page loads and always-fresh content. | |
| A **Next.js (Pages Router)** blog application that powers the [Keploy Blog](https://keploy.io/blog). Content is authored in a headless **WordPress** instance and fetched at build time via the **WPGraphQL** plugin. The site is statically generated with **Incremental Static Regeneration (ISR)**, revalidating every 10–60 seconds depending on the route for near-instant page loads and fresh content. |
Copilot
AI
Apr 6, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Prerequisite “Node.js ≥ 18” is slightly too broad for the current Next.js version: next@14.0.1 requires Node >=18.17.0. Consider updating the documented minimum Node.js version to avoid install/runtime failures on early 18.x releases.
| - **Node.js** ≥ 18 | |
| - **Node.js** ≥ 18.17.0 |
Copilot
AI
Apr 6, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Prereqs say “npm or yarn”, but the setup commands only show npm equivalents now. Either add the yarn commands back or remove yarn from prerequisites to keep instructions consistent.
Copilot
AI
Apr 6, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This line says Lighthouse audits run on PRs, but the Lighthouse workflow ignores **/*.md changes (paths-ignore). Consider clarifying that Lighthouse runs for code changes, not docs-only PRs.
| The CI pipeline will automatically run a build check and Lighthouse audits on your PR. | |
| The CI pipeline will automatically run a build check on your PR, and Lighthouse audits for code changes (not docs-only PRs). |
Copilot
AI
Apr 6, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The “Community Search” page is described as “Full-text search”, but the implementation filters posts client-side via includes() on title/excerpt. Consider rephrasing to “client-side substring search over title + excerpt” (or similar) to avoid overstating capabilities.
| | 6 | **Community Search** | [keploy.io/blog/community/search](https://keploy.io/blog/community/search) | `pages/community/search.tsx` | Full-text search scoped to community posts only | | |
| | 6 | **Community Search** | [keploy.io/blog/community/search](https://keploy.io/blog/community/search) | `pages/community/search.tsx` | Client-side substring search over title + excerpt for community posts only | |
Copilot
AI
Apr 6, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The “Global Search” page is described as “Full-text search across all posts”, but the implementation does client-side filtering over a pre-fetched list rather than a server-side full-text search. Please tweak this description to match actual behavior.
| | 11 | **Global Search** | [keploy.io/blog/search](https://keploy.io/blog/search) | `pages/search.tsx` | Full-text search across all posts (technology + community) | | |
| | 11 | **Global Search** | [keploy.io/blog/search](https://keploy.io/blog/search) | `pages/search.tsx` | Client-side search/filter across pre-fetched posts (technology + community) | |
Copilot
AI
Apr 6, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/api/search-all is described as “server-side full-text search”, but the handler just fetches and returns all community + technology posts (no query parameter / search). Please update the description to match actual behavior (e.g., “returns all posts for client-side filtering”).
| | 1 | `/api/search-all` | `keploy.io/blog/api/search-all` | `pages/api/search-all.ts` | Server-side full-text search across all posts, returns JSON | | |
| | 1 | `/api/search-all` | `keploy.io/blog/api/search-all` | `pages/api/search-all.ts` | Returns all community and technology posts as JSON for client-side filtering | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
WARNING: Incorrect Next.js version
The Tech Stack table states "Next.js 18" but the actual version in package-lock.json is 14.0.1. This should be updated to reflect the correct version.
| | **Framework** | Next.js 18 (Pages Router, SSG + ISR) | Entire app | | |
| | **Framework** | Next.js 14 (Pages Router, SSG + ISR) | Entire app | |
Copilot
AI
Apr 6, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR description mentions “Removed unreferenced libraries (e.g., highlight.js)”, but this PR only changes README and highlight.js is still present in package.json. Either update the PR description to reflect the actual scope, or include the dependency removal in the PR if that was intended.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
WARNING: References non-existent file
The file lighthouse_comment.yml no longer exists in the repository (it was deleted in the main branch). This line should be removed from the Project Structure documentation to avoid confusion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like this says "nextjs 18", it should be so, there is no nextjs 18 version released by vercel yet, we are still on 16 lol