Francisco GramajoSchool IT / web systems / practical AISchool IT, useful systems, practical AI, and clearer handoffs.
I'm Francisco Gramajo, a K-12 IT professional and web systems builder focused on making technology calmer, easier to trust, and built for the real world.
Use arrows, swipe, or choose a page.
Pages 01-02 / Contents marker / first spread
A fast read for people who want the shape of the work before they choose where to go deeper.
I support classroom technology, accounts, devices, troubleshooting, and the human moments that happen when tools fail during a busy school day.
Devices, accounts, networks, classroom tools, troubleshooting, and practical solutions.
Better notes, clearer workflows, useful tools, and small improvements that make work easier to repeat and hand off.
OK to Great Web Studio builds clean client websites, project scopes, and business inquiries.
Pages 03-04 / Currently
A living snapshot of the work that currently has the most gravity.
Right now, most of my attention goes toward supporting school technology, building clearer web systems, and using AI carefully to make planning and documentation less painful.
I work with devices, accounts, classroom tools, support requests, and troubleshooting. The job is helping people get back to the work that feels urgent to them.
I care about websites that load quickly, guide visitors clearly, and avoid turning every update into a small negotiation with the codebase.
I use AI for planning, drafting, summarizing, QA, study support, and turning rough information into usable structure while people keep judgment.
Good documentation keeps people from solving the same problem from scratch and helps the next person continue without guessing.
Pages 05-06 / Method
The repeatable thinking behind support tickets, websites, documentation, and AI-assisted workflows.
Great systems are not impressive because they look complicated. They are impressive because they reduce confusion at the exact moment someone needs help.
Before fixing the tool, understand what the person was trying to do, where the system failed them, and what would make the next attempt easier.
A plain label, reliable checklist, or obvious path beats a clever system people avoid. Clarity keeps the work from becoming interpretation work.
Useful notes preserve the decision, the context, the current state, and the next likely question. If the next person cannot understand what changed, the work is not finished.
Polish matters, but usefulness comes first. A smaller working version with clear constraints usually beats a perfect plan that never reaches the person who needs it.
Pages 07-08 / Contact Desk
The personal site gives context. The studio site handles client website work, packages, project inquiries, launch work, process, and business contact.
Personal context lives here. Client website work lives at OK to Great Web Studio: packages, project inquiries, launch work, process, and business contact.
Email, LinkedIn, GitHub, and studio inquiries each have a direct path so the next step stays easy to choose.
Thanks for reading Issue 01. Let us build systems people can trust and websites people can choose.