[Phase 1] Personal Portfolio - Planning

Context

Since graduating from my college, I have been doing job searching for seven months but do not have any response. Because of the massive applications, I started to think about what I can do to better illustrate my values and get a chance. At the same time, I wanted to develop something with Angular. Then, I came up with an idea that I could develop a personal portfolio with my tech stacks to demonstrate my experience and skills. That is why I am doing this project.

I would like to start my project with planning, the first stage of the software development lifecycle. Meanwhile, I would put my steps and works into articles and publish them on this website. I hope my works can benefit others when this project goes ahead.

Goals

1. Help readers to understand my work experience and projects.
2. Allow creators to build their own portfolios.

Needed Features

1. Content Management
2. Authentication
3. Accessible layout

Here are the explanations for the two parts above.

As what I mentioned in context, I would like to create a portfolio for better illustration of my values. Illustration here is not only about showing my things but also about ensuring that the readers can receive the messages precisely and have a good experience. Therefore, I listed two goals under "Goals" section. The first one is to ensure readers can know more about me through my portfolio. The second one is about the content management which decides how the portfolio will look like.

For achieving these two goals, there are three features I have to implement.

The first one, of course, is the content management. The creators need to manage the contents on their portfolio. This is necessary to provide a portal for them to do so.

When the creators want to manage their contents, they not only want to edit or delete their contents but also want to prohibit others from taking control of their contents. Therefore, here comes authentication. Before the creators can make any modification on their contents, they must log into their own account. It secures the content management rights exclusively for the rightful owner.

Lastly, an accessible layout means users can access the website in multiple devices, such as mobile and desktop, without affecting their experience. In other words, the website must be responsive. It is a common feature in web design and a strong user demand.

Conclusion

That is all I did in this planning phase. I listed two goals and three features based on the analysis of my ideas. These goals and features are identified from two perspectives, namely creators and readers. They will be the base of next analysis phase.