A professional front-end template for building fast, robust, and adaptable web apps or sites.


HTML5 Boilerplate

Build status LICENSE devDependency Status NPM Downloads github-stars-image

HTML5 Boilerplate is a professional front-end template for building fast, robust, and adaptable web apps or sites.

This project is the product of over 10 years of iterative development and community knowledge. It does not impose a specific development philosophy or framework, so you're free to architect your code in the way that you want.

Quick start

Choose one of the following options:

  • Download the latest stable release from html5boilerplate.com. This zip file is a snapshot of the dist folder. On Windows, Mac and from the file manager on Linux unzipping this folder will output to a folder named something like html5-boilerplate_v7.3.0. From the command line will need to create a folder and unzip the contents into that folder.

    mkdir html5-boilerplate
    unzip html5-boilerplate*.zip -d html5-boilerplate
  • Clone the git repo — git clone https://github.com/h5bp/html5-boilerplate.git - and checkout the tagged release you'd like to use. The dist folder represents the latest version of the project for end users.

  • Install with npm: npm install html5-boilerplate or yarn: yarn add html5-boilerplate. The resulting node_modules/html5-boilerplate/dist folder represents the latest version of the project for end users. Depending on what you want to use and how you want to use it, you may have to copy and paste the contents of that folder into your project directory.

  • Using our new create-html5-boilerplate project, instantly fetch the latest npm published package (or any version available on npm) with npx, npm init or yarn create without having to install any dependencies. Running the following npx command installs the latest version into a folder called new-site

    npx create-html5-boilerplate new-site
    cd new-site
    npm install
    npm start


  • A finely-tuned starter template. Reap the benefits of 10 years of analysis, research and experimentation by over 200 contributors.
  • Designed with progressive enhancement in mind.
  • Includes:
  • Placeholder Open Graph elements and attributes.
  • An example package.json file with Parcel commands built in to jumpstart application development
  • Placeholder CSS Media Queries.
  • Useful CSS helper classes.
  • Default print styles, performance optimized.
  • An optimized version of the Google Universal Analytics snippet.
  • Protection against any stray console statements causing JavaScript errors in older browsers.
  • "Delete-key friendly." Easy to strip out parts you don't need.
  • Extensive documentation.

Browser support

  • Chrome (latest 2)
  • Edge (latest 2)
  • Firefox (latest 2)
  • Internet Explorer 11
  • Opera (latest 2)
  • Safari (latest 2)

This doesn't mean that HTML5 Boilerplate cannot be used in older browsers, just that we'll ensure compatibility with the ones mentioned above.

If you need legacy browser support you can use HTML5 Boilerplate v6 (IE9/IE10) or HTML5 Boilerplate v5 (IE 8). They are no longer actively developed.


Take a look at the documentation table of contents. This documentation is bundled with the project which makes it available for offline reading and provides a useful starting point for any documentation you want to write about your project.


Hundreds of developers have helped to make the HTML5 Boilerplate. Anyone is welcome to contribute, however, if you decide to get involved, please take a moment to review the guidelines:


The code is available under the MIT license.

  • script loading solution

    script loading solution

    # This issue thread is now closed. ## It was fun, but the conversations have moved elsewhere for now. Thanks ### In appreciation of the funtimes we had, @rmurphey made us a happy word cloud of the thread.


    via labjs or require.

    my "boilerplate" load.js file has LABjs inlined in it, and then uses it to load jquery, GA, and one site js file. if it helps, I have an integrated RequireJS+jQuery in one file: http://bit.ly/dAiqEG ;)

    also how does this play into the expectation of a build script that concatenates and minifies all script? should script loading be an option?

    opened by paulirish 132
  • Remove Google CDN reference for jQuery

    Remove Google CDN reference for jQuery


    According to that, there is a very little benefit to using the Google CDN to serve jQuery source. A better option would be to encourage devs to minify and concatenate all of their script files into one JS file served with a long-lived cache time.

    This was referenced by Alex Sexton (@SlexAxton) in his talk at jQueryTO March 2nd, 2013.

    opened by localpcguy 111
  • Drop legacy browser support

    Drop legacy browser support

    IE6 is essentially dead in the Americas and Europe...and increasingly rare in the territories where it is clinging on. IE7 is close to dropping under 2%. Firefox 3.6 is no longer supported by Mozilla. Safari 4 died ages ago.

    Going forward, we shouldn't actively support these browsers in the HTML5 Boilerplate project. If in the future someone absolutely needs legacy support for a specific project they are working on, then they can download the last stable release of HTML5 Boilerplate that supports it - it will do the job perfectly well.

    Probable changes involved in dropping IE 6/7, Firefox 3.6, Safari 4:

    • Changes to conditional comments around opening html tag.
    • Switch to normalize.css v2
    • Update main.css to remove any IE 6/7 hacks
    • Change version of IE that gets Chrome Frame prompt.
    opened by necolas 96
  • Remove IE conditional classes

    Remove IE conditional classes

    We should consider their complete removal from the HTML5 Boilerplate template. A good time to do it would be as part of #1050 when IE 6/7 support is dropped for version 5.0.


    • You can easily develop without them (personally, I've never used them).
    • For IE 8+, their use is much more limited.
    • IE 10+ will not support conditional comments.
    • We don't explicitly target any other browser versions in the same way.
    • It would fix whatever is going on in the very long-standing issues about the X-UA-Compatible meta tag. See #1187.

    Hopefully, even "conditional IE class" users will view them as disposable in an IE 8+ development setting. If you need IE 6/7 support, the last 4.* release will still cater to your needs. However, feedback is welcome!

    awaiting feedback 
    opened by necolas 85
  • rewrite project css as scss

    rewrite project css as scss

    It'd be better for us to author the styles in scss.

    We can still host the css in the repo for newbs that can't be bothered with a compass compile step

    overall advantages:

    • easier for most authors to begin scaling their styles
    • better authoring experience
    • integrated error checking
    • don't need to rewrite everything (like a Sass dialect would require)

    individual advantages

    • hotpink color could be a variable
    • :selection styles DRYd up
    • box-sizing mixin for input[type=search]
    • probably something very clever with our nonsemantic helper classes
    • probably more than i'm missing


    • one more step. (not if you're using livereload, codekit, etc)
    • double file checkin for css changes (not that they happen often)
    opened by paulirish 85
  • Drop IE8 support

    Drop IE8 support

    Microsoft is ending the extended support for Windows XP on April 8, 2014. Since IE8 is mostly a Windows XP browser, and it's market share is slowly but steadily going down¹ , I think we should start the discussion on dropping IE8 support.

    ¹ Some current estimates (feel free to share your own/other):

    Changes involved with dropping IE8 support:

    • Remove IE8 related code
    • Switch to jQuery 2.x.x
    • Update conditional comments for "browse happy" prompt
    • Remove html5shiv?
    • Update documentation
    • Other (which?)
    awaiting feedback 
    opened by alrra 77
  • Revert mobile-first media queries and remove respond.js

    Revert mobile-first media queries and remove respond.js

    IE6-8 require respond.js to act as a polyfill because H5BP uses mobile-first media queries.

    I'm not convinced mobile-first media queries are best.

    1. Clearly they have this extra cost for IE baked in.
    2. Secondly, it's a little awkward, as a developer, to write your styles mobile first.

    What mobile browsers (in use, currently) do not support media queries? Moreover, of the ones who don't, are there browsers that don't scale the content to somehow adapt to the small screen size?

    I don't know enough of the Blackberry/Nokia product line to know what's up on this front. But I have a feeling the mobile-first MQ setup is a lot of work. And the payoff is not worth the effort.

    javascript css documentation 
    opened by paulirish 74
  • A build script is necessary

    A build script is necessary

    • js/css concat and minification
    • html minification
    • filename revving for far-future expries.
    • image optimization (jpegtran, pngcrush, etc)

    others: http://daverupert.com/2010/06/web-performant-wordpress/

    I'm unsure on how this could be added to the project in a general way.. something php/ruby/py/html folks could all use it.

    opened by paulirish 74
  • IE conditional comments around html tag adds Compat View icon to address bar

    IE conditional comments around html tag adds Compat View icon to address bar

    Even though the doctype is HTML5 recommended and the X-UA-Compatible meta tag is present, by putting the HTML tag in a series of IE conditional comments, IE refuses to believe that the website is indeed "modern" and puts the dreaded "Compatibility View" button in the address bar.

    The way I get around this is by using JavaScript to add the ie6/7/whatever classes.


    <html class="no-js" lang="en">
    <!--[if lt IE 7 ]>
        <script src="js/libs/dd_belatedpng.js"></script>
        <script> DD_belatedPNG.fix('img, .png_bg'); var ie = "ie6"; </script>
    <!--[if IE 7 ]> <script> var ie = "ie7"; </script> <![endif]-->
    <!--[if IE 8 ]> <script> var ie = "ie8"; </script> <![endif]-->
    if(typeof ie !== 'undefined') $('html').addClass(ie); // in js/script.js

    I'm sure there are better ways to handle this, but this works as expected.

    opened by DingoEatingFuzz 67
  • Look into updating .ir to use a

    Look into updating .ir to use a "new and improved" method

    This article claims that -9999px (or -999em in our case) has noticeable performance issues when running animations on the iPad 1.

    Performance is dramatically improved because a 9999px box is not drawn. Noticeably so in animations on the iPad 1.

    The new CSS would be something like:

    .ir {
        text-indent: 100%;
        white-space: nowrap;
        overflow: hidden;

    Also, H5BP has some non-obvious tweaks in the existing .ir class that would need to be evaluated if this new method were to be implemented.

    opened by davidmurdoch 52
  • Move our build script over to Rake

    Move our build script over to Rake

    I'm thinking we should move from the Ant build script to something else..


    • XML is gross. Therefore the build.xml is less than sexy.
    • ant build files are a pain to read and learn from
    • ant build files are not very easy to maintain. we have a lot of unsolved issues and such
    • using java hasnt been the cross-platform magic that i was hoping for.

    However, what is does is hugely useful.

    We're thinking about using Sass and Compass in the build cycle in order to get @import inlining for our stylesheet optimization. This introduces a Ruby dependency. (However I will note that I have nearly successfully campaigned a YUI Compressor (which we're currently using) developer to add the @import inlining feature)

    So if we need ruby in the build process.. Let's just go for it. Rakefiles are wayyy better and more readable than Ant build files.

    Things to be done:

    • Find experts
    • Get an estimate on level of difficulty on porting the script
    • Determine a lead
    • Port it
      • Hopefully breaking this step up into a few developers, if possible
    • ???
    • Profit? Nah, bro we're public domain. Benefit!!!

    Relevant links:

    Guys that are interested in helping (and have experience with Rake):

    • @joshuaclayton
    • https://twitter.com/#!/KushalP
    • https://twitter.com/#!/AlexGraul
    • @markupboy
    • https://twitter.com/#!/halfcube
    • @akahn

    (alternatively if anyone reading this thinks we should stick with Ant and wants to take the lead on iterating on it... by all means please speak up! :)

    opened by paulirish 49
  • [question] How to publish static assets?

    [question] How to publish static assets?

    I'm submitting a ...

    • [ ] bug report
    • [ ] feature request
    • [x] other (Please do not submit support requests here (below))

    How to I make static assets available on the published website? I want to publish at mywebsite.com/some-image.png so I can use it as an OpenGraph image (which does not allow relative URL).

    I tried to create a public folder and a static folder but they are not copied on build.

    I feel this info should be in HTML5Boilerplate docs.

    Sorry in advance if missed it but I read the docs (I checked the README, Usage, the FAQ Miscellaneous and Extending), I searched Parcel docs, Github Issues issues, SO.

    opened by xididri 2
  • VS Code Integration?

    VS Code Integration?

    Is there something we can do there? Don't mind me, I'm just looking for interesting stuff to do as I try to amp up my OS contributions over this summer.

    opened by roblarsen 5
  • Alert on attempt to use Topics API

    Alert on attempt to use Topics API

    As multiple third-party scripts might be added to a site during development, it can be difficult to see when a script is attempting to use new browser features that might have privacy consequences.

    Consider adding a simple alert so that scripts can be checked and/or the site Permissions-Policy set before deploying to production.

    The "alert" is for development purposes, and could be replaced with an analytics event if a site wants to monitor attempted use of Topics API by third parties in production.

    Related: https://github.com/h5bp/html5-boilerplate/pull/2459

    Types of changes

    • [ ] Bug fix (non-breaking change which fixes an issue)
    • [x ] New feature (non-breaking change which adds functionality)
    • [ ] Breaking change (fix or feature that would cause existing functionality to change)


    • [ x] My code follows the code style of this project.
    • [ x] My change requires a change to the documentation.
    • [ x] I have updated the documentation accordingly.
    • [ x] I have read the CONTRIBUTING document.
    • [ ] I have added tests to cover my changes.
    • [ ] All new and existing tests passed.

    Pull requests should be thought of as a conversation. There will be some back and forth when trying to get code merged into this or any other project. With all but the simplest changes you can and should expect that the maintainers of the project will request changes to your code. Please be aware of that and check in after you open your PR in order to get your code merged in cleanly.


    opened by dmarti 4
  • Use GitHub Issue Form Templates

    Use GitHub Issue Form Templates

    I'm submitting a ...

    • [ ] bug report
    • [x] feature request
    • [ ] other (Please do not submit support requests here (below))

    GitHub offers neat Issue templates. You can have required checklists so users can't ignore that they've read through the issue requirements. I think it would be very helpful to add 'Bug Report' and 'Request Feature' forms. A user will still have the option to create a new blank issue if necessary.

    I'm hopeful this will cut down on back and forth requesting more info for bug reports as well as hopefully cutting down on users testing issues without adding anything which creates extra noise for everyone.

    A user is already expected to check if an issue has been opened already before creating a new one but unfortunately our closed issues are full of users testing which makes it more of a hassle. :-(

    I've recently created some forms for some other open source projects so I'll open a PR for this.

    opened by coliff 0
  • v7.3.0(Nov 19, 2019)

  • v7.2.0(Jun 4, 2019)

  • v7.1.0(Mar 20, 2019)

  • v7.0.1(Feb 12, 2019)

  • v7.0.0(Feb 8, 2019)

    These many and glorious things:

    • Drop support for IE9/IE10 (usage of these versions is tiny and Microsoft officially ended support back in 2016. (#2074)
    • Move the CSS to a separate repo (#2066)
    • Add theme-color meta tag to index.html (#2074)
    • Add 'install with yarn' steps to README (#2063)
    • Improved Webmanifest (#2060)
    • Upgrade Normalize to 8.0.1 (#2104)
    • Update .htaccess (#2110)
    • Remove instances of shrink-to-fit=no (#2103)
    • Removes "display": "standalone" from manifest (#2096)
    • Big Docs update - Fixed links, removed IE9/IE10 specific info, made touch icons section more concise, add details on security.txt and more tidying up (#2074, #2065, #2062)
    Source code(tar.gz)
    Source code(zip)
    html5-boilerplate_v7.0.0.zip(87.86 KB)
  • 6.1.0(May 1, 2018)

    All this stuff!

    Update Apache Server Configs to v3.0.0. Migrate to eslint (#2037) Update to jQuery 3.3.1 (#2018) Update to Modernizr v3.6 and Normalize v8 (#2028) Update Dev Dependencies (#2032) (#2017) (#2010) (#2009) Replace 'node-sri' with 'ssri' (#2031) Add .babelrc and .prettierrc to .gitattributes (#2030) Update .htaccess (#2003) Fixed JSHint errors (#1994) Add CODE_OF_CONDUCT.md (#2011) Update Documentation (#2029) (#2015) (#2007) (#2006) (#1996)

    Source code(tar.gz)
    Source code(zip)
    html5-boilerplate_v6.1.0.zip(88.71 KB)
  • 6.0.1(Sep 11, 2017)

  • 6.0.0(Aug 17, 2017)

    • Fix Bug: .visuallyhidden on macOS VO fixes #1985 (#1989)
    • Adds web app manifest file (#1963)
    • Update to jQuery 3.2.1 (#1942)
    • Improve ::selection documentation which became confusing after c7057be (#1955)
    • refactor(html): update browsehappy to https instead of http (#1952)
    • Fix links to CONTRIBUTING.md (#1951)
    • Adds .github folder and contents Fixes (#1948)
    • Modernizr 3, modernizr.config and (#1940)
    • Housekeeping by @coliff (#1968 #1969 #1965 #1964 #1958 #1957 #1956)
    • Update .gitattributes for Web Projects (#1935)
    • Add the link for useful .gitignore templates (#1936)
    • Node plumbing updated (#1925) (#1928) (#1931)
    • Use es2015 syntax in mocha tests (#1788)
    • Scope :first-letter selector for print styles (#1904)
    • Add SRI Hash for jQuery (#1904)
    • Update .jshintrc (#1903)
    • Improve accessibility with visuallyhidden content (#1900)
    • Tell users that IE 8 and 9 are outdated (#1747).
    • Removed IE8 Support (upgrades jQuery and normalize.css to latest) (#1524).
    • Fix print styles for Internet Explorer 11 (#1799).
    • Update doc links to https (#1889).
    • Delete crossdomain.xml (#1881).
    • Adds pre-wrap to PRE (#1742).
    • Change license format to SPDX format (#1814).
    • Simplify the Google Analytics snippet using async & defer (#1660).
    Source code(tar.gz)
    Source code(zip)
    html5-boilerplate_v6.0.0.zip(87.57 KB)
  • 5.3.0(Jan 12, 2016)

  • 5.2.0(Apr 30, 2015)

  • 5.1.0(Apr 1, 2015)

  • v5.0.0(Feb 2, 2015)

    • Update to jQuery 1.11.2.
    • Update Apache Server Configs to v2.11.0.
    • Rename Apple touch icon to apple-touch-icon.png and add <link> in index.html (#1622).
    • Add vertical centering for iframe (#1613).
    • Change the outdated browser prompt classname to browserupgrade (#1608).
    • Update to Normalize.css 3.0.2. (#1050).
    • Update apple-touch-icon-precomposed.png and the "Apple touch icons" related documentation (#1599).
    • Add pseudo-elements to universal selector in print media query (#1585).
    • Update to Modernizr 2.8.3.
    • Remove need to readjust margins in 404.html (#1567).
    • Add /.editorconfig file (#1561, #1564).
    • Add auto to the Google Universal Analytics tracker create method (#1562).
    • Add timeline and timelineEnd to the list of console methods (#1559).
    • Add lang="" to <html> (#1542).
    • Use <!doctype html> instead of <!DOCTYPE html> (#1522).
    • Add /browserconfig.xml file and tile images (#1481).
    • Add Disallow: to robots.txt (#1487).
    • Remove default foreground color from form elements (#1390).
    • Remove default margin from print styles (#1477).
    • Remove image replacement helper class .ir (#1472, #1475).
    • Add vertical centering for svg (#1453).
    • Redesign 404 page (#1443).
    • Remove IE 6/7 hacks from main.css (#1050).
    • Remove IE conditional classes (#1187, #1290).
    Source code(tar.gz)
    Source code(zip)
    html5-boilerplate_v5.0.0.zip(102.64 KB)
  • v4.3.0(Sep 10, 2013)

    • Use one apple-touch-icon instead of six (#1367).
    • Move font-related declarations from body to html (#1411).
    • Update to Apache Server Configs 1.1.0.
    • Add initial-scale=1 to the viewport meta (#1398).
    • Vertical centering for audio-, canvas- and video-tags (#1326).
    • Remove Google Chrome Frame related code (#1379, #1396).
    • Update to Google Universal Analytics (#1347).
    • Update to jQuery 1.10.2.
    • Update to Normalize.css 1.1.3.
    Source code(tar.gz)
    Source code(zip)
  • v4.2.0(Jun 27, 2014)

    • Remove Google Analytics protocol check (#1319).
    • Update to Normalize.css 1.1.1.
    • Update Apache configurations to include the latest changes in the canonical .htaccess file.
    • Use a protocol relative URL for the 404 template script.
    • Update to jQuery 1.9.1.
    Source code(tar.gz)
    Source code(zip)
  • v4.1.0(Jun 27, 2014)

  • v4.0.3(Jun 27, 2014)

  • v4.0.2(Jun 27, 2014)

  • v4.0.1(Jun 27, 2014)

  • v4.0.0(Jun 27, 2014)

    • Improve the Apache compression configuration (#1012, #1173).
    • Add a HiDPI example media query (#1127).
    • Add bundled docs (#1154).
    • Add MIT license (#1139).
    • Update to Normalize.css 1.0.1.
    • Separate Normalize.css from the rest of the CSS (#1160).
    • Improve console.log protection (#1107).
    • Replace hot pink text selection color with a neutral color.
    • Change image replacement technique (#1149).
    • Code format and consistency changes (#1112).
    • Rename CSS file and rename JS files and subdirectories.
    • Update to jQuery 1.8 (#1161).
    • Update to Modernizr 2.6.1 (#1086).
    • Remove uncompressed jQuery (#1153).
    • Remove superfluous inline comments (#1150).
    Source code(tar.gz)
    Source code(zip)
  • v3.0.2stripped(Jun 27, 2014)

  • v3.0.2(Jun 27, 2014)

  • v3.0.1stripped(Jun 27, 2014)

  • v3.0.1(Jun 27, 2014)

  • v3.0(Jun 27, 2014)

    • Improvements to .htaccess.
    • Improve 404 design.
    • Simplify JS folder structure.
    • Change html IE class names changed to target ranges rather than specific versions of IE.
    • Update CSS to include latest normalize.css changes and better typographic defaults (#825).
    • Update to Modernizr 2.5 (includes yepnope 1.5 and html5shiv 3.2).
    • Update to jQuery 1.7.1.
    • Revert to async snippet for the Google Analytics script.
    • Remove the ant build script (#826).
    • Remove Respond.js (#816).
    • Remove the demo/ directory (#808).
    • Remove the test/ directory (#808).
    • Remove Google Chrome Frame script for IE6 users; replace with links to Chrome Frame and options for alternative browsers.
    • Remove initial-scale=1 from the viewport meta (#824).
    • Remove defer from all scripts to avoid legacy IE bugs.
    • Remove explicit Site Speed tracking for Google Analytics. It's now enabled by default.
    Source code(tar.gz)
    Source code(zip)
  • v3.0stripped(Jun 27, 2014)

  • v2.0(Jun 27, 2014)

    • Change starting CSS to be based on normalize.css instead of reset.css (#500).
    • Add Respond.js media query polyfill.
    • Add Google Chrome Frame script prompt for IE6 users.
    • Simplify the html conditional comments for modern browsers and add an oldie class.
    • Update clearfix to use "micro clearfix".
    • Add placeholder CSS MQs for mobile-first approach.
    • Add textarea { resize: vertical; } to only allow vertical resizing.
    • Add img { max-width: 100%; } to the print styles; prevents images being truncated.
    • Add Site Speed tracking for Google Analytics.
    • Update to jQuery 1.6.2 (and use minified by default).
    • Update to Modernizr 2.0 Complete, Production minified (includes yepnope, html5shiv, and Respond.js).
    • Use Modernizr.load() to load the Google Analytics script.
    • Much faster build process.
    • Add build script options for CSSLint, JSLint, JSHint tools.
    • Build script now compresses all images in subfolders.
    • Build script now versions files by SHA hash.
    • Many .htaccess improvements including: disable directory browsing, improved support for all versions of Apache, more robust and extensive HTTP compression rules.
    • Remove handheld.css as it has very poor device support.
    • Remove touch-icon link elements from the HTML and include improved touch-icon support.
    • Remove the cache-busting query paramaters from files references in the HTML.
    • Remove IE6 PNGFix.
    Source code(tar.gz)
    Source code(zip)
  • v2.0stripped(Jun 27, 2014)

This is a template project demonstrating how the MERN stack(Mongo, Express, React, Node) can be used, here we have the back end implementation and there is the React implementation as the front end

Versão em português MERN stack This is a template project demonstrating how the MERN stack(Mongo, Express, React, Node) can be used, here we have the

Douglas Samuel Gonçalves 2 Jan 22, 2022
Webplate is an awesome front-end framework that lets you stay focused on building your site or app all the while remaining really easy to use.

Webplate Framework Webplate is an awesome front-end framework that lets you stay focused on building your site or app all the while remaining really e

Chris Humboldt 560 Nov 24, 2022
Node Express Template (NET.ts) - a small template project which help you to speed up the process of building RESTful API

Node Express Template (NET.ts) - a small template project which help you to speed up the process of building RESTful API

Przemek Nowicki 26 Jan 4, 2023
Opinionated SvelteKit Template for building web applications.

Opinionated SvelteKit Template for building web applications.

Manassarn 7 Jan 1, 2023
A boilerplate application for building Node.js back-end application in TypeScript

RESTful API Node Server Boilerplate A boilerplate/starter project for quickly building RESTful APIs and with typescript ?? Installation Install the de

Youssef Hajjari 14 Nov 23, 2022
IDE and toolkit for building scalable web applications with React, Redux and React-router

An all-in-one solution for creating modern React apps Rekit is a toolkit for building scalable web applications with React, Redux and React-router. It

Rekit 4.5k Jan 2, 2023
An experiment in building a public facing personal knowledge web app with TiddlyWiki and Nodejs.

Maarfapad What is this? Maarfapad was my attempt at learning Expressjs back in 2016 while building a CRUD app to handle TiddlyWiki html files. It was

A.B. Samma 3 Mar 12, 2022
A toolkit for React, Preact, Inferno & vanilla JS apps, React libraries and other npm modules for the web, with no configuration (until you need it)

nwb nwb is a toolkit for: Quick Development with React, Inferno, Preact or vanilla JavaScript Developing: React Apps Preact Apps Inferno Apps Vanilla

Jonny Buchanan 5.5k Jan 3, 2023
A boilerplate for building production-ready RESTful APIs using Node.js, Express, and Mongoose

By running a single command, you will get a production-ready Node.js app installed and fully configured on your machine. The app comes with many built-in features, such as authentication using JWT, request validation, unit and integration tests, continuous integration, docker support, API documentation, pagination, etc. For more details, check the features list below.

Hagop Jamkojian 5k Dec 31, 2022
Solana Boilerplate - Lightweight boilerplate for Solana dapps. Allows quick building and prototyping.

Lightweight boilerplate for Solana dapps. Allows quick building and prototyping. Feel free to contribute or fork this repository. Make it yours! Leave us a ⭐️ if this repo helped you.

null 21 Nov 15, 2022
Starting a new JS app? Build, test and run advanced apps with kyt 🔥

kyt Every sizable JavaScript web app needs a common foundation: a setup to build, run, test and lint your code. kyt is a toolkit that encapsulates and

The New York Times 1.9k Dec 26, 2022
A simple environment to start building on Starknet with Cairo

Starknet Boilerplate A simple environment to start building on Starknet with Cairo. Uses Nile for compilation/deployment and Starknetjs for contract i

threepwave 19 Dec 11, 2022
A simple Fast CLI that create Express+Mongoose MVC pattern

express-schema-generator Site | Docs | Contributing | Code of Conduct | Twitter | Chat Bored Writing and Creating the Same Express MVC Folders Again a

Shantanu Bombatkar 10 Aug 15, 2022
A simple Vue3, Nuxt3 and Tailwind3 Starter Template

Nuxt 3 + Tailwind CSS 3 Starter This is a minimal starter template for Nuxt 3 projects with Tailwind CSS 3. It includes a simple template pages/index.

Rizkhal 1 Feb 11, 2022
Next Boilerplate was created to be a template for starting NextJS projects with pre-configured settings like Linters, Test Setup, Storybook and Commit Hooks.

Next Boilerplate was created to be a template for starting NextJS projects with pre-configured settings like Linters, Test Setup, Storybook and Commit Hooks.

Claudio Orlandi 4 Feb 22, 2022
A template repository for Deno, GraphQL, and Svelte projects

Svelte is an innovative approach to frontend software development, the component model, and reactivity features creates simplistic approach to some hard problems. Svelte runs on the front end and is known as a Single Page Application.

hyper 15 Dec 20, 2022
A Node template that follows the Clean Architecture principles and encourages established practices.

Clean Architecture Template A Node template that follows the Clean Architecture principles and encourages established practices. Features TypeScript f

Jamie Livingstone 91 Dec 25, 2022
A cli tool to generate cra-template from current create-react-app project.

Create Cra Template A cli tool to generate cra-template from current create-react-app project. Create Cra Template Templates cra-template-popular cra-

Yoki 23 Aug 18, 2022
A generic template for starting Web3 Projects

Redwood WARNING: RedwoodJS software has not reached a stable version 1.0 and should not be considered suitable for production use. In the "make it wor

Dennison Bertram 18 Jun 28, 2022