Forvaltning av eiendeler Jobs

My site leans heavily on large JPEG background images and, right now, they drag our loading times down. I want those same visuals to feel crisp yet arrive noticeably faster for visitors. Your task is to take the existing JPEG backgrounds, refactor and optimise them so that page weight drops without sacrificing the look and feel. Whether you prefer lossless, near-lossless, or smart compression techniques, the end result should be lighter files that still match their current dimensions and quality standards. If you feel lazy-loading, modern formats (while still serving JPEG fallbacks), or responsive sizing sets will help, please build that into the workflow. Deliverables: • Optimised versions of every current JPEG background, ready to be swapped in one-for-one. • A brief change...

I have a set of Figma wireframes that must live side-by-side with my codebase in GitHub. Your task is to export those wireframes, place them in the repo, and set up the folder hierarchy exactly to the naming rules and structure guidelines I will share once we start. Beyond the initial commit, I need the repository organised so future design iterations are easy to track: clear version folders, a concise README that explains where files belong, and a simple workflow I can keep using (for example, branch naming or a lightweight GitHub Action if you think it helps). You’ll receive: • Figma access with download permission • My written structure and naming conventions Deliverables I expect: 1. A pull request adding the exported wireframes in the agreed layout. 2....

I have a static HTML template that I now need broken down into clean Laravel Blade views. The header, footer and the main content area should each become their own Blade sections so I can extend them easily throughout the project later on. Please keep every asset reference intact, swap hard-coded links for the standard Laravel helpers where appropriate, and add the usual @extends, @yield and @section directives so the pages remain fully dynamic. When you hand the work back I expect: • resources/views/layouts/ holding the shared header and footer • individual page views that @extend that master layout and fill the content section • all CSS, JS and image paths updated to asset() or mix() helpers • no design drift from the original HTML If you have worked with L...