cortip/isomera

Drop support for Landing Pages

Open

#276 opened on Oct 20, 2024

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)TypeScript (6 forks)auto 404
back-endenhancementgood first issuehelp wantedtooling

Repository metrics

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

Description

Since many might use Webflow, there's no point in maintaining Next.js for a landing page. Even if it was needed, some might go with Remix or something else.

Since Landing Page is not tied via DTOs, validators and other constants that are usually data bridging helpers on frontend, backend and mobile, we can keep it more simple.

Contributor guide

Research direction
Identify all files related to landing pages (pages, components, routes) and remove them. Ensure no other modules depend on them.
Tech stack
typescript
Domain
frontend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
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
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90