# 7️⃣ Finishing touches We've come a long way. We now have a fully-functional and good-looking website. In what is the last section of coding before we move on to deploy our finished project, we'll add some refinements and finishing touches that will add a veneer of professionalism to our site. We'll add a loading indicator (sometimes called a 'spinner') so that the user knows something is happening in the background while data is being fetched from the REST API. No website is complete without a 404 page. We hope we'll never need it, but we should have one just in case. We'll add one! We will also take a look at a couple of other components that Frontity provides. Firstly we'll see how we can use the `` component to process our content, and then we'll use the `` component to make our site SEO friendly. We'll round out this section with some ideas and suggestions for more finishing touches that you could add on your own. Don't worry - we'll give you some hints and tips, and show you where you can find more info in the docs. We're on the home straight... --- # 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://tutorial.frontity.org/part7-finishing-touches.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.