Patternugit

Patterns are the keys.
Contribute to us / View tags / Report a bug

About the project

Many projects lack sufficient development and preparation in the area of their environment and sometimes are not intended as such at all due to the overall complexity, time-consuming and non-adaptive nature of such a process¹.

With this project, all you have to do is run some scripts, edit the necessary data and add your own basic project plugins and you will have a fully customized project from an open source perspective, ready for a development environment not only for you but for others as well.

Built-with

Project is created and "written" with help of:

Getting started

Before asking questions, read this block because here is all the primary information on the project, which can answer your future not-yet asked questions.

Prerequisites

For usage of this project just as template for your repository, there is no direct prerequisites besides Node.js.

But, for contributing to this project, we highly recommending following those prerequisites:

• Installed Node.js on your desktop on which you will edit/setup this project;
• Installed Python if you want to contribute to the scripts of this project (in terms of .PY scripts);
• It is recommended to use GitHub CLI on your machine for better experience via working not only within this project, but this the .GIT in entirety;

[^]

Installation

Permission is granted for free use in any of your products.

If you want to use this project, there are two ways to download-and-use this project: "official" and direct, so, let's start from official path:

1. Go up to the "main position" of page of this repository and seek for the "Use this template" button;
2. Click on this button and seek for the specified variants "Use this template → Create a new repository", or option with codespaces;
3. Use project, edit anything you want.

Guidelines for direct-installation way:

1. Download last tag on project's repository, for the last ZIP-tarball link provided below:
   download latest release
   • or just download the source-code through "Code → Download ZIP (or any option that you want)", and proceed to the next step;
2. Within downloaded ZIP (or project), clone everything and paste to the directory of your project via "copy+paste" procedure;
3. Now, you can use project just as if you installed it from other algorithms.

Guidelines for installation of source code of this project:

1. Clone the repository with any form of app which supports Git (or CLI of this site), guide is attached:
   https://www.howtogeek.com/451360/how-to-clone-a-github-repository/
2. Open it with any suitable for you editor and feel free to customize, update and/or contribute to this project².

[^]

Usage

Usage of this project is very easy and comfortable for common user, its not provided with any advanced code or anything, it just the "data" which user must interpretate as it wants.

1. Go to your project's directory and paste the contents of this template, which were installed with help of installation guides³;
2. Now, you can continue to work on your project with this template's data in it.

Before preparing to work on the projects that you prepared, initialize entire repository via initialize and prepare commandlets of npm (through either bash or powershell):

# Installing every dependency for package:
npm i
# Using prepare script for this repository:
npm run prepare:main

After setting up project's template within custom provided script, it is recommended to follow this algorithm:

1. You MUST update .GITIGNORE file, for more information and sources, check .GITIGNORE-README;
2. You MUST update .GITATTRIBUTES file, for more information and sources, check .GITATTRIBUTES-README;
3. If you don't use DOCKER/KUBERNETES, do this:
   REMOVE any related file either to DOCKER or KUBERNETES;
4. It is RECOMMENDED to set up custom workflows for your code;
5. It is RECOMMENDED to set up custom attributes for .GITCONFIG of your project (check GitHub subdirectory);
6. It is RECOMMENDED to read applied in this template documentation, you may disagree or want to edit it up;
7. It is RECOMMENDED to update LICENSE and readme according to your project (image is from readme template, for references see links below).

[^]

Roadmap

• Upgrade and update project to the second version generation;
• Refactor to project according to integrated linters and pass the checks within future;
• Write small pages site which contains philosophy and common ideology of project and how to use it;
  • Format and style it;
• Write a Markdown file which contains a pattern for philosohpies or ideologies for projects;
  • And write down a specified philosophy for this exact project;

[^]

Contributing

Contributions are what make open source community such an interest place to be in, so any form of contribution are greatly appreciated.

If you think that you can help this project become better but think its not so important/realizable in the current situtation or for a full contribution, use issues page, otherwise there is a guideline and policy for contributing.

If you want to contribute to this project, please, read contributioning policy and commit convention, this repository works with CLA, commits convention and on automated deployment system⁴.

For one-single file contributioning, use a more quicker way without forking the repository through site.

More about it in this article:

• "Working with forks" about syncing one-file fork;

[^]

License

Project thanks the Electron.js and Angular for their amazing repository scripts and entire infrastructure, which partially were imported to this repository.

For individual licensing and credits information, seek correspondive files and/or sources.

Project itself is being distributed under the MIT License — see the file for more specified information.

[^]

Contact

For any legal purposes, you can contact developer/maintainer through its email:

• Outlook email
  You can also check contact information in CODEOWNERS file within referencing our contacts.

If the developer/maintainer didn't answered, or you have other questions in nature, you can use issues page on this repository via specified templates or indirect self-written issue.

[^]

Acknowledgments

• https://shields.io/
• https://simpleicons.org/
• https://gitignore.io/
• https://gitattributes.io/
  • this generator is discontinued, use:
    https://richienb.github.io/gitattributes-generator/
• Best readme template

[^]

Footnotes

1. For this, please, read readme and keep in mind, that this is a template and if you want to, you could redefine entire structure of this file or entire repository. ↩

2. for contributing policy, see — CONTRIBUTING.md ↩

3. .../#installation ↩

4. read the files of commiting convention policy and contributioning policy ↩