Retro Unix Blog(WEbsite gonna go under the Redesign) --->(https://www.welcome-to-the-sunny-side.com/home.html)
Personal website and blog for Shane Cardoz, built as a lightweight static site with a retro Unix and FreeBSD-inspired visual language.
This project is intentionally simple:
- Static HTML first
- CSS for presentation and theming
- Near-zero JavaScript
- Text-first content
- Fast load times
- Readable source structure
The goal is not to recreate a terminal literally. The goal is to build a personal site that borrows the restraint, density, and clarity of older Unix systems while still reading well on modern browsers and small screens.
Phase 1 locks the project to a plain static-site approach:
- HTML for pages
- CSS for layout, typography, themes, and retro styling
- Markdown files in
posts/as source material for articles - GitHub Pages for deployment
For the MVP, published pages are maintained as static HTML. Markdown source files are kept so the project can move to a generator later if the writing workflow outgrows hand-authored HTML.
/
├── index.html
├── about.html
├── blog/
├── posts/
├── css/
├── ascii/
├── assets/
├── templates/
├── public/
├── rss/
├── TODO.md
├── README.md
└── LICENSE
index.html: homepageabout.html: about pageblog/: blog index and published post pagesposts/: Markdown source drafts and post source filescss/: global stylesheet(s)ascii/: reusable ASCII art snippets and branding assetsassets/: images, icons, fonts, and other static mediatemplates/: reusable HTML skeletons or reference snippetspublic/: optional generated output if a build step is introduced laterrss/: feed-related files
There is no build step yet.
Open the HTML files directly in a browser during early development, or serve the repo with any small static file server when relative-path testing matters.
Example:
python3 -m http.server 8000
Then open http://localhost:8000.
The content system is Markdown-first and publish-to-HTML:
- Start from
posts/_template.md - Write and store the source article in
posts/<slug>.md - Publish the final page as
blog/<slug>.html - Update the blog index, homepage listings, RSS feed, and sitemaps
This keeps the source material readable and portable while the site remains a plain static HTML project.
- Use semantic HTML.
- Keep markup shallow and readable.
- Prefer plain CSS over tooling unless a real maintenance problem appears.
- Default to ASCII content and source files.
- Avoid JavaScript unless there is no clean HTML/CSS alternative.
- Keep decorative effects subordinate to readability.
- Use lowercase class names.
- Prefer descriptive names tied to layout or component purpose.
- Keep theme values in CSS custom properties.
- Avoid one-off inline styles.
- Group related rules together: tokens, layout, typography, components, utilities.
Suggested naming pattern:
- Layout:
site-header,content-shell,page-section - Components:
prompt-nav,post-card,ascii-block - Utilities:
visually-hidden,stack,cluster
Target deployment is GitHub Pages from the repository after the base pages and feed are in place.
The repository includes a GitHub Actions workflow at .github/workflows/pages.yml.
It publishes only the public site files to GitHub Pages:
- HTML pages
css/blog/rss/assets/ascii/robots.txtsitemap.xml
Markdown source files in posts/, templates in templates/, and roadmap files are intentionally not included in the deployed artifact.
To deploy:
- Push changes to
main. - In GitHub repository settings, set Pages source to GitHub Actions.
- Wait for the
Deploy GitHub Pagesworkflow to complete.
The expected public URL is:
https://shanecardoz.github.io/
Phase 2 should build a shared page shell across:
index.htmlabout.htmlblog/index.html- at least one real post page