Problem starting project


I just finished the front end libraries challenges and I am about to start the projects, but I have a problem. I don’t really know how to start a project. I get the coding part but i don’t know how to use it.

I also want to start creating my own web application for a portfolio but don’t know where to get started with all the needed files and configuration and so forth. Do I just open up my text editor and start typing or what is the process?

Thank you for your help!

When you are starting a project like build a tribute page,

There is a link at the bottom of instructions to a codepen template which you can open and start typing to get started.

Hope this helps :slight_smile:


Thank you very much for answering my question!
In regards to the codepen, it wasn’t quite what I am looking for. I did the responsive web design projects a while back and it worked great then.
What i hoped was that i would be able to get some kind of reference to what a project would look like in a real world situation.
How you would create the package.json file?
How you would create a directory for you project locally?
How you would migrate that to a server to have it online?
Basically what the steps before programming would be if you were to create a web application for a client?


All these are great questions. I believe if you take these to google or youtube, there’ll be a lot of medium articles/videos for you to dive in.
And for React.js projects, there’s a CLI node package called create-react-app; it provides a project boilerplate, with package.json and initialized as a git repo and everything. :slightly_smiling_face:

Hi there , i have not worked in a real coorporate environment but i have worked on a real project based on my school final year project where i worked for a client in a group.

To answer your questions if you were to work for a client the first important step is gathering of requirements.Requirement gathering is the most obscure and important procedure because the requirements can be unsure. Client can also change requirements and you have to work with changes.

The way my group did was we gathered required by fulfilling a set of criterias.

Things like functional and non functional requirements.

so for functional requirements it will be like ( what sort of functionality a client wants e.g user being able to log in in a online portal for students , teachers able to get units you get the gist)

secondly non functional will be things like how fast the page should respond.

These are the sort of things to think about. In reality client projects are really big , and take months to complete . ( I have screenshots to the final apge if you are interested to view since its expensive to turn on the AWS site where we hosted the site).

the package.json file can be created through a comment npm init in the terminal .

as for migrating , it depends how big the project is if your project has backend like database then u do need to host it on a server like herku or aws.

But for static pages u can push it on github and github will host it for u