Publishing — Brickfolio HTML
Brickfolio’s HTML edition is a folder of static files: replace the demo’s person and work with yours, point the two forms at your service, then upload the folder to any web host.
Before you upload
Section titled “Before you upload”| Where | |
|---|---|
Your domain instead of https://brickfolio-html-framebrick.vercel.app |
Every page’s <head>, sitemap.xml, robots.txt (find and replace in files, Editing the site) |
| Your titles and descriptions (Home’s describes the template) | Each page’s <head> |
| Your name and photo instead of Javier Martinez’s: the profile card, the greeting, the roles | index.html (Editing the site) |
| Your name instead of “Brickfolio”: the logo, the titles, the copyright line | Search the folder for “Brickfolio” |
The “Email me” address (hello@example.com is a placeholder) and the social links (they open the networks’ home pages) |
index.html |
| Your projects, services, posts, testimonials, experience, client logos and questions | index.html, project/, blog/ |
| Your CV | cv.pdf |
| Placeholder photos and icons replaced | assets/images/, icon.png, apple-icon.png |
| The two forms deliver to you | assets/js/config.js (Forms) |
| A privacy page, if your country asks for one (the forms collect names, e-mails and phone numbers) | Editing the site |
| The style guide kept or deleted | style-guide.html |
Leaving the sample person, the sample e-mail, the sample testimonials or the sample CV on a live site is the most common mistake: search the folder for “Javier”, “example.com” and the title of a demo project one last time.
What to upload
Section titled “What to upload”Everything except the tools and the documentation:
| Upload | Leave out |
|---|---|
The .html pages, project/, blog/ |
node_modules/, src/, docs/ |
assets/, cv.pdf |
package.json, package-lock.json |
icon.png, apple-icon.png |
README.md, CHANGELOG.md, LICENSE.md |
sitemap.xml, robots.txt |
Documentation.html, Documentation.pdf |
Uploading the extra files does no harm, but there is no reason to publish them.
Where to host
Section titled “Where to host”| Host | How |
|---|---|
| Netlify | Drag the folder onto Netlify Drop. Done; then add your domain. |
| Cloudflare Pages, Vercel | Upload the folder or connect a Git repository; no build command, the output folder is the root. |
| GitHub Pages | Push the folder to a repository and enable Pages. |
| Shared hosting (cPanel, Plesk…) | Upload through the file manager or FTP into public_html (or www). |
Pages link to each other with their file names (index.html#contact, project/ecoshop-sustainable-e-commerce-platform.html),
so no server configuration is needed. Most hosts serve 404.html for unknown addresses automatically; on Apache, add
ErrorDocument 404 /404.html to .htaccess. The paths in 404.html start at the site’s root
(/assets/css/style.css, /index.html), because hosts show it at any address: if your site lives in a sub-folder of its
domain (example.com/portfolio/, or a GitHub Pages project site), add that folder to those paths.
If you deploy with Vercel from this folder, the included vercel.json holds "git": { "deploymentEnabled": false }
(how the demo is deployed): delete that entry if you want each push to your repository to publish the site.
Your domain
Section titled “Your domain”Add it in the host’s domain settings and point your DNS where they tell you (usually an A record or a CNAME). Turn
on HTTPS: every host above does it for free.
After it is live
Section titled “After it is live”- Check the pages. Click through every page on a phone and a laptop:
- the header’s links from Home and from a project page, and the phone menu;
- “More Projects” and “More Posts”, a project and a post with their close buttons;
- “Download CV”, the questions, the tickers;
- the 404 page (open an address that doesn’t exist).
- Send the contact form and sign up to the newsletter yourself and check that both arrived.
- Verify the share cards. Paste the URL of the home page and of a project into https://www.opengraph.xyz or a chat
window, and confirm the title and description (and the project’s cover). Home has no share image, as in the original
design: to add one, put
og:image,og:image:altandtwitter:imagetags inindex.htmlas a project page has them, and settwitter:cardtosummary_large_image. - Tell Google. Add the site to Search Console, verify ownership and
submit
https://yourdomain.com/sitemap.xml. Bing has the same thing in Webmaster Tools. - Analytics, if you want it. Paste your snippet before
</head>in every page (find and replace on</head>does it at once), or use your host’s built-in analytics (Cloudflare Web Analytics, Plausible, Fathom). None of them need a cookie banner. - Keep it current. Add projects and posts as described in Editing the site, and keep
sitemap.xmlin step.