dh-frontend-cookbook v1.6.1

Front-end Cookbook

Introduction

Collect, organize, unify and define all the necessary recipes you might need during your front-end development tasks at Docler Holding. It was a long-running request to define an environment where our developers can re-use our front-end codebase across products/projects to cut down development costs both short and long term. This also includes sharing complex features containing all the necessary business logic in some cases.

Be careful - get involved

This documentation is in alpha stage and many questions are still being an open discussion. It's goal to give a clear vision of where we're headed, what we want to achieve. We encourage you to open discussions on any topic.

How?

a. By ensuring interoperability for people and know-how across teams. The best way is to use what is already being out there in the front-end ecosystem known/used by many, without re-inventing the wheel. We're targeting the most common solutions and options to make our development process mainstream and easy to understand (Googling it :) ) even for new-comers.

b. By defining some strict rules/recommendations:

• Common naming conventions
• Coding conventions
• Project/package structures
• Development stack
• Deployment/CR/PR pipeline
• Rights and roles in a project