Are there any Dev's from India, let have a chat!

I build a tool in this space, so bias disclosed.

Agents are amazing at writing simple frontend, but dealing with the complexity of real apps? including state and how it propogates through the runtime? not so much. forcing the agent to either sepnd crazy amount of tokens to reason and guesstimate what the runtime might look like, and eventually make mistakes:

- spacing that looks fine in code but wrong in the browser

- a component that breaks only at one viewport

- HMR updates that do not match what the agent expected

- console/runtime errors the agent never saw

- CSS changes that technically apply but visually miss the target

For backend-ish work, repo context can be enough more often. For frontend, the page itself is part of the task.

I am testing a workflow where the agent can inspect DOM, screenshots, interactions, source, routes, browser logs, dev-server logs, and HMR feedback before editing.

Link for context: https://frontman.sh/
Fully Open Sourced and Self Hostable: https://github.com/frontman-ai/frontman

For frontend devs using AI agents: what runtime context actually helps?

And what is just tool bloat

Thanks!

Feels like well over half my week now is reading through components and styles a model generated and deciding what to keep. Reviewing's a real skill, fine, but the tooling is rough, I'm scanning a wall of JSX and CSS trying to spot what changed, with no clean way to accept this chunk and throw out that one. Is anyone on a review loop that feels like a real diff for generated UI, or are you all just eyeballing the whole component every time?

Building Cashvelope was a massive personal challenge. I wanted a true envelope budgeting app that put data control back in the user's hands.

Working on this late at night after my main work hours meant dealing with severe burnout, redesigning local data structures three times, and fighting through backend edge cases solo. Building a app end-to-end alone is a completely different beast than writing code for a client.

To fellow devs who built and released your own side projects:

How do you balance feature scope creep with actually getting the app across the finish line?

hi! I didn't think I'll need that in my life, but I very need to know how to use CSS properly. I mean what are the differences between one thing and another, what's more popular to use etc. So, I'm trying to relearn CSS.

For the context: I learned CSS in 2022 only to pass the exams and that's all, and then I was like "yahoo! I won't return to the web design ever again!". So, I can use the atributes with classes, id etc, but I can't understand what are the important things to properly use them. I didn't think I'll need to program projects related to web programming. I find JS and PHP quite easily to understand, bcz every thing has one meaning there. It was a bit hard to understand HTML for the first time, bcz I thought every tag has its own function, but when I understood that plenty of tags are semantical and I can just use <div> and <span> if I want, I started to use the semantical tags properly. CSS is the hardest part in Front-End for me, bcz Idk if plenty of things are similar to the HTML ones(an atribute is optional and it depends on you if you want/need to use that) or the programming languages(1 thing = 1 meaning).

Here are my questions about CSS to understand it better:

1. which position is the best? Bcz usually I used "position: absolute";
2. why to use the coordinates(except for the z-index) if you have the margins?;
3. why a lot of web developers prefer to use the paths from a vector image instead of uploading the .svg file itself?;
4. what to use: the standard shadow or something like "filter: drop-shadow(10pt 10pt 6pt);"?;
5. I liked the grid, but I saw a lot of developers use flexbox. Is it important to choose one thing over another or is it something optional?;
6. are the CSS similar, but different atributes important only for the browsers?;
7. what's the point in making something like "p.name1 {}", when I could just create a new class?;

I hope I didn't forget anything, but if I did, I'll make a new post about them

Edit: I can't change the title, but I meant questionS*

We've been heads-down on SvGrid for a while and it's finally at the point where we want it in front of people who actually ship Svelte apps.

It's written for Svelte 5 directly. Runes, no wrapper around a framework-agnostic core, no adapter layer. That was the whole reason to start.

<script lang="ts">
  import { SvGrid, type GridColumns } from '@svgrid/grid'

  type Person = { firstName: string; age: number; status: string }

  const data: Person[] = [
    { firstName: 'Ada',   age: 36, status: 'active' },
    { firstName: 'Linus', age: 54, status: 'active' },
  ]

  const columns: GridColumns<Person> = [
    { field: 'firstName', header: 'First name' },
    { field: 'age',       header: 'Age' },
    { field: 'status',    header: 'Status' },
  ]
</script>

<SvGrid {data} {columns} sortable filterable editable />

Every capability is off by default, so a bare <SvGrid {data} {columns} /> is a plain read-only table and you opt into the rest one word at a time.

Underneath: virtualized both directions so a million rows scrolls fine, Excel-style filter menus, inline editing, grouping with aggregation, tree data, pivot, and a server-side row model that pushes sort/filter/group down to your backend instead of pretending your dataset fits in memory. SSR renders the header plus a viewport window of rows.

About 2 KB gzipped for the headless core, 77 KB for the full render component, 9 KB CSS.

The part we didn't plan. A grid needs cell editors. Cell editors need date pickers, comboboxes, tag inputs. Those need a popover layer and focus management. We looked up and had 84 components.

You can poke at any of them without making a project first:

npx @svgrid/ui try calendar

That caches a tiny Vite sandbox and opens your browser, with a theme picker so you can see it in whatever you're actually using. add writes the starter file into your app instead of the sandbox.

Licensing, since it always comes up. The grid, the UI components, the web component build and the MCP server are MIT with nothing gated. No license key, no watermark, no row cap, no console nag. We charge for Excel/PDF export, Excel import, print, and the Kanban and scheduler renderers. OSS projects get those free, just send us a repo URL.

Where it's weak. The grid has been in production a while. The UI components are much newer and haven't been beaten on anywhere near as hard. If you find something broken we'd rather hear about it than not.

Context on us: we're the jQWidgets team and we've been shipping UI components since 2011. This is the first thing we've built Svelte-first rather than framework-agnostic, and that bet is what I'd most like opinions on. Going deep on one framework buys you a much smaller API, but you'll never see us in a React thread.

Two things I'd take from this thread:

1. https://svgrid.com/demos is 373 demos with source on every one, which is honestly the fastest way to work out whether it's any good. Break one and tell me which.
2. What's the grid feature you keep hand-rolling because nothing ships it properly? That list is how we pick what's next.
3. MCP Server

Repo: github.com/sv-grid/sv-grid

So I'm in a second year btech students CSE,,,, so there is anyone who is a taking a batch of apna college in which Web development is completely taught so help me yaarr bhaiyon muze bhi Koi access de do yaarr... Muze kharidne ka Mann nhi hai anyone here jo de sakte ho.......

Hey r/Frontend

I've been working on Oasis Editor, an open-source document editor written in TypeScript.

It has its own Canvas-based rendering engine for paged layout, text, selections, images, tables, and document geometry instead of relying entirely on contenteditable.

It also includes a typed command/plugin API, DOCX/PDF workflows, React and Vue adapters, and a headless runtime.

Live playground:
https://celsowm.github.io/oasis-editor/#/editor

GitHub:
https://github.com/celsowm/oasis-editor

I'd love feedback, issues, and contributions — especially around rendering, document layout, plugins, and import/export fidelity.

ps: MIT license

The UI stays unobtrusive while we treat accessibility as non-negotiable. There is no bail-out, because we believe that software should be available to everyone. There has been done a lot of work in fully supporting WCAG 2.2, and I'm really proud of the result.

The grid is now one of the most performant, most accessible enterprise type DOM based grids on the planet, supporting a ton of opt-in features, and it's MIT licensed.

Hello, so im going over an old website I made back when I first started developing, and silly me decided to build the entire thing with "position: relative, right: -233px" 😭

Am I going to have to redo the entire site CSS to flexbox so it doesnt move about on different screen sizes, or is there an easier way to save this site?

I'm new here.

We manage around 20 client sites and lately the annoying part has been catching small visual issues after WordPress or plugin updates. Usually it's something minor like a section shifting, a form looking off, or mobile spacing getting messed up, but we don't always notice until the client does.

Looking into visual regression testing mainly so we're not manually checking every important page after updates. What are other agencies using for this?

Hey everyone,

If you use GitHub Copilot Agent, you know it often wastes a lot of tokens and context just wandering around
your workspace trying to figure out which files to look at.

Copilot Bill Saver

The VS Code extension is designed to accelerate web development and stop context waste before it starts.

• How it works: It captures local bug evidence, maps likely files deterministically, and bundles them into a clean handoff that Copilot Agent retrieves using #billSaverContext so it starts directly on the right files.
• Privacy & Control: The extension never calls an AI model, never touches or edits your code, and runs locally with built-in secret redaction.

If anyone gives it a spin via the Marketplace, leave a word! *Copilot Bill Saver\*

Hello everyone,

currently I am doing FE development in a large scale project and I got the feeling that one of our designers doesn't know how Storybook works.

When she builds designs in Figma, I always tell her that she can look at the component libraries' Storybook and do the design according to how those components work. However, she does a lot of paddings in the design not adhering to our standard values or makes borders around only some parts of the components which would require that we need to split up some of the component (and much more).

I spent a lot of time discussing if we really need custom stylings, or if we should use the styles that are already baked into the finished components. Obviously, custom styles are more work and are kind of missing the point of having a component library for me. Most of the time my co-workers think I am right, but before I am always having the same discussion again and again...

Am I too strict with the designer and what are your experiences with them? Can I expect them to actually know Storybook and to check out how a component behaves using the controls?

EDIT: To be clear: We have a styleguide in Figma that is being implemented in Storybook. However, the Storybook is better maintained than the Figma. Also, in Figma no animations are designed and some states are missing (e.g. there are barely designs for dark mode). I don't expect the designer to write stories or build the Storybook, but I wish they'd have a look at the deployed Storybook so the discussions about unexpected behavior are becoming less.

I have a live website where some pages are populated dynamically through JavaScript/API calls. I’m shutting down the backend after the project ends and want to migrate the current version to a completely static site.

What’s the best way to do this while preserving the currently rendered content, images, CSS, fonts, etc.? I’ve tried wget/HTTrack, but they only save the initial HTML and miss the content generated by JavaScript.

Would a browser-based rendering tool be the best approach, or is there a better tool/workflow for this?

I play minecraft, and I’ve recently gotten into the field of computational redstone. After watching a tutorial on how to make a CPU, I decided to go and make an emulator for it based off the one used in the videos. It is programmed with pure front end JavaScript, and it comes complete with built in documentation. It is currently in version 1.7, and contributions are open for those interested. There is a link to the open source repository on-site.

I have been working on this video recorder (similar to screen studio but for windows), my app ui looks very cluttered and messy, I have no idea how can i make it feel easy to use and a little bit welcoming, any suggesions??

Has anyone gone through the interview process for a ios role at Robinhood recently? I’ve heard they don’t ask leetcode style questions, just ios specific (building screens, system design, etc). I believe it’s one tech screening round and a virtual onsite. Any insight would be appreciated!

I started building Cashvelope because I couldn't find a privacy-first, simple envelope budgeting tool that worked the way I wanted. Being a solo dev, I severely underestimated how tough it would be to handle everything end-to-end.

The hardest part wasn't the basic UI, it was managing complex state offline-first, ensuring data sync without breaking privacy, and crafting a clean UX for category allocations without bloating the codebase. There were multiple times I felt like throwing in the towel mid-way.

For those who have launched a full product by yourselves: What was that one feature or technical architecture issue that almost made you give up? How did you push through it?

I assume vast majority of people that will use this dashboard starter will remove all premade content with mock data so in a sense this change doesn't really matter, but it was fun to do it anyway.

In case someone was interested here's the live link https://demo.nellavio.com/analytics

To be clear - this project is not e-commerce platform or some other analytics platform, it's just a starter. All data is mocked, and charts are not meant to make sense as a whole. Question in this post is about UI design.