> For the complete documentation index, see [llms.txt](https://johnkazer.gitbook.io/core-web-dev-concepts/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://johnkazer.gitbook.io/core-web-dev-concepts/master.md).

# Building a website of reasonable complexity

## Disclaimer

**Definitely a work in progress...**

The original purpose of this book was to document the activities and concepts behind a project internal to my company - a sort of primer for technically-minded staff who are web-app noobs.

In principle you should be able to find examples most of the content in my [open-source repositories](https://github.com/johnkazer) (the Azure Cosmos database being a notable absence).

## Motivation

Even a reasonably complex website uses a wide range of technology and concepts to create and host. This guide is intended to provide an overview, with pointers for further reading, of each one. In part I am trying to support the company I work for, in part remind myself of all the details and finally to provide a resource for others moving on from 'tutorial hell'.

![A skeleton 'full-stack' app](/files/-LtRJ50lkXG6lNPjoLID)

{% hint style="info" %}
 'Full-stack' basically means development of an app encompassing all of the required 'layers' of the stack. A 'full-stack developer' is someone who (to some level of competence) can create or manage all of these layers.
{% endhint %}

For the impatient, you can get a quick view of the constituent parts of a website if you hit f12 in Chrome (desktop) and look at the 'Elements' and 'Sources' tabs of the [DevTools](/core-web-dev-concepts/setup/chrome-dev-tools.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://johnkazer.gitbook.io/core-web-dev-concepts/master.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.