> This is a brand new repository that we need to build out. It is a repository that is going to be used as a framework repository for other AI agents to build websites. Ideally, we need to break the website framework into four component parts. Those parts being in order:
>
> 1. Defining the purpose of the website
> 2. Defining the template of the website
> 3. Defining the tooling of the website
> 4. Defining the style of the website
> 5. Etc.

### Purpose

> The purpose of the website needs to be an all encompassing directive towards completing whatever goal we need. So if the user says build some type of website for ecommerce, that is its purpose. It must include things that are ecommerce related, like possibly catalogs or information or other things. If the user defines the purpose as a documentation based website, that is its purpose, and it must achieve its purpose completely.

### Template

> The user should be walked through a set of ideas that will dictate the template of the website. For instance, if the user is building an ecommerce website we need to specify how the layout will work, what types of pages are required, do we want breadcrumbs at the top, do we need a logo at the top, do we need a slideshow, do we need simply a drop down of all the categories of the products that we're selling? If the user specifies something like documentation for the website's purpose, then the template needs to be different. For a documentation based website, we need to consider things like, do we need search? Do we need breadcrumbs? Should we have a navigation panel on the left side? Do we need to have backlinking for tons of glossary items?

### Style

> We also need to define the style of the website. How will it look? How will it feel? When it comes to the style, it's all down to the colors, the atmosphere, the rounded edges. We don't care about the code here, only about what we can actually visibly see on the web page. This is where the CSS will be derived from. And this is how the user will be guided around the page. For instance, if we're working on an ecommerce website and trying to sell some type of product, we probably want something that visually indicates what the purpose of the website is. For a documentation website, we probably want to correctly identify the users, which would be developers. So we probably need different types of functionality and visibility settings. Like, for instance, a dark mode or a light mode.

### Tooling

> The tooling is probably one of the least and most important pieces of this entire thing that will dictate the actual implementation of the website. What programming languages should we use? Do we need a database? What type of styling tools are we going to use? Are we going to use raw CSS? Are we going to use JavaScript? Is this going to be built in WebAssembly? Do we need to connect to a server? Do we need a payment processor? Is this purely a front end project, or do we need to build the back end too? If we're building all of this out, what libraries will we need, and how will we achieve our goals based on the technology we're picking.

---

> Remember, we are building the framework for building websites using large language model agents. We are not building the website here. Remember, this has to be all encompassing, all comprehensive, and all versatile to handle every single situation or circumstance on designing a website front end would need. Please do what ever research, investigation, or websearches you need. If there are any gaps, let's bring it up with the User.