Week 3 of the four-week plan on this site is “A sample”: turning what you learned into something you can show. Publishing those samples in one place also gives you something to share in Week 4, “A practice opening.” This guide gives sample ideas by type and explains how to publish them with static hosting. If you have not taken a quiz yet, start with the Remote Side Gig Type Quiz or the Tech Skill Match Quiz so you can read this with your own type in mind.
Sample ideas by type
Samples can be small. It is enough to show why you made it, what you used, and what you would point out.
- The Storyteller: one article on a chosen topic, with a before-and-after edit
- The Visual Maker: three versions of one banner, each with its intent
- The Builder: a form-and-spreadsheet setup and a diagram of how it flows
- The Helper: sample replies to five common inquiries
- The Guide: slides and questions for a fifteen-minute mini lesson
- The Organizer: a cleaned public dataset and the rules you applied
- The Interface Crafter: one page that works on phones
- The Architect: a tiny API and a note on how data is stored
- The Analyst: a chart from public data with a three-line note
- The Operator: a step-by-step write-up of publishing a page in the cloud
- The Inspector: ten test cases, one of them automated
- The Product Designer: a screen redesign and what testers did with it
- The Guardian: an account-protection review checklist
- The Prompt Pilot: a comparison of three instructions and their outputs
What static hosting is
Static hosting serves files—HTML, CSS, images—as they are. No server setup and no database, which makes it a good first way to publish. Many services have free plans, but terms change, so check the official pages.
- Services tied to code hosting (such as GitHub Pages)
- Services that deploy automatically (such as Cloudflare Pages, Netlify, or Vercel)
- Hosting features of major clouds (such as Firebase Hosting or AWS Amplify Hosting)
Publishing formats that suit each type
Code-focused types such as The Interface Crafter and The Architect benefit from hosting linked to code repositories. Non-coding types such as The Visual Maker and The Storyteller can start from a template and swap in their own text and images. For The Operator, publishing through a major cloud’s hosting or storage is itself a learning exercise.
Writing about each piece
Aim for descriptions readable in thirty seconds: the goal, the tools, a highlight, and the next step. Label work in progress as such; it shows your growth. Reviewing descriptions and adding one new sample each month keeps the page alive.
Pre-launch checklist
Anyone can see a published page. Do a final check.
If you keep code in a public repository, add a README that explains the project and how to run it.
- No one else’s work and no employer or client materials
- No API keys or passwords in the files
- No unnecessary personal details such as address or phone number
- Checked on both phone and desktop
FAQ
Can I publish without coding?
Yes—start from a template and swap in your text and images. Learn a little HTML and CSS later.
Is one sample enough to publish?
Yes. One sample with a clear goal and notes is enough. Add more in the next four weeks.
Does it cost money?
Many static hosts have free plans, but terms vary. A custom domain usually costs extra.
Unfamiliar words? See the Glossary
