Overextended Redesigns

Note

This project is not affiliated with either overextended or Community Ox. It is a third party project to contribute externally with these projects by serving as a central point to share redesigns of the resources created originally by overextended.

Contributing & Author Rights

To ensure every redesign listed here is safe, performant, and follows community standards, we hold all contributors to high technical and ethical requirements.

Open Submission Policy

We welcome submissions from the community. Anyone may submit a redesign, provided it adheres to the original work's license (typically GPLv3). Submissions are manually vetted; if a PR is incomplete or fails to meet our quality bar, it will not be merged.

Author Protection & Opt-Out

While we support the open sharing of derivative works under GPLv3, we respect the preferences of original creators.

• Verified Ownership: If you are the original author and wish to have a redesign of your work removed from our listings, please open a "Take-Down" issue or contact Maximus7474.
• Flagging: If a resource is shared without the original author's active involvement, it will be marked with the GPLv3 Fork and No Support flags to ensure users do not contact the original author for assistance.

Note: Please submit only one redesign per PR. Ensure your work aligns with our submission guidelines.

Development Guide

This is a Next.js project bootstrapped with create-next-app.

Getting Started

First, run the development server:

bun dev

Open http://localhost:3000 with your browser to see the result.

This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.

Commit Conventions

Contributors must follow Conventional Commits, proper commit messages ensure a clean and readable project history.

Pull Request Process

Because github is picky on how to have multiple PR templates (even though they say you can -> github pull request templates), please ignore the template and follow the one listed here below:

Project Enhancement PR Template

## Description

### Rationale

<!--
    Reason for the changes made to the project within this PR.
    Please detail your explanation and avoid vague sentences (unless addressing a fix to a linked issue)
-->

### Verification
- Does the project compile and run locally? (Yes/No):
- Have you tested these changes across different screen sizes? (Yes/No):

### Technical Checklist
- [ ] I have followed the project's directory structure and naming conventions.
- [ ] I have not introduced any breaking changes to the existing data interfaces.
- [ ] I have removed any console logs or debugging code.

### Type of Change
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Refactoring (internal code changes with no functional impact)
- [ ] Documentation update

We appreciate all contributions, but those who explicitly explain their purpose are always better considered.

Learn More

To learn more about Next.js, take a look at the following resources:

• Next.js Documentation - learn about Next.js features and API.
• Learn Next.js - an interactive Next.js tutorial.

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!