Francisco GramajoSchool IT / web systems / practical AI
Now viewingCoverFront cover / 00:00
Issue 01School IT / web systems / practical AI

from Okay to Great

School 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.

Page 0 / Cover
01

Pages 01-02 / Contents marker / first spread

At a Glance

A fast read for people who want the shape of the work before they choose where to go deeper.

Issue 01 / Pages 01-02Who I Am
Who I Am

School IT, without the mystery fog.

I support classroom technology, accounts, devices, troubleshooting, and the human moments that happen when tools fail during a busy school day.

K-12 IT professionalOn the ground, in the real world.
Systems builderClearer workflows, practical tools, and useful improvements.
Calmer techTechnology should help people, not add to the chaos.
Page 01
Issue 01 / Practical SystemsWhat I Build
School IT

Stable tech. Reliable systems. Better days for teachers and students.

Devices, accounts, networks, classroom tools, troubleshooting, and practical solutions.

Systems

Systems I keep refining.

Better notes, clearer workflows, useful tools, and small improvements that make work easier to repeat and hand off.

Studio / Web

Client websites with their own front door.

OK to Great Web Studio builds clean client websites, project scopes, and business inquiries.

Page 02
02

Pages 03-04 / Currently

Now in Rotation

A living snapshot of the work that currently has the most gravity.

Current Work / Active InterestsCurrently
Current work

Current work, active interests, useful structure.

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.

  1. 01Education technology
  2. 02Maintainable websites
  3. 03Practical AI workflows
  4. 04Documentation that helps
Page 03
Issue 01 / Field NotesUseful Structure
01

Supporting the daily reality of education technology.

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.

02

Making websites easier to understand and maintain.

I care about websites that load quickly, guide visitors clearly, and avoid turning every update into a small negotiation with the codebase.

03

Using AI where it sharpens the work.

I use AI for planning, drafting, summarizing, QA, study support, and turning rough information into usable structure while people keep judgment.

04

Turning solved problems into reusable context.

Good documentation keeps people from solving the same problem from scratch and helps the next person continue without guessing.

Page 04
03

Pages 05-06 / Method

How I Work

The repeatable thinking behind support tickets, websites, documentation, and AI-assisted workflows.

The philosophy I come back toMethod

Less fog. Better handoffs. Useful versions.

Great systems are not impressive because they look complicated. They are impressive because they reduce confusion at the exact moment someone needs help.

Useful over clever
Page 05
Issue 01 / Working MethodPractical Principles
01

Start with the real user moment.

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.

02

Prefer clarity over cleverness.

A plain label, reliable checklist, or obvious path beats a clever system people avoid. Clarity keeps the work from becoming interpretation work.

03

Document the handoff.

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.

04

Ship the useful version.

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.

Page 06
04

Pages 07-08 / Contact Desk

Send a Signal

The personal site gives context. The studio site handles client website work, packages, project inquiries, launch work, process, and business contact.

Personal site vs. studioContact Desk
Personal site vs studio

Personal site here. Client services there.

Personal context lives here. Client website work lives at OK to Great Web Studio: packages, project inquiries, launch work, process, and business contact.

Page 07
Contact OptionsReach Out
Contact options

Reach out when the next step needs to be clearer.

Email, LinkedIn, GitHub, and studio inquiries each have a direct path so the next step stays easy to choose.

Page 08
Back CoverIssue 01

Useful systems. Clearer handoffs. Better next steps.

Thanks for reading Issue 01. Let us build systems people can trust and websites people can choose.

Francisco GramajoSchool IT professional / web systems builder
Front cover / 00:00