Alan W Gallagher Site

This is the repository for my personal profile and portfolio site: a public place to present my work, experience, projects and professional direction.

I have built this site because I wanted more than a standard CV or LinkedIn profile. It gives me a controlled space to show how I think, how I organise information, and how I use digital tools to turn experience, projects and evidence into something readable for employers, collaborators and decision-makers.

This is not meant to present me as a conventional software developer. The point is that I understand enough of the stack to plan it, structure it, work with it, use GitHub properly, guide AI-supported development, and translate the output back into language that people can actually use.

Live site: https://www.alanwpgallagher.info/

Purpose

The site is intended to support my professional move into roles around:

• business and technical operations
• service improvement
• project and governance support
• systems support and digital administration
• process documentation
• responsible use of AI in ordinary work
• technical liaison between users, teams and decision-makers

The site should make it easier for someone to understand not only what I have done, but how I think and how I approach messy organisational problems.

What I wanted to demonstrate

I wanted this repository and site to show that I can:

• structure a professional profile beyond a flat CV
• organise content into clear sections and user journeys
• use plain British English for public-facing material
• work with HTML, CSS, JavaScript, GitHub and static-site publishing
• use AI as a practical support tool while retaining judgement and editorial control
• document decisions clearly enough that another person can understand the work
• separate live content, archived material and work-in-progress material
• keep public material safe, professional and proportionate

The main message is practical judgement at the point where people, process, technology, evidence and decision-making meet.

Tech stack

This is deliberately simple and maintainable:

• static HTML
• CSS
• vanilla JavaScript
• Git and GitHub for version control
• static hosting for publication
• structured metadata for search and sharing

There is no heavy framework here. That is intentional. The site should remain understandable, portable and easy to maintain.

Site structure

The public site is organised around the main professional story:

• index.html — homepage and first impression.
• profile.html — professional profile and positioning.
• experience.html — work history and capability evidence.
• method.html — detail about the way I like to work.
• workbench.html — selected projects and demonstrations of my work.
• timeline.html — career and project chronology.
• 'CV.html` — where my CV is located.
• about.html — personal context
• contact.html — personal context
• assets/ — images, styles and scripts
• archive/legacy/ — older material retained for reference, not treated as current public positioning

Repository status

• Classification: Portfolio
• Status: Active
• Audience: hiring managers, recruiters, collaborators and organisations looking for operational, governance, project-support, service-improvement or technical-liaison capability
• Tone: practical, mature, evidence-led and clear

Content rules

I want the site to have personality, but it still needs to be safe and professional.

Public pages should not include:

• confidential employment material
• private financial information
• medical information
• third-party personal information
• unfinished dispute or grievance material
• inflated claims about development skill
• vague marketing language that does not say anything useful

Work-in-progress pages should not be promoted from the live portfolio until they have a clear purpose, audience and status.

Development approach

This project is partly a portfolio site and partly a working demonstration of how I use tools.

My approach is:

1. decide what the site needs to say
2. structure the information clearly
3. use AI and web tools to accelerate the build where useful
4. review the output myself
5. keep the language human and understandable
6. commit changes in GitHub so the work has a record

That is the real skill I want this site to show: not just pressing buttons, but knowing what needs to be built, why it matters, and how to make it usable for people - with the assistance of AI.

Showcase standard

Before I use this site prominently in job applications, it should have:

• a clear homepage message
• a focused CV/profile section
• a small number of strong project examples
• a safe contact route
• consistent visual style
• checked links
• checked spelling and punctuation
• no private or unnecessary personal material

Next improvements

Planned improvements include:

• tightening the homepage message
• improving the profile and experience pages
• adding stronger project case studies
• linking only the best supporting repositories
• reviewing old archived content so it does not confuse the current professional story

Working principle

I created this site to celebrate my own professional story without turning it into a generic CV page. It should show that I can understand tools, ask better questions, organise information, translate requirements, work with AI and technical systems, and help people make clearer decisions.