> For the complete documentation index, see [llms.txt](https://help.doctorlogic.com/onboarding/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.doctorlogic.com/onboarding/design-and-development-overview.md).

# Design And Development Overview

The design and development portion of your site build includes the following:

#### Kickoff Call

During your kickoff call, you will meet with your Project Manager (PM) to review the look and feel of your site. We will review some of our DoctorLogic sites and common elements, as well as your current site and brand identity.

#### Design Creation

After the kickoff call, we will create a staging version of your new DoctorLogic site. The staging site will be branded to your practice, including logo, color palette, and imagery suggestions.

#### Design Feedback and Approval

After the delivery of this link, we will ask that you provide feedback if necessary on your new site's look and feel. This includes branding, color palette, fonts, photos for proven designs and overall homepage layout on tailored designs.  Logos, colors, fonts, and photos can be switched out at any time even after the launch of your new site.

#### Site Development

After delivery of your staging site, we will prepare for the launch of your new site. 


---

# 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://help.doctorlogic.com/onboarding/design-and-development-overview.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.