Amour Editorials is a professional platform that helps students and professionals craft compelling Statements of Purpose (SOPs), Letters of Recommendation (LORs), and other academic documents — turning their dreams into impactful stories.
https://amour-editorial-website-4p915oz2c-lolpanda2004s-projects.vercel.app/
- About Us
- Features
- Preview
- Tech Stack
- Installation
- Folder Structure
- Requirement Document
- Contributing
- Contributors
- Connect with Us
Amour Editorials was founded by Akshai Krishna A and Lathika D with the mission to help aspirants express their journeys with honesty and power through SOPs, LORs, and other impactful narratives. Backed by years of experience and acceptances to top global universities, the team ensures every story echoes across admission panels worldwide.
- 🖥️ Fully responsive UI with 3D effects and animations
- 📄 Secure form submissions and email integrations
- 📅 Calendly booking support
- 🔐 File uploads through backend integration
- ⚙️ Modular and scalable Next.js frontend
- ✨ Advanced UI with Framer Motion and custom TSX components
- 🧪 TypeScript support and linting
- 🎯 SEO, performance, and accessibility focused
- 📎 Social sharing & legal pages (Privacy, Terms)
| Page Name | Description |
|---|---|
| 🏠 Landing Page | Engaging homepage with animation & brand overview |
| 🧍 About Us | Mission, vision, and team insights |
| 📑 Services | SOP, LOR, Editing service details |
| 💬 Testimonials | Client reviews and success stories |
| ❓ FAQs | Process and timeline clarifications |
| 📚 Resources | Samples and writing tips |
| 📝 Blog | Informative articles on writing, branding, etc. |
| 📅 Booking Page | Calendly embed for consultation scheduling |
| 📩 Contact Page | Contact form connected to backend |
| 🔐 Privacy & Terms | User protection documents |
| Area | Technology |
|---|---|
| Framework | Next.js (App Router) |
| Language | TypeScript |
| Styling | Tailwind CSS |
| Animations | Framer Motion |
| Component Library | Custom + ShadCN (UI primitives) |
| Icons | Lucide |
| Build Tool | Vite / Next.js build |
| Linting | ESLint |
| Area | Technology |
|---|---|
| Runtime | Node.js |
| Framework | Express.js |
| API Routes | /form (formRoutes.js) |
| Controllers | formController.js |
| Email Service | Nodemailer (emailService.js) |
| Security | Helmet, CORS, HTTPS |
| Component | Platform |
|---|---|
| Frontend Hosting | Vercel |
| Backend Hosting | Render / Railway / AWS / Cyclic |
| DB (Optional) | Supabase / MongoDB Atlas |
| CI/CD | GitHub Actions (optional) |
- Node.js ≥ 18.x
- npm ≥ 9.x
git clone https://github.com/sneha-94/Amour-Editorial-Website.git
cd Amour-Editorial-Website
npm run startAccess frontend:
http://localhost:3000Access backend:http://localhost:5000(or your configured port)
Amour-Editorial-Website/
├── amour-Backend/
│ ├── Controllers/
│ ├── routes/
│ ├── utilise/
│ ├── index.js
│ ├── package.json
│ └── ...
├── amour-next-ts/
│ ├── src/
│ │ ├── app/
│ │ ├── components/
│ │ └── lib/
│ ├── public/
│ └── ...
├── PROJECT-SETUP.md
├── Contributors.md
├── LICENSE
└── README.md
📎 Click to view the complete project requirement document
We welcome contributions from developers, designers, writers, and testers! 💜
-
Fork the repository
-
Clone to local
-
Create a new branch for your feature/bug
-
Commit changes with meaningful messages
-
Push and create a Pull Request
-
Raise a issue We appreciate you taking the time to improve the project! Here’s how to raise an issue effectively:
Check for Existing Issues -Browse through existing issues to avoid duplicates.
Use a Clear Title -Make your title short but descriptive (e.g., "Navbar overlaps logo on mobile").
Describe the Issue in Detail -Explain what the issue is and why it matters. -Mention the expected behavior vs. actual behavior. -Include steps to reproduce the problem (if it's a bug).
Attach Relevant Media (if applicable) -Screenshots, GIFs, or terminal logs help speed up understanding.
Use Appropriate Labels -Add labels like bug, feature, enhancement, good first issue, etc.
Be Respectful and Constructive -Keep communication kind and focused on solutions.
-
Create a Pull Request Go to your forked repo on GitHub. You'll see a prompt to "Compare & pull request".
Click it.
Fill in the PR title and description: ✅ Title: docs: add contribution guidelines for issues and PRs ✅ Description: Briefly explain what you did. Example: This PR adds a new section to the README with clear steps on how contributors can raise issues and submit PRs, as requested in Issue #.
Submit the PR.
-
Comment on the Issue If the task was assigned via an Issue, comment something like: I have created a PR that addresses this. Please review it here: [#PR-Link]
- 🧹 Maintain code style & lint rules
- 🚫 Don’t break existing features
- 🧪 Write/modify tests (if applicable)
- 💬 Be clear in PR descriptions
- 🙌 Respect others and give constructive feedback
-
🧠 Lathika D - Founder & Creative Director
lathika@amoureditorial.com
Vision, content strategy, and brand direction -
🧠 Akshai Krishna A - Reporting Manager & Co-Founder
akshai@amoureditorial.com
Technical requirements, project management -
🧠 Suraksha M - Social Media Manager
suraksha@amoureditorial.com
Content validation, social integration
-
🛡️ Sayman Lal
buisnesssayman@gmail.com
Project Setup, SEO, Next.js & Typescript implementation
-
🛡️ Krithika Meenakshi
krithika.meenakshi11@gmail.com
Frontend Development, UI/UX, Design
-
🛡️ Mohd Jarir Khan
kjarir23@gmail.com
Navbar, About, Blog & Contact page development
- 🌐 Official Website
- 📧 Email: contact@amour-editorial.com
Your contributions will be reviewed and appreciated! Let’s build something impactful together.
| Page / Feature | Preview |
|---|---|
| Landing Page |  |
| Services Section |  |
| Booking Flow |  |
| Testimonials |  |
| Responsive View |  |
This project is licensed under the MIT License.