# Project: Make your website

## A point of reference about yourself

You don't need a personal website right off the bat but it's good to have and it's a fun project to test your skills with. In the simplest case, it's a direct conduit to you for anyone searching and another way to craft your narrative. It doesn't have to be elaborate at all. If you hate writing, don't blog. But you need to be a real person. Showcase your work. Geek out.

For this project, it's best for you to identify the personal websites of several people you admire and see what you think they've done right. In general, it's best to keep your site simple, clean and to the point rather than bloated and full of "look what I can do!" features. Let your portfolio of work speak for itself.

* [Why Every Job Seeker Should Have a Personal Website](http://www.forbes.com/sites/jacquelynsmith/2013/04/26/why-every-job-seeker-should-have-a-personal-website-and-what-it-should-include/)

## Documentation

Don't underestimate the importance of high quality documentation on your projects. As a professional developer writing good documentation is a must. As a job seeker it's a hidden opportunity to shine. Your projects should include a useful README and at least one screenshot. Include a section about why you built the project and another section with instructions to run the project locally.

Remember to write some documentation for both technical and non-technical audience. A potential employer should be able to follow your documentation, regardless of their technical background.

* [A Beginner’s Guide to Writing Documentation](http://www.writethedocs.org/guide/writing/beginners-guide-to-docs/)

## Assignment

Here are a list of portfolios of professional developers. Analyze these sites to see examples of portfolios how they're presented.

* [Stratis Bakas](https://stratisbakas.com/)
* [Matt Farley](https://mattfarley.ca/)
* [Dejan Markovic](https://www.dejan.works/)
* [Rafael Caferati](https://caferati.me/)
* [Ian Lunn](https://ianlunn.co.uk/)
* [Ben Adam](https://benadam.me/)
* [Seb Kay](https://sebkay.com/)
* [Jonny MacEachern](https://jonny.me/)
* [Jack Jeznach](https://jacekjeznach.com/)
* [Andriy Chemerynskiy](https://andrewchmr.com/)
* [Chris Ota's Portfolio](https://www.otadesigns.com/)
* [Pierre Nel](https://pierre.io/)
* [Adrien Laurent's Portfolio](https://adrienlaurent.fr/)
* [Thomas' Portfolio](https://www.thomasbosc.com)
* [Timmy O’Mahony](https://timmyomahony.com/)
* [Elliot's Portfolio](https://elliotcondon.com/)
* [James Warner](https://jmswrnr.com/)
* [Tiago Sá's Portfolio](https://i-am-tiago.com/)
* [Patrick David](https://bepatrickdavid.com/)
* [Luis Krötz](https://luiskr.com/)
* [Leonid Kostetckyi](https://lk.emotion-agency.com/)
* [Alex Madeira](https://www.alexmadeira.com.br/)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://howtocode.trek.io/topics/getting-hired/preparing-to-find-a-job/project-build-a-personal-website.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.