{"id":117,"date":"2026-01-23T17:39:22","date_gmt":"2026-01-23T16:39:22","guid":{"rendered":"https:\/\/jljimenezcara.es\/?page_id=117"},"modified":"2026-01-23T17:59:29","modified_gmt":"2026-01-23T16:59:29","slug":"proceso-de-trabajo-2","status":"publish","type":"page","link":"https:\/\/jljimenezcara.es\/en\/proceso-de-trabajo-2\/","title":{"rendered":"Workflow"},"content":{"rendered":"\n
\n
<\/div>\n\n
\n
\n

Workflow<\/h1>\n

\n A web project doesn\u2019t start with a template or a fixed quote. It starts with a diagnosis.\nBefore touching a single line of code, I need to understand what\u2019s broken, what works, and what the system is actually expected to do.\n <\/p>\n <\/header>\n\n

\n
\n

1 \u00b7 Diagnosis<\/h2>\n

I analyze the structure, hosting, performance, security, dependencies, and latent errors. First we identify the cause; then we decide the intervention.<\/p>\n <\/article>\n\n

\n

2 \u00b7 Proposal<\/h2>\n

I deliver a concrete technical solution\u2014no endless menus of options. Decisions are made on technical grounds, not based on trends.<\/p>\n <\/article>\n\n

\n

3 \u00b7 Implementation<\/h2>\n

What we agree on gets built. If something isn\u2019t viable, I\u2019ll say so. If something is going to break something else, I\u2019ll warn you beforehand.<\/p>\n <\/article>\n\n

\n

4 \u00b7 Support<\/h2>\n

If something fails, it gets fixed from the root cause, not with patches. And if the issue is expectations, that gets addressed too.<\/p>\n <\/article>\n <\/div>\n\n

\n \n <\/figure>\n\n
\n

This process is for people who want a website that works\u2014not one that looks pretty for two weeks.<\/p>\n Contact<\/a>\n <\/div>\n <\/div>\n<\/section>\n\n