PortfolioForge Personal Brand Website Builder

Problem

Personal brand sites often get stuck on asset preparation: bios, projects, awards, and certificates may be scattered across TXT files, Excel sheets, and image photos. PortfolioForge aims to turn that material into a single index.html that can be opened offline or uploaded to static hosting, rather than producing an online resume.

How It Works

• Local validation: It reads a local folder and checks directory structure, UTF-8 encoding, image size, file weight, and link prefixes. Missing fields are logged without blocking generation.
• Multi-source timeline: Awards and experience can come from plain text, Excel tables, or certificate photos. The latter can be transcribed via OCR or visual recognition into year, title, and category, then merged into a grouped timeline.
• Style and layout pairing: Four styles and five layouts can be combined freely; A + T5 or C + T5 is usually recommended for a more website-like personal brand page.
• Single-file output: The generated page inlines CSS/JS, references images with relative paths and loading="lazy", and renders missing fields as dashed placeholders so the site can be regenerated after edits.
• Iteration and packaging: Users can update the local folder or request changes in chat, such as copy, colors, buttons, or links. Once approved, it packages index.html and images into website_bundle.zip.

Limits

• Local file access and certificate-photo reading require user confirmation.
• Excel parsing depends on openpyxl; offline rendering favors system fonts, while web fonts require network access.
• It is best suited for static portfolios and personal sites, not for backends, authentication, permissions, or full CMS workflows.