AI‑First Engineering • Open Web • Automation That Scales
Pakistan‑based global tech org building open tools, SaaS products, and services across WordPress, JavaScript/TypeScript (Next.js, React, Node), Shopify, and applied AI + automation.

Short version: We build things that help devs, founders, and teams move faster. Much of our work is (or will be) open source. Jump in, give feedback, open issues, and build with us.

• Website: revnix.com
• Org Discussions (ask / suggest / feedback): See the Discussions tab in this org.
• Security Reports: security@revnix.com (please email; do not open a public issue for vulnerabilities).
• Hiring / Internships: hire@revnix.com
• General Contact / Press / Partnerships: hello@revnix.com

• Open Web & CMS: High‑performance WordPress, Headless WP APIs, custom Next.js frontends.
• JavaScript / TypeScript Apps: Next.js 15, React, Node, Supabase, serverless + edge.
• Shopify & E‑Commerce: Themes, apps, conversion / CRO tooling.
• AI & Automation: Content pipelines, internal agents, developer productivity tools.
• Starter Kits & Ops Guides: Practical templates and infra cookbooks for small teams.

Watch the org to get notified as these repos go public.

1. Browse repos. Look for issues labeled good first issue or help wanted.

2. Open an issue before large changes. Share the problem, your idea, and any questions.

3. Fork → branch → PR. Smaller, focused pull requests get reviewed faster.

4. Use clear, simple English. Many contributors are non‑native speakers—clarity helps everyone.

Branches
main is protected. Use feature branches: feature/<short-name>, fix/<short-name>, docs/<short-name>.

Commit Style (recommended)
Conventional Commits (not forced, but helpful): feat: add bulk importer to nextlycms api fix: null check in supabase client docs: update install steps chore: bump deps

Pull Requests

• Link the related issue.
• Explain what changed and why.
• Add screenshots / screen recordings for UI changes.
• Include setup + test steps so reviewers can reproduce.

Coding Style

• TypeScript: strict mode on in all TS/JS repos.
• Lint / Format: ESLint + Prettier (JS/TS); Ruff + Black (Python); PHPCS WordPress Standards (PHP/WP).
• .editorconfig at repo root when possible.

Testing

• Unit where it adds value.
• Light e2e smoke tests for deploy‑critical flows.
• Lint + type checks must pass CI.

• License: MIT (default; see repo for overrides).
• Default Branch: main.
• Node Version: 20 LTS (update here if this changes).
• Package Manager: pnpm preferred (project may override if documented).
• Environment Vars: Ship a .env.example; never commit real secrets.
• CI: GitHub Actions (standard lint/test/build workflows per project).

Found a vulnerability? Email security@revnix.com with details and reproduction steps. Please avoid filing public issues for security matters. We aim to acknowledge within 72 working hours.

Most conversation happens in Issues and Discussions right now. A public chat space (Slack/Discord) is planned—if you want early access, open a Discussion and let us know.

We train fresh grads and self‑taught builders. If you want hands‑on learning with real projects in WordPress, JS/TS full‑stack, Shopify, or applied AI:

1. Email hire@revnix.com with a short intro: who you are, what you know, what you want to learn.
2. Include your GitHub and any sample work (even small / learning projects).
3. Tell us if you are in Pakistan (preferred for on‑site training) or remote.

Need the Revnix, WPAegis, NextlyCMS, or Ficonz logo for press, blog posts, events, or integrations? Email hello@revnix.com with the use case.

Primary brand color: #0069ff.

• Watch the org for new public repos and releases.
• Star the projects you use.
• Join / start a Discussion to follow roadmap updates.

Open source works because of people who share, review, test, and teach. Thanks for being here.

— Team Revnix