[gsoc26] Added WLP modernization idea

[nemesifier]

Added WLP modernization idea-

[coderabbitai]

Warning

Rate limit exceeded

@nemesifier has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 9 minutes and 45 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between b5481bb and bd8369b.

📒 Files selected for processing (2)

• releases/25.10.rst
• requirements.txt

Walkthrough

Adds a new GSoC 2026 project idea "WiFi Login Pages Modernization" to developer/gsoc-ideas-2026.rst, including description, image reference, technologies (JavaScript, Node.js, React), mentors, project size (175 hours), difficulty (medium), five implementation objectives, prerequisites, implementation approach, testing strategy, and expected outcomes. Also updates spelling_wordlist.txt with six new allowed terms: codemods, dom, npm, reconnection, redux, and testability.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding a GSoC 2026 WiFi Login Pages modernization project idea to the documentation.
Description check	✅ Passed	The description, though brief, is related to the changeset by referencing the WLP (WiFi Login Pages) modernization idea being added.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch gsoc26-add-wlp

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In `@developer/gsoc-ideas-2026.rst`:
- Around line 52-207: Run the validator (PRODUCTION=1 ./run-qa-checks) to see
exact RST errors, then fix developer/gsoc-ideas-2026.rst by correcting
ReStructuredText formatting around the top sections and directives: ensure
section underline lengths match their titles (e.g., "WiFi Login Pages
Modernization", "Key Objectives", "Code Refactoring and Architecture
Improvements"), add required blank lines before directives like ".. image::" and
".. important::", fix inline literal markup to use double backticks for code
(``client/components/status/status.js``), ensure bullet/list indentation and
nested lists are properly indented, and remove any stray trailing whitespace or
malformed hyperlink roles so the file passes the QA checks.
- Around line 88-89: The document references issues `#272` and `#314` that cannot be
found in the openwisp-wifi-login-pages repo; confirm whether those issue numbers
belong to this repository or another OpenWISP repo and either (a) correct the
issue numbers and hyperlink targets to the proper repository/issues, (b) change
the text to reference the correct/closed issues with status, or (c) remove the
incorrect references; locate and update the references in
developer/gsoc-ideas-2026.rst where issues `#272` and `#314` are mentioned (near the
existing references to `#918`, `#947`, `#870`) so all issue links point to valid
issues or are removed/annotated as closed.

🧹 Nitpick comments (1)

developer/gsoc-ideas-2026.rst (1)

74-76: Consider clarifying the scope of "backward compatibility."

The statement "All refactoring work should maintain backward compatibility—since users interact with the application through their browsers, these internal code changes should be transparent to them" is generally accurate for browser users. However, consider adding a note that organization administrators who have customized YAML configurations may need to verify their customizations still work after the refactoring, particularly for the header HTML changes (objective 3) and any breaking changes from the React 19 upgrade.

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4b896e7 and 0f67efc.

📒 Files selected for processing (3)

• developer/gsoc-ideas-2026.rst
• images/gsoc/ideas/2026/wifi-login-pages.webp
• spelling_wordlist.txt

🧰 Additional context used

🪛 GitHub Actions: OpenWISP Docs

developer/gsoc-ideas-2026.rst

[error] 1-1: ReStructuredText check failed. File could be reformatted. Step: PRODUCTION=1 ./run-qa-checks. Process exited with code 1.

🔇 Additional comments (3)

spelling_wordlist.txt (1)

35-35: LGTM! Spelling wordlist additions are appropriate.

All six added terms (codemods, dom, npm, reconnection, redux, testability) are relevant technical terms used in the new GSoC project idea for WiFi Login Pages Modernization. The terms are correctly alphabetized and consistently formatted.

Also applies to: 69-69, 190-190, 239-239, 241-241, 285-285

developer/gsoc-ideas-2026.rst (2)

52-67: Well-structured project idea with clear objectives and outcomes.

The project proposal is comprehensive and well-organized:

• Clear project metadata (mentors, size, difficulty)
• Five specific, actionable objectives with GitHub issue references
• Appropriate prerequisites matching the required technologies
• Balanced testing strategy that encourages TDD without being prescriptive
• Detailed expected outcomes with deliverables for each objective
• Comprehensive documentation requirements including migration guide and video demo

The 175-hour estimate appears realistic for the scope of work described.

Also applies to: 78-86, 154-207

---

137-152: No issues found. All statements in the GSOC project idea are accurate. React 19 is stable (since December 2024), the React 18.3 → 19 upgrade path is officially recommended with deprecation warnings in 18.3 to catch breaking changes early, official React 19 codemods are available via npx codemod@latest react/19/migration-recipe, and Enzyme is effectively end-of-life for React 18+ with React Testing Library as the consensus replacement.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}