Loading...
Answers
MenuCan my website be recoded for my new business or do I have to start from scratch?
Had a marketplace website done with node.js for backend and react for front end. Would like to pivot to an entirely new business but with same marketplace model. Can it be recoded for the new business or have to start from scratch?
Answers
It depends on how similar the businesses are. For example if you are moving from selling shoes to selling hats versus you are moving from selling shoes to creating web apps – they are very different situations. Since you said that the marketplace model is the same, then it is probable that you can reuse a lot of the code from your current website. Both React and Node.js are up to date tools for building web apps. An experienced developer should be able to do this for you.
G'day,
The short answer is yes. No need to reinvent the wheel again.
Most likely the underlying fabric is focused towards the mechanism for advertising and selling generic products but you tailored those products into something specific.
Keep the same mechanics just change the design and repopulate the products with the new ones you wish to sell.
The great thing with code, especially if you are talking about a similar marketplace model, it can be repurposed to suit your new needs.
Definitely, don't pay again to have it all recreated from scratch!
Cheers,
Dr.Nick
Most of the time you will be able to reuse a large portion of your codebase.
Related Questions
-
How to build a technical company just with AI
bold new or lovable in front end and cursor ai in a backend
Choose Your AI Stack - Frontend: Use an AI no-code release like Lovable or Bolt.new to generate UI components (React, Tailwind) and integrate basic flows (auth, data fetching) from prompts. According to one comparison: “Lovable … full stack app creation from natural language” - Backend: Use Cursor AI an AI-powered IDE based on VS Code with auto-complete, chat prompts, debugging, and project-wide context. Perfect for writing/refining server logic. Outline Your Architecture 1. Prompt Lovable/Bolt.new Ask for "a React frontend with Tailwind, Supabase as backend, and authentication flow" Export code (to GitHub or ZIP) 2. Refine via Cursor AI Import the generated codebase into Cursor Prompt Cursor to improve structure: “Refactor authentication code, add Joi validation” Cursor can generate tests, APIs, fix bugs, etc. A Reddit user who did this shared: “I did a full AWS thing… Except some minor tweaks here and there it was all Cursor and Claude.” Step 3: Manage AI Workflow - AI thrives with short, focused prompts: feed it ERROR logs or specific chunks, not the whole app - Maintain context: keep docs, ER diagrams, project folder structure up-to-date so Cursor understands your codebase - Use hybrid flow: prompt AI to scaffold, then refine manually; don’t simply trust its first output Step 4: Build & Refine Iteratively - Prototype fast: Leverage AI for scaffolding (frontend + backend) arguxlabs.com+8joshsorenson.com+8reddit.com+8 - Fine-tune features with Cursor: validation, performance, bug fixes - Keep user interface polished: one user said “I took the code it produced and loaded it up in Cursor, and Cursor has done a great job adding to it since then.” Example Tech Flow 1. Prompt Lovable/Bolt.new: “Create a TODO app with auth + Supabase DB” 2. Export code → open in Cursor 3. Cursor: “Add API endpoint /todos/create with validation and tests” 4. Cursor: “Refactor UI for mobile responsiveness” 5. Host frontend via Vercel, backend on Supabase or serverless my tip - You still need to oversee: AI suggests; you validate - Use modular AI cycles: prompt, review, refine -Balance control: don’t over-guide the AI—adapt to its patterns - Avoid context overload: reset chats, maintain clean project docs TL;DR • Frontend: Lovable/Bolt.new to generate UI scaffolding • Backend: Cursor AI to create, debug, and refine logic and APIs • Workflow: prompt → export → refine → deployment AI is your co pilot you stay in the driver’s seat You can build a robust technical company using just these AI tools but it works best if you're guiding, cleaning up, and iterating. AI accelerates your work, but doesn’t replace the human in the loopPE
-
To be a front end wen developer with ZERO experience.
The first thing you want to do is to stay away from major JavaScript frameworks—they are a time sink that doesn't translate into much experience down the road. Invest some time into learning the basics HTML, CSS, vanilla Javascript. Start simple with these technologies and build on that stack over time. If you start making websites with Bootstrap, React or something else, you'll quickly be overwhelmed and you'll miss on essential basic understanding. The first step for you now would be go explore CodePen, make an account and use that as a playground. It greatly reduces your moving parts, as you won't have to think about setting up a development environment. As to what to build and get your hands dirty with—find simple CodePen examples that you like, copy them and play with their code. Try changing things here and there and see how this plays out.RD
-
What’s a good book on writing and testing cross-browser compatible CSS/HTML?
This is a great question, and my best Googling / Amazon-searching efforts aren't turning up much. Maybe time to write that book :) After considering this one for a bit, I can also imagine why this would be a tough book to write. With browser technology iterating relatively quickly, and with new CSS features continuously developing, any resource that dives into specifics (specific browsers, specific features, specific issues, etc) would inevitably be out of date within a matter of years, if not months. This isn't to say there can't be great resources on designing across browsers, just that talking specifics can pose a unique challenge (although perhaps great incentive to release new editions of the book each year!). That said, here are some resources that I've found helpful and somewhat timeless in their advice. Some are more general in their discussion of best practices and considerations, while others are more specifically issue- or browser- related. http://www.smashingmagazine.com/2010/06/07/the-principles-of-cross-browser-css-coding/ Smashing Magazine (June 2010) - a great article that covers general approaches to creating CSS/HTML to work across browsers as best as possible - an oldie but goodie. https://www.modern.ie/en-us/category/code-with-standards Internet Explorer (November 2013) - somewhat ironically, Internet Explorer has a great article on fundamental best practices for ensuring you have to do as little browser troubleshooting as possible late in the game. http://css-tricks.com/search-results/?q=cross+browser CSS Tricks (search archive) - when I have a CSS issue I'll often turn to CSS Tricks. If you want a good overview of general cross-browser issues to watch out for, this search results page gives a good top-level perspective. Like I said, there are lots of great articles out there covering all the issues and solutions surrounding something like IE8, but they'll be somewhat irrelevant in the coming years (e.g. https://www.tinfoilsecurity.com/blog/cross-browser-development-tips-css). So no book recommendation, alas. Hopefully some of these links might be helpful. If not, I'm serious about writing that book :)MK
-
What can be done to improve mobile page load performance after you optimized all the assets (css,js,images)?
Sometimes you get too caught up, and as a result, your site gets slower and slower because you keep adding more and more. It's called code bloat, keep your site lightweightAS
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.