What kind of work for the portfolio of a front-end developer should be done?

Question

Frontend

Good afternoon. I am currently studying to be a front-end developer. Now I'm going to practice and create a portfolio. I saw a lot of ideas on the Internet what can be done (snake, doo list, calculator, weather forecast application, etc.), but it seems to me that this is not quite right and is somewhat divorced from the real tasks of a front-end developer. I would like to know what projects (close to real ones or real ones that are found in the work of a front-end developer) can be done for a portfolio, so that later I can show it at an interview (in addition to a one-page / multi-page site)? Thanks in advance everyone for your replies

Answer 1

None. In real development, everything will come from the needs of the business, which is not at all what the developer thinks about at the start. Do what shows development skills. This will never apply to real work.

Answer 2

A portfolio is a demonstration to the business of what you can do.
Even a simple to-do hosted on GitHub can tell quite a lot about you.
For example:
- Knowledge (or ignorance) of technologies
- Your coding style
- Algorithmic abilities
- Your level of work with IDE (any relevant, for the project!, config for IDE)
- Ability (or inability) to work with GitHub.
This includes commit naming, branching, merging, README file design, documentation, and so on.
- Ability (or, again, inability) to maintain a profile on GitHub.
No one seriously cares about this, but you should refrain from dubious photos, inadequate nicknames, and the like.
- etc.
An application as simple as todo can be completely copied and pasted from somewhere and passed off as your own. Therefore, it is best to write something more voluminous, but not go too deep into the jungle.
It is very good if a company needs, say, a Vue developer and you show knowledge of Vue in a portfolio.