Advice for work project

Greetings to all.
I have recently completed the information security certificate, and I believe that I can now venture to do a small practical project.
Well, my sister has a small clothing business, and I intend to collaborate with her, creating a website that will basically be a catalog of the products.
So, I want advice on:

  1. Aspects that I should take into account.
  2. Methodology to follow.
  3. Documentation that you should read.
    note: I intend to use de mern stack.

Well, I will be grateful for your answers.

[link added jun 03]

You skipped the most important step:

Getting requirements of what you need to build.

From there you can start with the things your asking for, but otherwise without understanding and describing to the best possible detail what you need to build, you could be setting yourself up for failure before you begin.

A description of “website to catalog products” can only go so far, for example:

  • Who edits the products?
  • Can user’s directly buy products?
  • How often are the products edited?
  • How many products could there be?
  • What does the catalog look like?
    etc etc,

The list is technically infinite, but from understanding the requirements of the problem you can build the solution how you see fit with your current skills, or even back-off some requirements. A catalog to show stuff off requires a whole different set of skills/technologies/requirements than a full on e-shop. There’s also usually the question if if you can use pre-existing solutions to help offset building this, from using a full on website builder, to more finite libraries.

2 Likes

I like what Brad has said, but just to add a little…

  • Methodology to follow.

Can you be clearer about what you mean by this? Do you mean the method of development? The architecture?

  • Documentation that you should read.
    note: I intend to use de mern stack.

Read whatever documentation you need. I always recommend that people get in the habit of reading through relevant docs - maybe read through the React docs a few pages a night? Maybe redux, maybe express? Whatever you need. And of course reference them when you need to.

1 Like

Thanks for your reply,
I have worked a little more on the ideas that I have in my mind.
In the link you can find a little more information about it.

I highlight the fact that the business is small, in the same way the application will be small.

Thanks for your reply.
At the point of methodology, I was thinking about things like

  1. Structure of folders.
  2. Know if the project starts with the backend or with the frontend.
  3. How to do so that the project can be scalable, or how to do so that another person can give continuity to the project.
  1. That really depends on you. There are a lot of different ways to do that. I like to have a folder for generic components, a folder for pages with sub pages nested underneath. I have folders for assets and services and redux (if needed) and utilities, etc.

  2. Either way works. I like to put a lot of thought into the structure of my data so if I’m starting with my f/e, I will create some mock data in the shape that I want. But you can also start with your b/e and just hit it with Postman or something to make sure it is working the way you want. For me, I use both from time to time, switching depending on my mood or the feature I’m working on. For some small things I may even develop both at the same time.

  3. Well, scalability is a whole other thing. I think that’s largely going to be a b/e issue - can your memory handle an uptick? Can your server handle the bandwidth? As far as someone else developing on your project - that is down to writing good code that is readable and well organized. That takes practice, but it’s good that you’re thinking about it.

1 Like