Frontend (SSR, Jinja2) for CRM on FastAPI - strictly according to the technical specifications, without SPA
There is a ready backend CRM on FastAPI (Python 3.12).
Roles implemented: admin / supervisor / manager, authorization, RBAC, CSRF, security middleware, API contracts.
It is necessary to implement the zero stage of the frontend (Stage 0) strictly according to the technical specifications.
Frontend — server-side rendering (SSR):
* Jinja2 templates
* minimal vanilla JavaScript
* no React / Vue / SPA
The project is engineering-focused, emphasizing architecture, security, and predictable UI behavior.
The backend is already implemented. The architecture is fixed.
The frontend does not contain business logic, only display and interaction with the API.
---
What needs to be done:
1. Implement SSR pages:
* auth: login, TOTP setup
* dashboard by roles (admin / supervisor / manager)
* employee lists
* user cards
* system error pages (403 / 404 / 500)
2. Implement a common frontend layer:
* unified JS API client (fetch is prohibited outside of it)
* correct handling of 401 / 403 / 422 / 500
* safe-redirect (next)
* CSRF (double submit)
* breadcrumbs
* role-based sidebar
* global UI states: loading / empty / error
3. Ensure security requirements:
* CSP compatibility (no inline-script, onclick, etc.)
* correct handling of cookies and CSRF
* no bypassing backend restrictions
4. Testing:
* minimal set of e2e tests (Playwright)
* checking basic user scenarios
---
Technical requirements (mandatory):
* SSR (Jinja2 or similar), no SPA
* FastAPI backend (already ready)
* Vanilla JS (modules)
* Understanding of HTTP statuses and UX errors
* Experience with role-based interfaces
* Attention to technical specifications and details
* Willingness to strictly follow the architecture
---
What NOT to do:
* SPA / React / Vue
* Rewrite the backend
* Simplify requirements
* Add fields, logic, or UI "at your discretion"
---
Work format:
* Fixed volume (Stage 0)
* Stage acceptance
* Direct communication with the project architect
* Technical specifications — the only source of truth
---
Who we are looking for:
Please do not respond if:
* you only work with SPA (React/Vue);
* you do not read long technical specifications;
* you have not worked with SSR;
* you do not write e2e tests.
---
In your response, please answer the questions:
1. Have you worked with SSR (Jinja2 / Django templates / similar)? Briefly describe the project.
2. How do you usually organize JavaScript logic on top of SSR?
3. Do you have experience with Playwright or Cypress?
4. Are you willing to strictly follow the technical specifications without architectural improvisations?
Responses without answers to the questions will not be considered.
---
Deadlines and budget:
Deadline: 1-2 weeks.
Budget: negotiable, target 1000–1800 USD.
Applications 1
-
Hello! The requirements are clear: SSR without SPA, fixed architecture, strict adherence to the technical specifications, no business logic on the frontend, priority on security (RBAC, CSRF, CSP), predictable UI behavior, and phased acceptance with the architect. The format and constraints suit me.
I will answer the questions.
1. Yes, we have worked with SSR: Jinja2 (FastAPI, Flask) and Django templates. I have created internal CRMs and admin panels with server-side rendering, roles (admin/manager, etc.), cookie-based authorization, CSRF (double submit), strict CSP without inline scripts, system error pages, breadcrumbs, and role-based navigation. The backend was the source of truth, and the frontend was a thin layer for display and API calls.
2. We organize JavaScript on top of SSR in a minimalist way: ES modules, a single API client (fetch is encapsulated, not used outside the client), centralized handling of HTTP statuses (401/403/422/500), safe-redirect through next, global UI states (loading/empty/error). JS does not contain business logic, only UI state management and interaction with backend contracts, fully compliant with CSP (no inline, no onclick).
3. Yes, I have experience with Playwright (main) and Cypress. I write e2e tests for basic user scenarios: login, role checks, access/denials, error handling, redirects, correct form operation, and CSRF.
4. Yes, we are ready to strictly follow the technical specifications without architectural improvisations, not to add fields, logic, or UI "from ourselves," and to work within the fixed architecture and backend contracts.
-
242 Do you have experience with Playwright or Cypress?
I do not have commercial experience with Playwright / Cypress. I have not previously implemented e2e tests, but I am ready to learn basic scenarios (login, role-based access, transitions, and errors) strictly within the framework of the technical specifications.
How do you usually organize JavaScript logic on top of SSR?
I have not previously organized JavaScript logic on top of SSR. I am ready to use minimal vanilla JS strictly as a UI layer: for working with forms, processing server responses, and displaying interface states, without transferring business logic or access decisions to the client.
Have you worked with SSR (Jinja2 / Django templates / similar)?
I do not have direct commercial experience with Jinja2 / Django templates. I am comfortable working with server-generated HTML (WordPress, PHP projects), I understand the SSR model and the role of templates as a presentation layer without business logic.
… Are you ready to strictly follow the technical specifications without architectural improvisations?
Yes. I work strictly according to the technical specifications, read the requirements in full, pay attention to details, and am comfortable working under strict architectural constraints.
-
96760 1276 1 10 Hello. I have experience with FastAPI/Jinja. I am ready for collaboration.
-
Зачем страдать ерундой. А не сделать фронт на том языке на котором он работает. JS.
-
Могу реализовать фронт на Angular(SSR).
-
Current freelance projects in the category HTML & CSS
Web design and developmentHello! For the current project, I am looking for two separate specialists: web designer (Figma) web developer (Frontend / WordPress) The project includes tasks such as: landing pages, online store, admin panels, WordPress site, as well as small tasks on React / Next.js and… HTML & CSS, Web Design ∙ 6 hours 1 minute back ∙ 63 proposals |
A modern website is needed for a stretch ceiling company in Poland.
635 USD
Need a modern premium design, mobile device adaptation, fast loading, SEO, animations, calculator, portfolio, application form. Experience in creating websites in Poland, landing pages for construction or renovation companies is preferred. Please be sure to send examples of your… HTML & CSS, Web Programming ∙ 7 hours 1 minute back ∙ 112 proposals |
Looking for a Frontend Developer for an educational platformFrontend Developer https://www.figma.com/design/vXKC6kfWOeDBX2464BXqRv/%D0%A2%D0%97?node-id==0-1&p=f&t=OJxQ9DF0zXBNnBJv-0 Hello! We are looking for a frontend developer to work on a modern music platform Muse. The project already has a ready design in Figma, a… HTML & CSS, Web Programming ∙ 8 hours 50 minutes back ∙ 76 proposals |
A Drupal developer is needed for edits on several websites.A Drupal developer is needed for edits on several websites. The site has bloated and filled up all the hosting.. HTML & CSS, Web Programming ∙ 13 hours 14 minutes back ∙ 33 proposals |
Optimization of WordPress site speed
113 USD
We will send full details in private messages Goal Maximize website loading speed, especially on mobile devices. KPI (mandatory) After the work is completed, the following metrics must be achieved. Mobile Performance 90+ LCP less than 2.2 sec INP less than 200 ms CLS less than… HTML & CSS, Javascript and Typescript ∙ 1 day 4 hours back ∙ 61 proposals |