Some HTML, CSS and JS best practices.

A one-page questionnaire to help your team establish effective frontend guidelines, so that you can write consistent & cohesive code together.

📝 Front-end Guideline by Juntos Somos Mais

本文原文是一篇来自Github上@bendc的6,539星的文章,在此声明，原作者保有所有权利，本文仅供技术探讨学习。

No description available

O3 World’s Front-End (HTML & CSS) Coding Standards and Best Practices

D-ZERO Frontend Developer's Guideline

Opinionated guidelines for frontend projects at Applifting — from React patterns and TypeScript tips to data fetching, routing, and workflow.

前端约定

No description available

Mupen64plus frontend designed based on Elementary OS guidelines.

Frontend project scaffolds, folder structures, best practices guidelines

MyMoviePlan Project 4 DESCRIPTION Create a dynamic and responsive web application for booking movie tickets online for different genres and languages. Background of the problem statement: NMS Cinemas is a chain of single screen theatres that screen movie shows of different genres and languages at very genuine prices. It was established in 2004 in Pune, India. Recently, the business analysts noticed a decline in sales since 2010. They found out that the online booking of movie tickets from apps, such as BookMyShow and Paytm were gaining more profit by eliminating middlemen from the equation. As a result, the team decided to hire a Full Stack developer to develop an online movie ticket booking web application with a rich and user-friendly interface. You are hired as the Full Stack Java developer and are asked to develop the web application. The management team has provided you with the requirements and their business model so that you can easily arrange different components of the application. Features of the application: Registration Login Payment gateway Searching Filtering Sorting Dynamic data Responsive and compatible with different devices Recommended technologies: Database management: MySQL and Oracle Backend logic: Java programming, NodeJS Frontend development: JSP, Angular, Bootstrap, HTML/CSS, and Javascript Automation and testing technologies: Selenium, Jasmine, and TestNG DevOps and production technologies: Git, GitHub, Jenkins, Docker, Kubernetes, and AWS Project development guidelines: The project will be delivered within four sprints with every sprint delivering a minimal viable product. It is mandatory to perform proper sprint planning with user stories to develop all the components of the project. The learner can use any technology from the above-mentioned technologies for different layers of the project. The web application should be responsive and should fetch or send data dynamically without hardcoded values. The learner must maintain the version of the application over GitHub and every new change should be sent to the repository. The learner must implement a CI/CD pipeline using Jenkins. The learner should also deploy and host the application on an AWS EC2 instance. The learner should also implement automation testing before the application enters the CI/CD pipeline. The learner should use Git branching to do basic automation testing of the application in it separately. The learner should make a rich frontend of the application, which is user- friendly and easy for the user to navigate through the application. There will be two portals in the application, namely admin and user portal. Admin Portal: It deals with all the backend data generation and product information. The admin user should be able to: Add or remove different genres to or from the application to build a rich product line Edit movie details like name, ticket price, language, description, and show timings to keep it aligned to the current prices Enable or disable the movie shows from the application User Portal: It deals with the user activities. The end-user should be able to: Sign-in to the application to maintain a record of activities Search for movie tickets based on the search keyword Apply filters and sort results based on different genres Add all the selected movie tickets to a cart and customize the purchase at the end Experience a seamless payment process Receive a booking summary page once the payment is complete

CSS guidelines for large and maintainable frontend projects.

Mazecare's frontend coding guidelines

Frontend Guidelines for the Analytics Cloud team

Guidelines for True's frontend development practices and standards

【译文】一些HTML，CSS和JS的最佳实践。

GitHub Actions workflow that reviews frontend code against Vercel's Web Interface Guidelines using Claude AI. Non-blocking, educational feedback for accessibility, performance, and UX patterns.

Silverstripe's front-end coding guidelines

Oblique is the unified frontend ecosystem of the Swiss Confederation — encompassing all libraries, tools, guidelines and services that shape how we design, build, and maintain user interfaces. It provides a cohesive foundation for consistent, maintainable and high-quality frontend development across all projects.

Create a dynamic and responsive Java e-healthcare web application for ordering medicines of different categories. Background of the problem statement: Medicare is a company that supplies medicines and a couple of other healthcare essentials at an affordable price. It was established in 2012 in Delhi, India. It had been serving fine all these years, however, the business analysts noticed a decline in sales since 2017. They found out that online ordering of medicines with companies, such as 100mg and mfine are gaining more profits by eliminating middlemen from the equation. As a result, the team decided to hire a Full Stack developer to develop a healthcare web application with a rich and user-friendly interface. You are hired as the Full Stack Java developer and are asked to develop the web application. The management team has provided you with the requirements and their business model so that you can easily arrange different components of the application. Features of the application: Registration Login Payment gateway Searching Filtering Sorting Dynamic data Responsive and compatible with different devices Recommended technologies: Database management: MySQL and Oracle Backend logic: Java programming, NodeJS Frontend development: JSP, Angular, Bootstrap, HTML/CSS, and Javascript Automation and testing technologies: Selenium, Jasmine (frontend testing), and TestNG DevOps and production technologies: Git, GitHub, Jenkins, Docker, Kubernetes, and AWS Project development guidelines: The project will be delivered within four sprints with every sprint delivering a minimal viable product. It is mandatory to perform proper sprint planning with user stories to develop all the components of the project. The learner can use any technology from the above-mentioned technologies for different layers of the project. The web application should be responsive and should fetch or send data dynamically without hardcoded values. The learner must maintain the version of the application over GitHub and every new change should be sent to the repository. The learner must implement a CI/CD pipeline using Jenkins. The learner should also deploy and host the application on an AWS EC2 instance. The learner should also implement automation testing before the application enters the CI/CD pipeline. The learner should use Git branching to do basic automation testing of the application in it separately. The learner should make a rich frontend of the application, which is user-friendly and easy for the user to navigate through the application. There will be two portals in the application, namely admin and user portal. Admin Portal: The admin portal deals with all the backend data generation and product information. The admin user should be able to: Add or remove medicine details from the application to build a rich product line Edit medicine details like name, price, seller, product description, and offers to keep the product information updated with the current prices Enable or disable a medicine product User Portal: It deals with the user activities. The end-user should be able to: Sign-in to the application to maintain a record of activities Search for products based on the search keyword Apply filters and sort results based on different cuisines to get the best deals Add all the selected food items to the cart and customize the purchase at the end Perform a seamless payment gateway Get an order summary details page once the payment is complete

前段代码优化

Guidelines for Front-End Web Development

Opinionated Front-End Guidelines

Stamkracht frontend development guidelines.

A guidelines of Front-end developer

Design Guidelines for the JitCoin Client Frontend

DESCRIPTION Create a dynamic and responsive online food delivery web application for ordering food items of different cuisines from a restaurant. Background of the problem statement: Foodbox is a restaurant chain that delivers food items of different cuisines at affordable prices. It was established in 2014 in Bengaluru, India. It had been serving fine all these years, however, the business analysts noticed a decline in sales since 2016. They found out that the online ordering of food items with companies, such as Swiggy and Foodpanda were gaining more profit by eliminating middlemen from the equation. As a result, the team decided to hire a Full Stack developer to develop an online food delivery web application with a rich and user-friendly interface. You are hired as the Full Stack Java developer and are asked to develop the web application. The management team has provided you with the requirements and their business model so that you can easily arrange different components of the application. Features of the application: Registration Login Payment gateway Searching Filtering Sorting Dynamic data Responsive and compatible with different devices Recommended technologies: Database management: MySQL and Oracle Backend logic: Java programming, NodeJS Frontend development: JSP, Angular, Bootstrap, HTML/CSS, and Javascript Automation and testing technologies: Selenium, Jasmine, and TestNG DevOps and production technologies: Git, GitHub, Jenkins, Docker, Kubernetes, and AWS Project development guidelines: The project will be delivered within four sprints with every sprint delivering a minimal viable product. It is mandatory to perform proper sprint planning with user stories to develop all the components of the project. The learner can use any technology from the above-mentioned technologies for different layers of the project. The web application should be responsive and should fetch or send data dynamically without hardcoded values. The learner must maintain the version of the application over GitHub and every new change should be sent to the repository. The learner must implement a CI/CD pipeline using Jenkins. The learner should also deploy and host the application on an AWS EC2 instance. The learner should also implement automation testing before the application enters the CI/CD pipeline. The learner should use Git branching to do basic automation testing of the application in it separately. The learner should make a rich frontend of the application, which is user- friendly and easy for the user to navigate through the application. There will be two portals in the application, namely admin and user portal. Admin Portal: The admin portal deals with all the backend data generation and product information. The admin user should be able to: Add or remove different cuisines to or from the application to build a rich product line Edit food item details like name, price, cuisine, description, and offers to keep it aligned to the current prices Enable or disable the food items User Portal: It deals with the user activities. The end-user should be able to: Sign-in to the application to maintain a record of activities Search for food items based on the search keyword Apply filters and sort results based on different cuisines to get the best deals Add all the selected food items to a cart and customize the purchase at the end Perform a seamless payment process Get an order summary details page once the payment is complete

Guidelines for frontend developlment