I personally like H2 (yes you could set H1 sizes - I know)
I personally like lg body font size
You may change as needed
PROMPT:
Elements project currently open. Use the Elements MCP tools.
Site: create a welcoming, refreshing, uncluttered, well spaced.
Propose first, build second. Never build unapproved.
ROUND 1 — Look at the site. Show me 3 distinct design directions.
For each: name, the idea in two lines, type scale, spacing, button
treatment, and what changes on the Home page. No building.
ROUND 2 — I pick one. Apply it to the Home page only, then stop.
ROUND 3 — I approve Home. Roll it out three pages per session,
stopping after each page.
RULES
Keep every page, name, and URL. Keep existing text — move and
restyle only. Preserve Globals, never detach them. No custom
components or code. Theme’s existing colors and fonts. Body lg at
all sizes. Top heading per page is H2, one per page, never add H1.
Keep the main body font size lg throughout all screen sizes.
Never touch CMS. Never publish.
must be really nice saying hey..ive created this site…oh…wait a min some AI created it…I prefer the fun of learning and creativity of doing it myself not some computer somewhere!!!
David I have a site with over 100 assets, all mine designed by a graphic designer with me. I own these assets and they are hand created by a professional. I have all their Pantone colours and have them in high res/low res/svg and various printing formats.
I am NOT a web designer and have been using Elements since Beta and pre AI version, so as AI is a tool I have used it to help me when I get stuck and to “beautify” my crap designs. So in your world does using AI as tool - which it is - constitute something that was created by AI or crafted and used all tools available?
I suppose it might be. However, short of only creating products by yourself with no employees or other help, you can’t get there from here. I’ve run two-people companies and two-thousand people companies, and the way I treat AI is basically the same as I treated employees: if it/they can get something done while I’m concentrating on the bigger picture, that’s what I’ll use.
In one case I wrote a 250-page manual for a product that didn’t exist (design) and handed that to two very talented programmers. The three of us then took on different aspects of the actual coding after discussing the architecture needed. That’s exactly what I’m doing with Claude. Overall design is mine, architecture is a discussion between us, implementation is shared in tasks between myself and Claude.
This is a good debate. From my perspective it depends on what you want the AI to do.
If I may, I’m going to make a comparison. I do photography. I could take a photo with no skill on my iPhone and feed it into AI to ask it to change the photo and make models look galmorous. On the other hand I can pick up my DSLR, carefully light, pose and composite each photo and then do my own digital processing and editing with no help from AI.
At what point does something cease to be my own work?
The reality is I use AI as a tool for repetitive tasks that I used to do manually such as adjusting skin tones, removing glare from skin, removing unwanted objects (e.g. a tripod) and smoothing out background screens.
As a general rule I want all my photos to be real, that is they look like the person posing in them and not someone else. That’s what my clients want, rather than some artificial recreation. But no-one objects to me using AI to make automated edits under my direction to do what I used to do manually until recently. It saves a lot of time and it is still my photo.
Sometimes I will generate a 100% AI image. Why? To help clients see what they may look like or to generate mood boards to give ideas. At other times I will avoid any use of AI if the client requires it or it’s for a competition (where rules forbid AI).
So returning to the use of AI in developing websites; it’s a tool. I use it to speed things up and save time. How much I use the tool will depend on the context and what I am trying to achieve. This will vary from perons to person and if you have clients, from client to client.
Exactly. Moreover, Elements is a tool. So you now have a tool which can live within (API) or communicate with (MCP) a tool.
I think a lot of the anti-AI argument is really fear of being out of a job. That “site design” will become so simple that anyone can do it and you don’t need to hire someone.
I don’t see what’s being done between Elements and AI as putting anyone out of a job. If anything, I can sell the talent of using the tools to do the work a customer needs better now than I ever could. Why? Because I can prototype faster, I can deliver faster, I can design better and more flexibly, and I can produce better Web sites than I could a couple of years ago.
Moreover, the tool combo does everything. Previous site builders did some, or eventually most of the things you might need done for a site. I’m not aware of anything I’d want to do on the Web that I can’t do with the Elements/AI combo.
REALLY impressed by the design implementation - took awhile in Claude - but really really happy with the results - had a few tweaks - but to be expected VoteDroste.org is up
