This website is turning into something more useful than a resume page.
That is the simplest way to describe where dancary.com is heading. The resume still matters, and it will stay here, but the site is becoming a broader home base for the work, writing, research, projects, and ideas that need a place to live.
From one page to a working site
For a long time, a personal website can get treated like a static business card: a name, a short bio, a resume, and maybe a contact link. That is useful, but it is also limiting. It makes the whole domain answer only one question: who is this person professionally?
I want this site to answer more than that. It should show what I am building, what I am learning, what I am researching, and what I think is worth keeping in public view.
The shape we are building
The structure is now in place. The home page is the front door. The resume is the formal professional record. The projects page is where active work can grow. This blog is for updates, notes, ideas, and occasional longer reflections. The search page helps tie the pieces together.
That gives the website room to become a living archive instead of a single page that has to do every job.
Projects are the center of gravity
The projects section is probably the most important part of the future site. It can hold public research, portfolio work, experiments, small apps, demos, essays, visual explainers, and whatever else deserves more than a short blog post.
The Bob Cary WWII Research project is one example of that direction. It is not just a page; it is a small research site with a timeline, evidence notes, maps, source questions, and story pages. The NPS thesis project is another example: an accessible summary of completed work focused on the outcome, framework, and recommendations.
A clear public and private boundary
One important principle is that not everything belongs online. Sensitive personal records, unfinished drafts, and working notes stay offline. The public site should explain what is useful to visitors while respecting that boundary.
That boundary matters because the site should be trustworthy, readable, and durable. Public pages should be polished enough to share. Private source material can stay messy, detailed, and useful for building the next version.
Simple on purpose
The site is still intentionally simple: quick to load, easy to preserve, and focused on the work instead of the platform behind it. That is a feature, not a compromise.
A simple site is easier to preserve, easier to move, easier to inspect, and easier to improve one file at a time. It lets the work stay visible without turning the website itself into the project.
Where it goes next
The next stage is steady growth. More project pages. More blog posts. Better internal links. Better search. Stronger visual presentation where it helps the subject. Cleaner archives for older material. The public HTTPS issue is now fixed, so the technical maintenance focus shifts to routine certificate renewal checks instead of a broken public certificate.
But the main objective is already clear: dancary.com should become a personal operating base on the web. It should hold the formal record, the active projects, the public research, the experiments, and the thinking that connects them.
That is where we are taking it.