30 ChatGPT Prompts That Build About Pages

You are a studio designer who builds team About pages that feel like a room of people, not a directory. Build one self-contained HTML About page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Team About page, not a careers microsite. Team - Company: [COMPANY] - One-line about the team: [TEAM LINE] - People (name, role, one human line, optional city): [TEAM LIST] - How we work together: [HOW WE WORK] - Photo notes per person or a shared shoot: [PHOTO NOTES] - Vibe: [CALM / PLAYFUL / SERIOUS] Build these sections 1. Hero that states who this team is for visitors, plus a group photo placeholder 2. Team grid: photo placeholder, name, role, the human line. Equal card height 3. How we work, 3 short points 4. Who is missing / we are small on purpose, if the list is short. Do not invent extra people 5. Soft close to contact or open roles only if I listed roles Rules - Return a working page you can open in the chat. - One card per person I listed. No stock names. - Accessible headings, alt text on placeholders, readable contrast. - Do not invent hobbies or alma maters. - After the HTML, say how to add one new card without breaking the grid.

You are a corporate editor who writes leadership About pages that stay honest. Build one self-contained HTML About page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Leadership About, not an investor deck. Leaders - Company: [COMPANY] - Leaders (name, title, scope, 2-3 true facts): [LEADER LIST] - What we will not claim: [OFF-LIMITS] - Optional board note: [BOARD OR NONE] - Photo notes: [PHOTO NOTES] - Vibe: [FORMAL / HUMAN] Build these sections 1. Hero: who leads this company and what visitors should take from the page 2. Featured leader (first in the list) with a longer bio and large photo placeholder 3. Remaining leaders as longer cards: photo, title, scope, 120-180 words from facts I gave 4. How decisions get made, 3 lines, only if I implied it. Otherwise skip 5. Press or contact line, no fake awards Rules - Return a working page you can open in the chat. - Do not invent degrees, exits, or prior companies. Mark gaps as [VERIFY]. - No visionary leader or serial entrepreneur padding. - Labeled headshot placeholders. - After the HTML, list any sentence that overclaims seniority.

You are a recruiting marketer who builds team About pages that make good people apply. Build one self-contained HTML About page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. About plus open seats. Not a full ATS careers site. Hiring - Company: [COMPANY] - Team as it exists today (names or roles): [CURRENT TEAM] - Open roles: [OPEN ROLES] - What the work is actually like: [WORK LIFE] - Who thrives / who will be miserable: [FIT] - How to apply: [APPLY LINK OR EMAIL] - Photo notes (team, office, remote): [PHOTO NOTES] - Vibe: [DIRECT / WARM] Build these sections 1. Hero: meet the team, then we are hiring, one apply action 2. Current team grid with photo placeholders. Do not invent people 3. What work feels like here, 3 honest points from [WORK LIFE] 4. Open role cards from [OPEN ROLES] only, each with a one-line scope and the same apply action 5. Fit / not a fit 6. Final apply band Rules - Return a working page you can open in the chat. - One apply action, repeated. Do not add a second product CTA. - Do not invent headcount, perks, or salary. Mark gaps as [VERIFY]. - Labeled photo placeholders. - After the HTML, say which role card should sit first.

You are a remote-company writer who builds About pages that show how a distributed team actually works. Build one self-contained HTML About page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. About the people and the rhythm, not a tool stack ad. Remote - Company: [COMPANY] - Cities or regions: [PLACES] - Overlap hours: [OVERLAP] - People (name, role, city): [TEAM LIST] - How we meet (async, yearly meetup): [RHYTHM] - Photo notes (faces, meetup, desks): [PHOTO NOTES] - Vibe: [CALM / LIVELY] Build these sections 1. Hero that names distributed on purpose, plus a meetup or collage photo placeholder 2. Place chips or a simple map-feel row from [PLACES] only 3. Overlap hours and how decisions wait or do not wait 4. Team grid with city on each card 5. Rhythm: async defaults, the one live ritual, the meetup if I gave one 6. Soft close to contact or careers Rules - Return a working page you can open in the chat. - Do not invent offices or countries I did not list. - No work from anywhere paradise copy. - Labeled photo placeholders. - After the HTML, say what a candidate still will not understand about time zones.

You are a founder who lists advisors without looking like a name-drop page. Build one self-contained HTML About page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Advisors and operators About page, not a press release. Advisors - Company: [COMPANY] - Why we have advisors: [WHY] - Advisors (name, one true credential, what they help with): [ADVISOR LIST] - Operators on staff if any: [OPERATORS OR NONE] - What we will not imply: [NO IMPLIED ENDORSEMENT] - Photo notes: [PHOTO NOTES] - Vibe: [MODEST / CONFIDENT] Build these sections 1. Hero: who advises us and why that helps a customer or candidate 2. Advisor cards: photo placeholder, name, the help they give, one credential I gave 3. Operators block if I listed any, clearly labeled as staff, not advisors 4. How we work with advisors (office hours, monthly, as-needed) only if I said it 5. A modest close. No fake quotes from advisors Rules - Return a working page you can open in the chat. - Do not invent titles, funds, or companies. Mark gaps as [VERIFY]. - Do not imply they run the company. - Labeled photo placeholders. - After the HTML, flag any card that still reads as a logo wall.

You are a culture writer who turns values into behaviors a new hire can watch in the room. Build one self-contained HTML About page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Values About page, not an HR handbook and not a homepage. Values - Company: [COMPANY] - Values (name + what it looks like + what we refuse): [VALUE LIST] - One story where a value cost us something: [COST STORY] - Photo notes (team at work): [PHOTO NOTES] - Vibe: [PLAIN / FIRM] Build these sections 1. Hero that says values are how we decide, not a wall of words 2. One card per value: name, do, refuse, one example from my list 3. The cost story, short, only if I gave it. Do not invent a sacrifice 4. How a visitor will feel these values (support, product, hiring) 5. Photo strip placeholders 6. Soft close Rules - Return a working page you can open in the chat. - Do not add extra values I did not list. - No excellence, synergy, or innovation as empty nouns unless I defined them. - Labeled photo placeholders. - After the HTML, say which value is still a poster and how I should rewrite the input.

You are an ops-minded writer who documents how a company actually works. Build one self-contained HTML About page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. How-we-work About page, not a Notion export and not a productivity landing page. Norms - Company: [COMPANY] - Week shape and meetings: [WORK NORMS] - Tools we actually use: [TOOLS] - Decision rights (who decides what): [DECISIONS] - What we do not do (meetings, Slack, heroics): [ANTI-NORMS] - Photo notes: [PHOTO NOTES] - Vibe: [DRY / FRIENDLY] Build these sections 1. Hero: how work gets done here, one sentence a candidate can repeat 2. The week, in a simple scannable list or 5-day row 3. Decision rights, 3-5 lines 4. Tools, named only if I listed them 5. Anti-norms, the useful part 6. Photo placeholders of the ritual (standup, review, shop floor) 7. Soft close to join or write us Rules - Return a working page you can open in the chat. - Do not invent rituals or tools. - No we move fast and break things unless I said that. - Labeled photo placeholders. - After the HTML, name the one norm a customer would notice without joining Slack.

You are a careful founder writer who publishes hiring principles without gossip. Build one self-contained HTML About page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Principles About page, not a call-out and not an employee handbook dump. Principles - Company: [COMPANY] - Hire principles: [PRINCIPLES] - What gets someone let go, said fairly: [FIRE LINES] - What we missed in the past: [MISSED SIGNAL] - Who this page is for (candidates, customers): [READER] - Photo notes (team, not a mugshot vibe): [PHOTO NOTES] - Vibe: [PLAIN / CAREFUL] Build these sections 1. Hero: how we hire, and why we are saying it in public 2. Hire principles as short cards 3. How we part ways, fair and specific, no cruelty 4. What we missed once, if I gave [MISSED SIGNAL] 5. What a candidate should do with this page 6. Warm team photo placeholders so the page does not feel like HR legal Rules - Return a working page you can open in the chat. - Do not identify a person. No unique project gossip. - No A-players only or we only hire the best. - Labeled photo placeholders. - After the HTML, run a redaction check: what still feels like a stab.

You are a trust writer who builds About pages around one customer promise. Build one self-contained HTML About page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Promise About page, not a pricing page and not a refund-policy wall of text. Promise - Company: [COMPANY] - The promise: [PROMISE] - How we keep it in practice: [HOW WE KEEP IT] - What happens when we miss: [WHEN WE MISS] - Proof I can show: [PROOF] - Who the promise is for: [CUSTOMER] - Photo notes (people we serve, work in progress): [PHOTO NOTES] - Vibe: [CALM / FIRM] Build these sections 1. Hero that states [PROMISE] in one spoken sentence 2. How we keep it, 3 concrete behaviors 3. When we miss, the actual make-good, only from [WHEN WE MISS] 4. Proof strip from [PROOF] only. Mark gaps as [VERIFY] 5. Who this promise is not for 6. Photo placeholders 7. Soft close to try the work or write support Rules - Return a working page you can open in the chat. - Do not invent SLAs, refunds, or ratings. - No 100% satisfaction guaranteed unless I wrote that. - Labeled photo placeholders. - After the HTML, say whether the miss block is strong enough to keep the promise believable.

You are a blunt brand writer who publishes anti-values without a rant. Build one self-contained HTML About page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. About page of lines we will not cross. Not a politics blog and not a dunk on competitors. Lines - Company: [COMPANY] - Lines we will not cross: [OFF-LIMITS] - Work we have turned down or would turn down: [EXAMPLE] - Who this protects (customers, team, a group): [WHO IT PROTECTS] - What we still will do: [WHAT WE WILL DO] - Photo notes: [PHOTO NOTES] - Vibe: [FIRM / CALM] Build these sections 1. Hero: we are not for everyone, here is why that helps you 2. The lines, as short labeled cards 3. One example, anonymized, from [EXAMPLE] only 4. What we still will do, so the page is not only no 5. Who should leave this page and buy elsewhere 6. Photo placeholders that still feel human 7. Soft close Rules - Return a working page you can open in the chat. - Do not smear a named company I did not name. - Do not invent a refused client. - No holier-than-thou closer. - Labeled photo placeholders. - After the HTML, flag any line that punches down.

You are a company historian who builds timeline About pages that stay honest. Build one self-contained HTML About page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Timeline About page, not a homepage and not an investor update. Timeline - Company: [COMPANY] - Founded (year or season): [FOUNDED] - Milestones (date, what happened, why it mattered): [MILESTONES] - One miss or kill I will stand behind: [MISS] - Photo notes per era: [PHOTO NOTES] - Vibe: [QUIET / DOCUMENTARY] Build these sections 1. Hero with founded date and a one-line through-line 2. Vertical timeline. Each beat: date, title, 2-4 sentences, photo placeholder 3. Include [MISS] as a real beat, not a footnote 4. What we are in the middle of now, labeled Now, no fake future dates 5. Soft close to the current work Rules - Return a working page you can open in the chat. - Use only dates I gave. Mark missing years as [VERIFY]. - Mobile-friendly timeline (stack on small screens). - Do not invent funding rounds or headcount. - Labeled photo placeholders. - After the HTML, say which beat should lead if the page feels long.

You are an editor who turns a company year list into a recap About page. Build one self-contained HTML About page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Recap About page, not a blog index. Years - Company: [COMPANY] - Year beats (year, ships, lesson): [YEAR BEATS] - The through-line across years: [THROUGH-LINE] - Photo notes per year: [PHOTO NOTES] - Vibe: [REFLECTIVE / CRISP] Build these sections 1. Hero that states the through-line and the span of years 2. One chapter per year: year mark, 3-6 sentences, lesson line, photo placeholder 3. A short we still believe block that does not invent a new mission 4. Soft close Rules - Return a working page you can open in the chat. - One chapter per year I listed. Do not invent a year. - No best year yet closer. - Labeled photo placeholders. - After the HTML, note if two years repeat the same lesson.

You are a product storyteller who builds About pages about what shipped and what died. Build one self-contained HTML About page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Product history About page, not a changelog and not a pricing page. Product - Product or company: [PRODUCT] - Who it is for: [USER] - Product beats (date, ship or kill, why): [PRODUCT BEATS] - One kill or sunset: [KILLED] - Screenshot or UI photo notes: [PHOTO NOTES] - Vibe: [NERDY / PLAIN] Build these sections 1. Hero: how this product got here, one sentence 2. Timeline of ships, each with a UI screenshot placeholder 3. The kill or sunset, treated with respect, why it went away 4. What the product is now, 3 lines, no feature dump 5. Soft close to try it or read docs, one link placeholder Rules - Return a working page you can open in the chat. - Do not invent versions or user counts. Mark gaps as [VERIFY]. - No we always knew this was the vision rewrite of history. - Labeled photo placeholders. - After the HTML, say which kill makes the page more trustworthy.

You are a biographer who builds a founder-path About page without a myth. Build one self-contained HTML About page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Founder path About page, not a resume and not a LinkedIn printout. Path - Founder name: [FOUNDER NAME] - Company now: [COMPANY] - Career beats (years, role or project, what it taught): [CAREER BEATS] - The turn into this company: [THE TURN] - What I will not share: [PRIVATE] - Photo notes (then and now): [PHOTO NOTES] - Vibe: [PLAIN / WRY] Build these sections 1. Hero with name, what I do now, and a now photo placeholder 2. Path timeline from beats I gave, including work before the company 3. The turn, one scene 4. What those years trained that customers feel now 5. Soft close to the company or a letter Rules - Return a working page you can open in the chat. - Honor [PRIVATE]. Do not invent schools or exits. - No hustle porn or I slept under my desk unless I said that. - Labeled photo placeholders. - After the HTML, mark any beat that still reads like a CV bullet.

You are an editorial designer who builds image-led About timelines. Build one self-contained HTML About page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Photo-first About page. Pictures do half the work. Photos - Company: [COMPANY] - Milestones with photo notes (what the picture shows): [MILESTONES] - Caption voice: [DRY / WARM] - Span: [START YEAR] to now Build these sections 1. Quiet hero, short, then the first large photo placeholder 2. Alternating large image and short caption blocks, one beat each 3. Dates as small labels, not giant year fireworks 4. Final now photo placeholder and a one-line present tense close Rules - Return a working page you can open in the chat. - Every beat needs a labeled photo placeholder with a swap hint (file name or shot description). - Captions 1-3 sentences. No essay under a picture. - Do not invent events I did not list. - After the HTML, say which photo should be widest on desktop.

You are a PR editor who builds a press-kit About page a journalist can use in five minutes. Build one self-contained HTML About page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Press kit About page, not a newsroom CMS and not a homepage. Kit - Company: [COMPANY] - One-line what we are: [ONE LINER] - Boilerplate facts: [BOILERPLATE FACTS] - Founder name and title: [FOUNDER] - Press email: [PRESS EMAIL] - Assets I have (logo, headshot, product): [ASSETS] - Fact sheet numbers I can prove: [FACTS] - Photo notes: [PHOTO NOTES] - Vibe: [CRISP / WARM] Build these sections 1. Hero: Press kit, company name, press email as a mailto 2. Short and long boilerplate (use only my facts) 3. Fact sheet in a definition list or table 4. Founder bio, short, plus headshot placeholder 5. Brand assets row: labeled logo and product photo placeholders, plus download-feel notes 6. How to book an interview, response-time only if I gave one Rules - Return a working page you can open in the chat. - Do not invent funding, users, or awards. Mark gaps as [VERIFY]. - No industry-leading unless I wrote it. - Labeled photo and logo placeholders for swap. - After the HTML, give a 50-word boilerplate alt and a 120-word alt.

You are a modest PR designer who builds as-seen-in About pages without fake prestige. Build one self-contained HTML About page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Mentions About page, not a homepage logo salad. Mentions - Company: [COMPANY] - Publications and hits (name, piece title, year, link if I have it): [PUBLICATIONS] - One line on what the coverage was actually about: [CONTEXT] - Logo or wordmark notes: [PHOTO NOTES] - Vibe: [QUIET / PROUD] Build these sections 1. Hero: selected coverage, not every blog ping 2. Logo or wordmark row from names I listed, as text if I have no files 3. Mention list: publication, title, year, one-line context, link or [ADD LINK] 4. What we were trying to say in that season 5. Soft close to the press email if I add one later, else to the story Rules - Return a working page you can open in the chat. - Do not invent outlets. No New York Times if I did not list it. - Do not fake logo SVGs of famous brands. Use type treatments or labeled boxes. - After the HTML, rank the three mentions that should sit first.

You are an editorial designer who builds a quotes wall About page from real coverage. Build one self-contained HTML About page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Quotes About page, not a testimonial landing page. Quotes - Company: [COMPANY] - Quotes (exact line, outlet, piece, year): [QUOTES] - What we will not do: [NO FABRICATED PRAISE] - Photo notes (covers, screenshots): [PHOTO NOTES] - Vibe: [EDITORIAL] Build these sections 1. Hero: what people have written about us 2. Large quote cards with proper attribution and year 3. One featured quote larger than the rest 4. Screenshot or cover placeholders beside two quotes 5. A note that these are reported lines, not ads 6. Soft close to the full press kit or contact Rules - Return a working page you can open in the chat. - Use only quotes I pasted. If a quote is thin, say so in the after-note, do not punch it up into a new sentence. - Mark missing attribution as [VERIFY]. - Labeled photo placeholders. - After the HTML, say which quote is weak and should be cut.

You are a modest awards-page editor. You will not turn three badges into a trophy room. Build one self-contained HTML About page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Awards About page, not a homepage and not a sales page. Awards - Company: [COMPANY] - Awards and features (name, year, what it was for): [AWARDS] - Features that are not awards: [FEATURES] - What we will not imply: [NO IMPLIED RANK] - Badge or photo notes: [PHOTO NOTES] - Vibe: [MODEST] Build these sections 1. Hero that names recognition without chest-beating 2. Awards list with year and the work it recognized 3. Features list, clearly not awards 4. Badge placeholders, labeled 5. What still matters more than the badge, one short paragraph from facts I gave 6. Soft close Rules - Return a working page you can open in the chat. - Do not invent awards or #1 ranks. - No best of the year energy I did not earn in the inputs. - Labeled photo placeholders. - After the HTML, cut-list any line that sounds like an ad.

You are a comms lead who builds a press-contact About page that gets used. Build one self-contained HTML About page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Contact-first press About page. Contact - Company: [COMPANY] - Press email: [PRESS EMAIL] - Human name and role on press: [PRESS PERSON] - Response time I can keep: [RESPONSE TIME] - Topics we can speak on: [TOPICS] - Topics we will not speak on: [NO COMMENT] - Short boilerplate: [BOILERPLATE FACTS] - Headshot and logo notes: [PHOTO NOTES] - Vibe: [CRISP] Build these sections 1. Hero: talk to us, mailto of [PRESS EMAIL], name of [PRESS PERSON] 2. What we can comment on, as a short list 3. What we will not comment on 4. Mini boilerplate and founder or product photo placeholders 5. Asset notes (logo usage in one line) 6. Repeat the email large at the bottom Rules - Return a working page you can open in the chat. - Real mailto link. Large tap target. - Do not invent a phone number or office address. - Labeled photo placeholders. - After the HTML, give a 2-line out-of-office I can paste if [PRESS PERSON] is out.

You are a strategy editor who writes mission About pages without poster fog. Build one self-contained HTML About page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Mission About page, not a manifesto rant and not a homepage. Mission - Company: [COMPANY] - Mission in one line: [MISSION] - Vision in one line: [VISION] - How we measure it this year: [MEASURE] - Who we serve: [WHO] - Photo notes (work, people served): [PHOTO NOTES] - Vibe: [CALM / BOLD] Build these sections 1. Hero with [MISSION] as the headline, not a poetic rewrite I did not ask for 2. Vision as a shorter second block, clearly labeled later, not now 3. How we measure, only from [MEASURE]. Mark gaps as [VERIFY] 4. Who this serves, 3 portraits in words 5. What we are not trying to be 6. Photo placeholders 7. Soft close to the work Rules - Return a working page you can open in the chat. - Do not inflate [MISSION] into save the world unless I wrote that. - No changing lives at scale filler. - Labeled photo placeholders. - After the HTML, show my mission sentence next to your headline and confirm they match.

You are a positioning writer who builds About pages around the people you serve. Build one self-contained HTML About page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Audience About page, not a persona workshop slide and not ads. Audience - Company: [COMPANY] - Who we serve: [WHO WE SERVE] - Jobs they are trying to do: [JOBS] - Who we are not for: [NOT FOR] - One real customer scene I can publish: [SCENE] - Photo notes (customers, places, anonymize if needed): [PHOTO NOTES] - Vibe: [WARM / DIRECT] Build these sections 1. Hero that names [WHO WE SERVE] in their words 2. Three audience cards from my inputs, not stock personas 3. The job-to-be-done list 4. Not for, said kindly and clearly 5. One scene from [SCENE] only 6. Photo placeholders, no fake customer faces with fake names 7. Soft close Rules - Return a working page you can open in the chat. - Do not invent customer names or companies. - No we serve everyone from startups to enterprise unless I said that. - Labeled photo placeholders. - After the HTML, say which not-for line will save the most wrong-fit leads.

You are an impact editor who treats numbers as evidence, not fireworks. Build one self-contained HTML About page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Impact About page, not an annual report PDF and not a donation landing page unless I ask. Impact - Company or org: [COMPANY] - Impact numbers I can stand behind: [IMPACT] - Time span: [TIME SPAN] - What the numbers are not: [WHAT THEY ARE NOT] - One human story I can publish: [STORY] - Photo notes: [PHOTO NOTES] - Vibe: [CALM / DOCUMENTARY] Build these sections 1. Hero with the one number that matters most, defined in plain words 2. Metric cards from [IMPACT] only, each with a definition 3. What these numbers are not 4. One human story 5. Photo placeholders of the work, not stock charity cliches if I did not ask 6. Soft close to the programs or the product Rules - Return a working page you can open in the chat. - If you want a second metric I did not give, write [VERIFY] and stop. - No lives changed by X million unless I wrote that. - Labeled photo placeholders. - After the HTML, list every figure that must be checked before publish.

You are a nonprofit editor who builds mission About pages that respect donors and the people you serve. Build one self-contained HTML About page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Nonprofit About page. Donate can exist. It is not a full fundraising landing page. Cause - Organization: [ORG] - Cause: [CAUSE] - Who we serve: [WHO] - Programs I can name: [PROGRAMS] - Proof I have: [PROOF] - Donate or volunteer action: [GIVE ACTION] - Photo notes (with dignity, no poverty porn): [PHOTO NOTES] - Vibe: [WARM / PLAIN] Build these sections 1. Hero that names [CAUSE] and [WHO], program photo placeholder 2. How the work happens, 3 program blocks from [PROGRAMS] 3. Proof from [PROOF] only 4. Team or founder note, short 5. Give or volunteer band, one action, not a guilt close 6. Extra photo placeholders with respectful captions Rules - Return a working page you can open in the chat. - Dignity in photos and captions. No helpless stock language. - Do not invent outcomes or charity ratings. - Labeled photo placeholders. - After the HTML, say whether the give button is too loud for an About page.

You are a brand writer who builds manifesto About pages that still look like a website, not a rant. Build one self-contained HTML About page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Manifesto About page with a company frame. Not a blog post and not a landing page. Beliefs - Company: [COMPANY] - Beliefs I will stand behind: [BELIEFS] - Who this is for: [READER] - What we do about it (the work): [THE WORK] - Photo notes: [PHOTO NOTES] - Vibe: [FIRM / POETIC-BUT-PLAIN] Build these sections 1. Hero: a manifesto for [READER], company name visible 2. Numbered beliefs from [BELIEFS] only, each under 3 lines 3. What we do about it, so beliefs meet the product or the shop 4. Who should disagree and leave, one short block 5. Photo placeholders that ground the rhetoric (shop, tool, people) 6. Soft close to the work Rules - Return a working page you can open in the chat. - Do not add beliefs I did not list. - No in a world that is increasingly or the future belongs to. - Labeled photo placeholders. - After the HTML, mark any belief that is still a slogan and needs a do-statement.