Web hosting for academics and researchers

Build a personal academic website for me. I am a [PhD student / postdoctoral researcher] and I will use the site when applying for [faculty positions / postdocs / industry research roles].

About me:
- Name: [Full Name], pronouns [optional], [PhD candidate in X / Postdoc] at [Department, University, City, Country], advised by [Advisor name]
- Expected completion or current contract end: [month year]; on the job market: [yes, from month year / no]
- Research in two plain sentences: [e.g. I study how proteins fold using cryo-EM data and geometric deep learning. My work makes low-resolution maps usable for drug discovery.]
- Research themes with one line each: [theme 1; theme 2; theme 3]
- Publications: [paste my BibTeX here, including any code, data, slides or pdf fields]
- Selected papers to feature on the homepage: [keys of 3 entries]
- Talks and posters: [title, event, year, link to slides or recording]
- Teaching and mentoring: [course, role, term; students mentored]
- Awards, fellowships, service: [list with year and awarding body]
- Education: [degree, institution, year, thesis title]
- Links: email [email], ORCID [URL], Google Scholar [URL], GitHub [URL], LinkedIn or Bluesky [URL]
- Photo: images/portrait.jpg

Pages:
1. index.html: my name and position as the H1, the two-sentence research description, my photo, the three featured papers with one line each on why they matter, a short "News" list I will edit by hand (paper accepted, talk given, award), and the links above. If I am on the job market, a short dated notice near the top that says what I am looking for and links to my CV and research statement.
2. research.html: one section per theme with the question, the approach, the key result so far and the papers that belong to it, each linking to its paper page.
3. publications.html: all entries grouped by year, newest first, each with authors (my name in bold), title, venue, year, and links for DOI, arXiv, code, data, slides and PDF only where I gave them, plus a "BibTeX" toggle showing the entry I gave. Mark preprints as preprints.
4. papers/[key].html for every entry: title, authors, venue, abstract (I will paste abstracts; leave [EDIT] where missing), links, figures I supply, the BibTeX, and the Google Scholar meta tags described in the technical requirements. Make the first one complete and copy the pattern for the others.
5. cv.html: a full CV from the details above, in sections (Education, Positions, Publications, Talks, Teaching, Awards, Service, Skills), with a "Last updated" date and a print stylesheet so it saves cleanly as a PDF from the browser.
6. research-statement.html: a 600-word research statement drafted from my descriptions with [CHECK] marks on every claim I should verify; I will rewrite it.
7. teaching.html, talks.html and contact.html.

Design: quiet and scholarly. White, one deep [blue / green / plum] accent, a readable serif for headings and a sans-serif for text, generous margins, hanging indents in the publication list. No stock photos of microscopes or chalkboards, no particle backgrounds.

Build a personal website for me. I am a faculty member.

About me:
- Name: [Full Name], [Assistant / Associate / Full Professor of X] at [Department, University, City, Country], with affiliations to [centres or institutes, optional]
- Research in two plain sentences: [what I study and why it matters]
- Research themes with one line each: [theme 1; theme 2; theme 3]
- Publications: [paste my BibTeX here]; selected papers to feature: [keys of 5 entries]
- Group: [name of my lab or group, link to its site if separate; current members with role and year; alumni with current position]
- Supervision: [I am / am not taking PhD students for [year]; postdoc openings: [yes/no]; what I expect in a first email; funding routes]
- Grants and projects: [title, funder, years, role; only ones I may publish]
- Teaching: [course code and name, term, link to course site]
- Service and editorial roles: [list]
- Talks: [title, event, year, slides or video link]
- Press and outreach: [article or podcast, outlet, year, link; only real ones]
- Education and previous positions: [list]
- Links: email [email], office [building and room, optional], ORCID [URL], Google Scholar [URL], GitHub [URL], LinkedIn [URL]
- Photo: images/portrait.jpg

Pages:
1. index.html: name and position as the H1, the two-sentence research description, my photo, five featured papers, a dated "Taking students" or "Not taking students" line that links to the Join page, a News list I edit by hand, and the links above.
2. research.html: a section per theme with the question, the approach, the key results and the papers behind them.
3. publications.html: all entries grouped by year, newest first, authors with my name in bold, venue, links only where I gave them, a BibTeX toggle per entry, and a filter by year and by member of my group (match co-author names I listed under Group).
4. papers/[key].html for every entry, with the Google Scholar meta tags in the technical requirements. Make the first one complete and copy the pattern.
5. group.html: current members with photo, role and research line; alumni with their next position; how the group works (meetings, mentoring, expectations), and the funding acknowledgements I listed.
6. join.html: whether I am taking students and postdocs, the admission route at my university, funding, what to include in a first email, and a "Prospective student" form (see the technical requirements) or a mailto link if I said no form.
7. teaching.html, talks.html, cv.html with a print stylesheet and a "Last updated" date, and contact.html.

Design: assured and plain. White with a deep [colour] accent and one warm secondary colour, serif headings, sans-serif text, real photos of me and the group, figures from my papers used as section openers with captions and credit. No stock imagery, no animated hero.

Build a website for my research group.

About the group:
- Name: [Lab name], led by [PI name and title], at [Department, University, City, Country], founded [year]
- What we study, in two plain sentences: [the question and why it matters]
- Research areas with one line each: [area 1; area 2; area 3]
- Current projects: [name, one-line goal, people, funder and grant number if I may publish it, start year; for each]
- People: [name, role (PI, postdoc, PhD student, master's student, RA, visitor), start year, one research line, website or email; photo file name; for each]
- Alumni: [name, role here, years, current position and employer; for each]
- Publications: [paste the group's BibTeX]
- Software and datasets: [name, one line, repository or DOI link, license, citation; for each]
- Openings: [position, start date, funding, requirements, deadline, how to apply; or "none at present"]
- Values and how we work: [meetings, mentoring, code of conduct, open science practices]
- Funders and partners I may name: [list]
- Contact: email [email], address [building, room, postal address], map link [URL]
- Social: [GitHub organisation, Bluesky, LinkedIn, YouTube]

Pages:
1. index.html: lab name and what we study as the H1, the two-sentence description, one strong figure or photo I supply, three current projects, latest three news items (I edit these by hand), the openings notice if any, and funder names as text.
2. people.html: current members grouped by role with photo, name, role, start year and research line; alumni as a table with years and current positions.
3. projects/[slug].html: one per project with goal, approach, people, publications, software and data, funder and partners; make the first complete and copy the pattern.
4. publications.html: grouped by year, newest first, with group members' names in bold, links only where I gave them, a BibTeX toggle per entry, and filters by year, project and member.
5. papers/[key].html for every entry, with the Google Scholar meta tags in the technical requirements.
6. software.html: each tool and dataset with description, link, license, how to cite (BibTeX and a plain citation) and the paper it belongs to.
7. join.html: openings with deadlines and how to apply, what we expect in a first email, how PhD admission and funding work at our university, and a "Join us" enquiry form (see the technical requirements) or a mailto link if I said no form.
8. news.html: a dated list, newest first, that I edit by hand.
9. contact.html with a map that loads only after a click, and privacy.html.

Design: a lab, not a start-up. White with the [colour] of our figures as the accent, serif headings, sans-serif text, a simple wordmark for the lab, photos of real people and real experiments. No abstract molecule stock art, no gradient blobs.

Build a public website for a university course I teach.

About the course:
- Code and title: [e.g. CS 371: Introduction to Machine Learning], [term and year], at [Department, University]
- Instructor: [name, email, office hours, office or video link]; teaching assistants: [names, emails, office hours]
- Meeting times and room: [days, time with time zone, room or online link]
- Description in two sentences: [what the course covers and who it is for]
- Prerequisites: [list]
- Learning outcomes: [4 to 6 lines]
- Grading: [components with weights]
- Policies: [late work, collaboration, academic integrity, AI tools, accommodations contact; paste the university's required text where there is one]
- Schedule: [week number, date, topic, readings, assignment due; for each week]
- Materials: [textbook or free resources, software to install, links]
- Where graded work lives: [LMS name and link, e.g. Moodle / Canvas]
- Past exams or sample problems I may publish: [links or "none"]

Pages:
1. index.html: course code and title as the H1, term, instructor and TAs with office hours, meeting times, the description, and the next three deadlines pulled from the schedule as a list I will edit by hand.
2. syllabus.html: description, prerequisites, outcomes, grading, policies and the required university text in full.
3. schedule.html: the week-by-week table with topic, readings, slides and notes links, and assignment due dates; make the current week easy to spot with a highlight I can move by changing one class name.
4. lectures/[n].html: one page per lecture with the topic, a summary, links to slides and notes, and the readings; make the first complete and copy the pattern.
5. assignments.html: each assignment with release and due dates, a short description, the rubric, and a link to the LMS for submission. No submissions through this site.
6. resources.html: textbooks, tools, tutorials and past exams.
7. faq.html: 10 questions students ask every term (late policy, regrades, collaboration, AI use, what to bring to the exam), answered plainly.

Design: clear and calm. White, one [colour] accent, a sans-serif throughout, tables that work on a phone, 17 to 18px text, high contrast. Dates always with the day of the week. No decorative images.

Accessibility matters more than usual: this must work with a screen reader and at 200% zoom.

Build a website for an academic [conference / workshop / summer school].

About the event:
- Name and edition: [e.g. Workshop on X, 3rd edition], part of [parent conference, or "standalone"]
- Dates and place: [dates, venue name, city, country, time zone]; format: [in person / hybrid / online]
- One-line scope: [what the event is about and who should come]
- Organisers: [name, affiliation, role; for each]; program committee: [names and affiliations]
- Invited speakers: [name, affiliation, talk title if known, photo file name; for each]
- Call for papers: [topics, submission types and page limits, review process, publication of accepted work, submission system link]
- Important dates: [submission deadline, notification, camera-ready, registration deadline, event dates; all with time zone]
- Registration: [fees by category, link to the registration system, what it includes]
- Program: [sessions with times, titles and speakers, or "to be announced"]
- Venue and travel: [address, how to get there, hotels, visa letter process, accessibility of the venue]
- Code of conduct: [paste or name the one you adopt]
- Sponsors I may name: [list with logo files]
- Past editions: [year, place, link to proceedings or site; for each]
- Contact: [email]; social: [URLs]

Pages:
1. index.html: event name and dates as the H1, place and format, the scope, the next upcoming deadline from the important dates as a dated notice I will edit by hand, invited speakers with photos, and sponsor logos as text if I did not supply logos.
2. call-for-papers.html: topics, submission types, review process, publication, and the submission link.
3. dates.html: the important dates as a table with time zone, and an "Add to calendar" .ics file for the event dates.
4. program.html: the schedule as a table per day with times in the venue time zone and a note on converting; a printable version through a print stylesheet.
5. speakers.html, organisers.html, registration.html (link out; never collect payment on this site), venue.html with a map that loads only after a click, code-of-conduct.html, past.html and privacy.html.

Design: legible from a phone in a hallway. White with one [colour] accent, a sans-serif throughout, dates and times set large, tables that scroll on small screens. No countdown timers, no autoplaying video.

Keep every page working after the event: add a past-event note at the top and keep the program and proceedings links live, because people cite them.

Build a project website for a piece of research [software / dataset / benchmark].

About the project:
- Name: [Project name], one-line description: [what it does and for whom]
- Maintainers: [name, affiliation, role; for each]; contributors I may name: [list]
- Repository: [GitHub or GitLab URL]; documentation: [URL, or "on this site"]; package: [PyPI / CRAN / conda name, or "none"]
- Archived release with DOI: [Zenodo or figshare DOI]; license: [license name]
- The paper: [BibTeX of the paper that describes it, and the DOI]; preferred citation text: [plain citation]
- Quick start: [install command, a 5-line example, expected output]
- Key features or dataset contents: [4 to 6 lines; for a dataset: size, format, splits, collection method, licensing of the source data, known limitations]
- Who uses it: [papers or groups that have used it, only ones I can link]
- Versions: [version, date, one line of changes; for each]
- Funding: [funder and grant number, if I may publish it]
- Contact and support: [issue tracker link, mailing list, email]

Pages:
1. index.html: project name and the one-line description as the H1, the quick start in a code block with a copy button, three key features, a "Cite this" box with the BibTeX and the plain citation and a copy button, the DOI badge as text and a link, license and the repository link.
2. docs.html (if documentation is on this site): installation, usage with examples, configuration, and a troubleshooting FAQ, with a table of contents.
3. data.html (for a dataset): a datasheet with motivation, composition, collection process, preprocessing, uses, distribution, maintenance and known limitations, following the Datasheets for Datasets structure; download links go to the archived DOI, not to files on this site.
4. changelog.html: versions newest first.
5. used-by.html: papers and projects that use it, with links.
6. team.html, citation.html with CITATION.cff content shown as text, and contact.html.

Design: a tool, not a brochure. White with one [colour] accent, a monospace face for code and version numbers, a sans-serif for text, no hero image. Code blocks with a visible copy button and a dark background that keeps AA contrast.

Never invent download counts, stars, users or citations.

Technical requirements:
- Output index.html and every extra page I asked for as complete files, with all CSS in a <style> tag and only a little vanilla JavaScript. No frameworks, no build step, no external libraries. If I need equations, write them in MathML and ask me before adding anything from a CDN.
- Mobile-first and responsive from 360px wide. Tap targets at least 44px. The main action I named (for example "Join us" or "Download") appears in the header and at the end of the relevant pages.
- Accessible: semantic HTML, one H1 per page, alt text on every image (figures get a one-sentence description of what they show), visible focus styles, AA colour contrast, a 17 to 18px base font, tables with real <th> headers and a caption, no autoplay audio or video.
- Fast: a system font stack or at most one web font with font-display: swap, width and height on every image, and loading="lazy" on images below the first screen. Don't add srcset; my host generates image sizes.
- Publications: group by year, newest first. For each entry show authors with my name in bold, title, venue, year, and links for DOI, arXiv, code, data, slides, video and PDF only where I gave them. Add a "BibTeX" toggle that shows the exact entry I gave. Never invent a paper, venue, co-author, citation count, h-index, award or affiliation. Mark anything you could not take from my input with [CHECK].
- Paper pages: one page per entry at papers/[key].html with the title as H1, authors, venue, abstract, links, figures and BibTeX, plus these meta tags in the head for Google Scholar: citation_title; one citation_author per author as "Last, First"; citation_publication_date as the year; citation_journal_title for articles or citation_conference_title for proceedings; citation_volume, citation_issue, citation_firstpage and citation_lastpage where I gave them; citation_doi; citation_arxiv_id for preprints; citation_dissertation_institution for theses; citation_pdf_url only for a pdf field I gave. Add ScholarlyArticle JSON-LD with the same data.
- CV: cv.html with a "Last updated" date and a print stylesheet (no header or footer, black text, page breaks avoided inside sections) so it saves as a PDF from the browser.
- Forms, if I asked for one: a standard HTML <form> with method="POST" and a name attribute on every field. Prospective student or Join us form: name, email, current institution and degree, intended start (dropdown), research interests (one field, 600-character limit), link to CV (URL field, no uploads). Contact form: name, email, message. Add a required consent checkbox linking to privacy.html on every form. No file uploads.
- Embeds: a talk video or a map loads only after a click on a preview, never when the page opens, with a plain link as the fallback.
- Claims: use only the details, publications, people, funders, logos and press I gave you, word for word where they are quotes. No "as featured in" badges, no invented testimonials, no rankings.
- SEO: a title under 60 characters with my name (or the lab, course or event name), position and institution; a meta description under 160 characters; an H1 that names what I study or what the site is; Open Graph and Twitter card tags with a 1200 x 630 image; a canonical link to https://[yourdomain.org]/; a "Last updated" date on research, people and CV pages.
- Structured data (JSON-LD): Person for me (or for each member) with name, jobTitle, affiliation as an Organization with name and url, image, url, email, sameAs (ORCID, Google Scholar, GitHub, LinkedIn), knowsAbout, alumniOf and hasCredential for degrees; Organization for a lab; ScholarlyArticle on paper pages; Course on a course site; Event with startDate, endDate, location and organizer on a conference site; SoftwareSourceCode or Dataset on a project site, with license, codeRepository and citation; Article with author and dateModified on posts; FAQPage for any FAQ; BreadcrumbList on inner pages. No Review or AggregateRating markup.
- Use relative links and paths such as images/portrait.jpg so the site works on any domain.
- Mark every piece of placeholder text I still need to replace with [EDIT].
- Give me each file in its own code block, then list the images I need with file names and sizes (portrait 800 x 1000, square headshot 400 x 400 for author bios and people pages, figures at their native size up to 1600px wide, Open Graph image 1200 x 630).