About Gridopedia

A written reference and a set of browser tools for construction project-delivery people. Planning engineering first; the structure allows for more.

Two things already exist for planners, and neither is complete. The forums have community but the good answer is comment fourteen of thirty and nothing ever became a page you could find. The training sites have content but no way to ask anybody anything. And the analysis tools are mostly Excel add-ins that corporate IT blocks — the free browser ones that do exist will show you a schedule, but not check one.

Gridopedia is all three in one place: pages that answer the question in the first sentence, tools that run in a browser tab, and — later, once there is a reason for people to come back — somewhere to compare notes.

How it is built

Static pages, no ads, no accounts to read anything. Fonts are served from this site, so loading a page makes no request to any third party. Traffic is measured with Cloudflare Web Analytics — page views and referrers in aggregate, no cookies, no cross-site tracking, nothing that identifies you. The tools run entirely on your own machine. There is no server that sees your schedule file, because there is no server.

Who writes it

One person, with help. Every page cites the standard it relies on so you can check the source rather than trust the author. Where something is uncertain it says so.

Contact

Two addresses, so the important one never gets buried

Anything at all

Questions, corrections, contributions, tool feedback, partnerships.

hello@gridopedia.com

Your data

Removing your email address, removing a contribution, any privacy request.

privacy@gridopedia.com

Found a mistake on a page? Send it to hello@gridopedia.com with the page and what's wrong. Corrections are made quickly and the reviewed date on the page is updated when they are.

Follow along

Occasional email when something worth reading publishes.