# Documenting Design Building your own website is something I thought only programmers do. It was a skill I did not have. So when Pablo introduced us to various ways of making a website, I thought it was such a great opportunity to learn. This is not only useful here, but also in the future! When i first used Gitbook, it was so refreshingly simple to use. That was my first impression. But the more I started to use it, I started noticing its limitations. One thing that bothers me most is the fact that I cannot change the font styles or size. There are limitations on which colors I can use, barring only a few. But, more than building the website, I though it was better to focus on making the content that goes on the website. Since everything I am doing at IAAC is new and exciting, I thought it made sense to atleast keep my website very clean and easy to use. But it would be really nice to explore Notion to make my website. Currently trying to figure out when that would be possible, may or may not be this year :) For now, I am liking the easy of operation Gitbook offers, and I am learning to navigate its limitations. --- # 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://maithilis.gitbook.io/mdef-archive/terms/term-1/documenting-design.md?ask= ``` 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.