Posts Tagged:drupal developer austin

rfp-robotRFP ROBOT: Website Request for Proposal Generator

The time has come for a new website (or website redesign), which means you need to write a website request for proposal or web RFP. A Google search produces a few examples, but they vary wildly and don’t seem to speak really to your goals for developing or redesigning a new website. You need to write a website RFP that will clearly articulate your needs and generate responses from the best website designers and developers out there. But how?

Have no fear, RFP Robot is here. He will walk you through a step-by-step process to help you work through the details of your project and create a PDF formatted website design RFP that will provide the information vendors need to write an accurate bid. RFP Robot will tell you what info you should include, point out pitfalls, and give examples.


​No Joke…Download Anything You Want on Storyblocks

(This is a sponsored post.)Storyblocks is giving CSS-Tricks followers 7 days of complimentary downloads! Choose from over 400,000 stock photos, icons, vectors, backgrounds, illustrations, and more from the Storyblocks Member Library. Grab 20 downloads per day for 7 days. Also, save 60% on millions of additional Marketplace images, where artists take home 100% of sales. Everything you download is yours to keep and use forever—royalty-free. Storyblocks regularly adds new content so there’s always something fresh to see. All the stock your heart desires! Get millions of high-quality stock images for a fraction of the cost. Start your 7 days of complimentary downloads today! Direct Link to Article — Permalink ​No Joke…Download Anything You Want on Storyblocks is a post from CSS-Tricks Source: CssTricks

The All-New Guide to CSS Support in Email

Campaign Monitor has completely updated it’s guide to CSS support in email. Although there was a four-year gap between updates (and this thing has been around for 10 years!), it’s continued to be something I reference often when designing and developing for email. Calling this an update is underselling the work put into this. According to the post: The previous guide included 111 different features, whereas the new guide covers a total of 278 features. Adding reference and testing results for 167 new features is pretty amazing. Even recent features like CSS Grid are included — and, spoiler alert, there is a smidgeon of Grid support out in the wild. This is an entire redesign of the guide and it’s well worth the time to sift through it for anyone who does any amount of email design or development. Of course, testing tools are still super important to the over…

Read More →

The Modlet Workflow: Improve Your Development Workflow with StealJS

You’ve been convinced of the benefits the modlet workflow provides and you want to start building your components with their own test and demo pages. Whether you’re starting a new project or updating your current one, you need a module loader and bundler that doesn’t require build configuration for every test and demo page you want to make. StealJS is the answer. It can load JavaScript modules in any format (AMD, CJS, etc.) and load other file types (Less, TypeScript, etc.) with plugins. It requires minimum configuration and unlike webpack, it doesn’t require a build to load your dependencies in development. Last but not least, you can use StealJS with any JavaScript library or framework, including CanJS, React, Vue, etc. In this tutorial, we’re going to add StealJS to a project, create a component with Preact, create an interactive demo page, and create a test page. Article Series: The Key…

Read More →

Deploying ES2015+ Code in Production Today

Philip Walton suggests making two copies of your production JavaScript. Easy enough to do with a Babel-based build process. <!– Browsers with ES module support load this file. –> <script type=”module” src=”main.js”></script> <!– Older browsers load this file (and module-supporting –> <!– browsers know *not* to load this file). –> <script nomodule src=”main-legacy.js”></script> He put together a demo project for it all and you’re looking at 50% file size savings. I would think there would be other speed improvements as well, by using modern JavaScript methods directly. Direct Link to Article — Permalink Deploying ES2015+ Code in Production Today is a post from CSS-Tricks Source: CssTricks

The Key to Building Large JavaScript Apps: The Modlet Workflow

You’re a developer working on a “large JavaScript application” and you’ve noticed some issues on your project. New team members struggle to find where everything is located. Debugging issues is difficult when you have to load the entire app to test one component. There aren’t clean API boundaries between your components, so their implementation details bleed one into the next. Updating your dependencies seems like a scary task, so your app doesn’t take advantage of the latest upgrades available to you. One of the key realizations we made at Bitovi was that “the secret to building large apps is to never build large apps.” When you break your app into smaller components, you can more easily test them and assemble them into your larger app. We follow what we call the “modlet” workflow, which promotes building each of your components as their own mini apps, with their own demos, documentation,…

Read More →

Chrome to force .dev domains to HTTPS via preloaded HSTS

Mattias Geniar: A lot of (web) developers use a local .dev TLD for their own development. … In those cases, if you browse to http://site.dev, you’ll be redirect[ed] to https://site.dev, the HTTPS variant. That means your local development machine needs to; Be able to serve HTTPs Have self-signed certificates in place to handle that Have that self-signed certificate added to your local trust store (you can’t dismiss self-signed certificates with HSTS, they need to be ‘trusted’ by your computer) This is probably generally A Good Thing™, but it is a little obnoxious to be forced into it on Chrome. They knew exactly what they were doing when they snatched up the .dev TLD. Isn’t HSTS based on the entire domain though, not just the TLD? Direct Link to Article — Permalink Chrome to force .dev domains to HTTPS via preloaded HSTS is a post from CSS-Tricks Source: CssTricks

React + Dataviz

There is a natural connection between Data Visualization (dataviz) and SVG. SVG is a graphics format based on geometry and geometry is exactly what is needed to visually display data in compelling and accurate ways. SVG has got the “visualization” part, but SVG is more declarative than programmatic. To write code that digests data and turns it into SVG visualizations, that’s well suited for JavaScript. Typically, that means D3.js (“Data-Driven Documents”), which is great at pairing data and SVG. You know what else is good at dealing with data? React. The data that powers dataviz is commonly JSON, and “state” in React is JSON. Feed that JSON data to React component as state, and it will have access to all of it as it renders, and notably, will re-render when that state changes. React + D3 + SVG = Pretty good for dataviz I think that idea has been in…

Read More →

A Rube Goldberg Machine

Ada Rose Edwards takes a look at some of the newer browser APIs and how they fit together: These new APIs are powerful individually but also they complement each other beautifully, CSS custom properties being the common thread which goes through them all as it is a low level change to CSS. The post itself is a showcase to them. Speaking of new browser APIs, that was a whole subject on ShopTalk a few weeks back. Direct Link to Article — Permalink A Rube Goldberg Machine is a post from CSS-Tricks Source: CssTricks

Basic grid layout with fallbacks using feature queries

I often see a lot of questions from folks asking about fallbacks in CSS Grid and how we can design for browsers that just don’t support these new-fangled techniques yet. But from now on I’ll be sending them this post by HJ Chen. It digs into how we can use @supports and how we ought to ensure that our layouts don’t break in any browser. Direct Link to Article — Permalink Basic grid layout with fallbacks using feature queries is a post from CSS-Tricks Source: CssTricks

Basic grid layout with fallbacks using feature queries

I often see a lot of questions from folks asking about fallbacks in CSS Grid and how we can design for browsers that just don’t support these new-fangled techniques yet. But from now on I’ll be sending them this post by HJ Chen. It digs into how we can use @supports and how we ought to ensure that our layouts don’t break in any browser. Basic grid layout with fallbacks using feature queries is a post from CSS-Tricks Source: CssTricks

“The Notch” and CSS

Apple’s iPhone X has a screen that covers the entire face of the phone, save for a “notch” to make space for a camera and other various components. The result is some awkward situations for screen design, like constraining websites to a “safe area” and having white bars on the edges. It’s not much of a trick to remove it though, a background-color on the body will do. Or, expand the website the whole area (notch be damned), you can add viewport-fit=cover to your meta viewport tag. <meta name=”viewport” content=”width=device-width, initial-scale=1.0, viewport-fit=cover”> Then it’s on you to account for any overlapping that normally would have been handled by the safe area. There is some new CSS that helps you accommodate for that. Stephen Radford documents: In order to handle any adjustment that may be required iOS 11’s version of Safari includes some constants that can be used when viewport-fit=cover is…

Read More →

Design Tooling is Still Figuring Itself Out

It probably always will be, to be fair. At the moment, there are all kinds of things that design software is struggling to address. The term “screen design” is common, referring to the fact that many of us are designing very specifically for screens, not print or any other application and screens have challenges unique to them. We have different workflows these days than in the past. We have different collaboration needs. We have different technological and economic needs. Let’s take a peak at all this weirdness. Design tooling is still figuring out Responsive Design It’s almost taken for granted these days that any given new web project (or redesign) will be responsive design. Responsive design is the answer for screens of different sizes and different capabilities. So we can’t just design a 1280px wide version and call it a day. Software like Sketch has made multiple artboards of arbitrary…

Read More →

​Deliver exceptional customer experiences in your product

(This is a sponsored post.)Pendo delivers the only complete platform for Product Teams that helps companies create great products. The Pendo Product Experience Platform enables Product Teams to understand product usage, collect user feedback, measure NPS, assist users in their apps and promote new features in product – all without requiring any engineering resources. This unique combination of capabilities is all built on a common infrastructure of product data and results in improved customer satisfaction, reduced churn, and increased revenue. Pendo is the proven choice of innovative product leaders at Salesforce, Proofpoint, Optimizely, Citrix, BMC and many more leading companies. Request a demo of Pendo today. Direct Link to Article — Permalink ​Deliver exceptional customer experiences in your product is a post from CSS-Tricks Source: CssTricks

Is there any value in people who cannot write JavaScript?

Mandy Michael: If all you do in your job is write JS, that is fantastic and you are awesome, just like all the people that write CSS or have a focus in a particular area like accessibility, SVG, animation etc. What I am very concerned about is that many still don’t see value in being skilled in CSS & HTML. This attitude is something I just don’t understand. All of us working together provide value in our industry. +1 on all Mandy’s points. I suspect HTML and CSS skill will swing back higher in desirability a bit as design trends swing toward more complicated looks. More interesting layouts being one of those things. I tend to find those developers who only dabble in HTML/CSS fall over quickly when it comes to from-scratch work that involves layout. There is a lot of gray area here too. For example, I write Ruby…

Read More →

Design Resource Sites

Sometimes when you’re designing something, you need little helping hands. Perhaps a nice stock photo. Perhaps a happy little color palette. Perhaps a bleep or bloop sound. Perhaps the perfect icon. There are tons and tons of sites that do those things. There are fewer sites that curate these design resource sites into manageable, high-quality groups. So allow me to abstract that yet another step and provide a selected list of those types of sites. The Stocks This is the one I was trying to remember the other day that spurred the idea for this little post. I quite like how you can just hang out on this site and click around to what you need by the type of resource, and the resource sites themselves just come up iframed. Sans Francisco Sans Francisco is a colorful and organize list of design resources by Robinson Greig. Design Resources (.party!) The…

Read More →

Do you put anything in your code specifically for “Find in Project”?

During a having a team meeting the other day, a code formatting idea came up that I thought was super interesting. It had to do with formatting code in a such a way that made it easier to find what you were looking for later with any code editors “Find in Project” feature. Here’s what it was. When declaring a function in JavaScript, put a space after the function name and before the opening parenthesis, like… function doSomething () { } That space between doSomething and () is perfectly fine. Then when you call the function, don’t use a space, like this: doSomething(); It’s just a syntax convention. But now, “Find in Project” is more useful. If we want to quickly find where that function was defined, we can search for “doSomething ()”, and if we want to find instances of where it is used, we can look for “doSomething()”.…

Read More →

HTML Templates via JavaScript Template Literals

You know those super cool backticks-for-strings in new JavaScript? let emotion = `happy`; let sentence = `Chris is feeling ${emotion}`; Besides the variable interpolation in there being mighty handy, the do multi-line strings wonderfully, making them great for chunks of HTML: const some_html = ` <div class=”module> <h2>${data.title}</h2> <p>${data.content}</p> </div> `; That doesn’t look overly different than JSX does it?! Maybe we’d do something like that as a React component: class MyModule extends React.Component { render() { return <div class=”module> <h2>{this.props.title}</h2> <p>{this.props.content}</p> </div>; } } But what if we don’t really need React, or any other fairly-large-ish JavaScript framework? What if the only thing we want is the ability to render HTML templates and also really efficiently re-render them when we need to, like React is known for? As far as I understand it, that’s what projects like lit-html are for. As I write, it’s a pretty new library from…

Read More →

lite.cnn.io

This little website pulls in all the main stories from CNN and strips almost everything from the design; styles, images, fonts, ads, colors. Nada, zilch, gone. At first it looks like nothing but hypertext and it feels like an extraordinary improvement but Sam Saccone made a thread about potential improvements that the team could use to make that experience even faster such as server side rendering and replacing the React framework with something smaller, like Preact. Either way this approach to news design is refreshing. However, I can’t find anything more about the the motivations for building this version of CNN.com besides the announcement on Twitter. It would certainly be fascinating to learn if CNN built this specifically for people caught in disastrous situations where battery life and load time might be a serious matter of life and death. Direct Link to Article — Permalink lite.cnn.io is a post from…

Read More →

Compilers are the New Frameworks

Tom Dale: Increasingly, the bytes that get shipped to browsers will bear less and less resemblance to the source code that web developers write. Indeed. I suspected the same: Because performance matters so much and there is so much opportunity to get clever with performance, we’ll see innovation in getting our code bases to production. Tools like webpack (tree shaking, code splitting) are already doing a lot here, but there is plenty of room to let automated tools work magic on how our code ultimately gets shipped to browsers. Tom also says: This is a loss in some ways (who else got their web development start with View Source?) but is a huge win for users, particularly in emerging markets. It seems to me today’s world of GitHub, StackOverflow, and the proliferation of learning resources more than make up for learning via our own website spelunking, not to mention how…

Read More →

Back to Top