Urgent.News

What's breaking now, across thousands of outlets.

Tech

Resumv: a resume editor you can deploy as a static site

Resumv is an MIT-licensed resume editor built with Astro and React. Its deployment model is deliberately small: build the project, serve the static output, and let the browser handle resume editing and exports. There is no user database or authentication service to operate. Source and setup instructions: https://github.com/liusha-com/resumv What comes from upstream Resumv adapts Reactive Resume's…

Resumv is an open-source resume editor released under the MIT license, allowing users to build and deploy their own static site for editing and viewing resumes. It leverages the Astro and React frameworks to provide a streamlined experience without the need for a user database or authentication service. The project incorporates 15 pre-designed resume templates, PDF rendering capabilities, and supports various export formats, including DOCX, Markdown, and JSON.

All processing occurs on the client-side, meaning there is no need for server-side storage or maintenance of resume records. Content is saved locally using the browser's localStorage feature, which means it is tied to the user's device and browser profile. Users can export their resume data using JSON backup and import functionality, ensuring they have a way to recover their work in case of device changes or clearing browser data.

Markdown and JSON exports provide a convenient way to maintain and transfer resume data across different devices, while the DOCX format allows for editable documents. However, the current implementation has some limitations, such as primarily supporting Latin-script resumes and not yet offering comprehensive Chinese typography support.

The browser's performance and storage behavior play a crucial role in the user experience, as all resume editing and export processes happen directly in the browser. While the technology does not require a server, the site still needs to be hosted on a static web server. Users should be aware of potential limitations, such as the loss of resume data if they clear their browser data or change devices.

Feedback from users who self-host small tools and those editing resumes is welcome to help improve the tool's usability and address any identified issues.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Building a Choose-Your-Own-Adventure API with NestJS — Part 4: Auth

Part 4 of the Grimoire API series. So far: a validated endpoint ( Part 1 ), persistence ( Part 2 ), and the actual XP/badge rules ( Part 3 ) — all running against one hardcoded "default player." This…

  • Replace placeholder DEFAULTPLAYERID with genuine user accounts
  • Use NestJS and Passport for authentication with Local and JWT strategies
  • Hash passwords with bcrypt and validate JWT tokens in JwtStrategy

Moving on-premises block storage to AWS? The "divide by 625 MBps" sizing approach comes out wrong

Moving on-premises block storage to AWS? The "divide by 625 MBps" sizing approach comes out wrong — measured session and queue counts What this article does and does not cover: it covers the measured…

  • Dividing throughput by 625 MBps to determine sessions is inaccurate.
  • Testing shows method fails to capture system's true potential.
  • Approach not recommended for AWS block storage sizing.

Polymarket Execution Verification: When “Filled” Doesn’t Mean Settled

A Polymarket trading bot can receive a successful execution response and still not know enough to safely continue trading. That sounds like a small implementation detail. It isn't.

  • Polymarket's bot receives execution responses even before full settlement.
  • System distinguishes between trade completion and transaction information availability.
  • Explicit state machine needed to avoid incorrect assumptions about trade status.

More from Wednesday 30 September →