Make this journey your own
Your Portfolio Editor
Edit words and pictures, then Save draft in this browser. Use Publish to website with your GitHub token to update the public site. This editor has a simple, bypassable browser gate, not secure authentication. All hosted files remain public; GitHub permissions protect publishing.
Upload limits
- Per original file: Photos: 8 MiB; PDFs: 15 MiB; Videos: 15 MiB, inclusive. Photos resize to 1600 px.
- Gallery: 30 photos + 3 clips. Total: 100 MiB encoded content (compact UTF-8 JSON, including text and archives).
- Plan for roughly 70 MiB combined original media — not guaranteed; text, archives and photo re-encoding affect space. Browser storage quotas may be lower; large drafts may be slow.
Keep exports and private originals backed up. Local capacity does not guarantee publication; publish only authorised, redacted content.
- 1 Choose a chapter
- 2 Edit text & pictures
- 3 Save draft or publish
Opening your saved browser draft…
Your pictures
Upload JPG, PNG or WebP (maximum 8 MiB per image). The editor resizes large images to 1600 pixels and embeds a copy in your exported file, so no separate picture upload is needed. Keep originals backed up. Add a brief image description for screen-reader users.
Continue or start over
To continue a previous editing session, select the
content.js you exported. Imports only read JSON data;
uploaded JavaScript is never executed. Save draft keeps edits on this
device; export keeps a portable backup. Browser data can be cleared,
and other people using this browser profile can see your draft.
Reset returns to the content.js that was loaded when this
editor opened; it does not change files on your computer.
Publish to your public website
Save draft keeps a local copy only. Publishing replaces content.js on Sasiru382/teacher-portfolio, branch main. It sends your text and embedded photos to GitHub. New local assets/PDFs must be uploaded separately.
Sign into GitHub in a separate tab. Your GitHub account must have write access to this repository. Create a short-lived fine-grained personal access token restricted to this one repository with Contents: read and write. No workflow write permission is needed. GitHub currently does not support fine-grained tokens for outside/repository collaborators: an invitation alone is not enough for this token workflow. The repository owner can publish with their own token, or a developer can configure a teacher-owned fork. Never share the owner's token. Step-by-step setup and collaborator instructions.
Used only for this action, never saved or exported. Cleared after each attempt. Never enter a token into a text/content field. Only publish from your trusted site and browser.
Checking the repository version…
Check deployment in GitHub Actions ↗After exporting
Find the downloaded file (usually in Downloads). Rename it exactly
content.js, then move it into your portfolio folder,
replacing the old file. Refresh index.html to see the
changes. If your site is online, upload the updated website folder
again. See publishing instructions.
The preview is temporary, not a save. If your browser blocks local preview storage, export and replace the file instead.