Brickfolio documentation — HTML
Everything you need to go from the downloaded HTML folder to a published portfolio, in the order to read it.
| Guide | What it covers |
|---|---|
| Editing the site | Opening the site, editing text, links and images, the blocks that repeat, the profile card, the tickers, adding and removing projects, posts and pages |
| Pages | Every kind of page, its sections with a map of each, where its text and photos are, and how the pages link to each other |
| Design | Colours, the logo and icons, the fonts, the Tailwind classes, rebuilding the stylesheet, the style guide and motion |
| Forms | Making the contact form and the newsletter box deliver to you |
| Editing without touching HTML | Your options when someone else needs to edit the site without touching HTML |
| Publishing | Pre-launch checklist, uploading, domains, what to do after launch |
| Troubleshooting and questions | Errors, questions and answers |
In a hurry: the first 15 minutes
Section titled “In a hurry: the first 15 minutes”- Open
index.htmlin your browser. That is the whole site: no install, no build. - Open the folder in a code editor (VS Code is a good free one).
- Replace the demo domain across all files with your editor’s find and replace in files (Editing the site), then search for “Javier” and “Brickfolio” to put your own name in the profile card, the logo, the titles and the footer.
- Write your texts, testimonials, experience and questions in
index.html, and replacecv.pdfwith your CV. - Replace the photos in
assets/images/: keep the file names and every page picks them up (Editing the site), and the iconsicon.pngandapple-icon.png. - Put your form endpoint in
assets/js/config.js(Forms). - Upload the folder to your host (Publishing).
How this template is put together
Section titled “How this template is put together”- One HTML file per page.
index.htmlis Home with every section; each project and post has its own file inproject/andblog/(Pages). - One stylesheet.
assets/css/style.css, built fromsrc/css/style.csswith Tailwind CSS. You only rebuild it when you use a class that isn’t in the site yet, or change the theme (Design). - One script.
assets/js/main.jsruns the phone menu, the rotating roles, the tickers, the service cards, the social links, the questions, “More Projects” / “More Posts” and the two forms. You rarely need to touch it: your settings go inassets/js/config.js. - Copies, not references. A block that shows on several pages (the header, the footer, a project’s or a post’s card) is written into each of them. Change every copy, or use find and replace in files (Editing the site).
- No framework, no dependencies at runtime. The pages work from any static host, and even straight from disk.
A portfolio changes slowly, and in this edition a new project or post is a handful of edits by hand. If you will publish often, choose the Brickfolio Astro or Brickfolio Next.js edition instead: a new project or post is one entry in a data file, and every card, list and sitemap line follows (Editing without touching HTML).
Getting help
Section titled “Getting help”- Your licence terms: License.
- What changed in each release: Changelog.
- Support and updates: https://framebrick.co/support.
- Want it done for you? Marcframe, the studio behind this template, updates templates to your needs, builds custom templates and designs new sites. It’s also on Contra.