![]() With HTML and CSS out of the way, the next area of focus should be JavaScript (JS). We’ll also set up linting with stylelint. Part Three of this series will cover setting up CSS support, starting with a simple build process for custom styles written in SCSS, and ramping up to a more complex build process that includes more third-party tooling. However, if you’re only going to support modern browsers, you have a lot more tools at your disposal. If you’re still stuck supporting IE11, it may not be practical to use a lot of CSS custom properties, and you might need something like autoprefixer. We’ll also need to make some decisions about browser support. Since this will be a starting point for future, undefined projects, we’ll want it to be flexible, or at the very least, replaceable. At this point, we need to decide whether to use a third-party thing like Bootstrap or Tailwind to write our own custom styles. Once we have HTML in place, it’s time to start styling it with CSS. We’ll cover all of that in Part Two, and we’ll also set up pa11y-ci to make sure our HTML output is valid and accessible. We will need layout files that define the basic HTML structure and dynamic content sections where page-by-page HTML will go. ![]() HTMLĪs the backbone of any web project, we need our HTML to be rock solid, and we want to repeat ourselves as little as possible. Part One of this series will cover the basics for setting up a project, including initializing Git and npm, adding basic configuration files, and building our first page with Eleventy. Project Setup and ConfigurationĮvery project has to start somewhere. Let’s break these down and define some goals for what we want our project starter to do.
0 Comments
Leave a Reply. |