From 8e592b5ec4a2d87ad3384d46d8a085864686ee33 Mon Sep 17 00:00:00 2001 From: Esther White Date: Mon, 17 Jun 2024 09:52:14 +0300 Subject: [PATCH] feat(templates): open source repo --- .github/FUNDING.yml | 3 + .github/ISSUE_TEMPLATE/bug_report.yml | 52 ++++ .github/ISSUE_TEMPLATE/config.yml | 5 + .github/ISSUE_TEMPLATE/feature_request.yml | 52 ++++ .github/PULL_REQUEST_TEMPLATE.md | 34 +++ .github/workflows/issue.yml | 28 ++ .github/workflows/triage.yml | 21 ++ CODE_OF_CONDUCT.md | 128 +++++++++ CONTRIBUTING.md | 289 +++++++++++++++++++++ LICENSE | 21 ++ README.md | 10 + SECURITY.md | 21 ++ analog.png | Bin 0 -> 2634 bytes anguhashblog-logo-readme.png | Bin 0 -> 4722 bytes angular-material.png | Bin 0 -> 3020 bytes index.html | 2 +- 16 files changed, 665 insertions(+), 1 deletion(-) create mode 100644 .github/FUNDING.yml create mode 100644 .github/ISSUE_TEMPLATE/bug_report.yml create mode 100644 .github/ISSUE_TEMPLATE/config.yml create mode 100644 .github/ISSUE_TEMPLATE/feature_request.yml create mode 100644 .github/PULL_REQUEST_TEMPLATE.md create mode 100644 .github/workflows/issue.yml create mode 100644 .github/workflows/triage.yml create mode 100644 CODE_OF_CONDUCT.md create mode 100644 CONTRIBUTING.md create mode 100644 LICENSE create mode 100644 SECURITY.md create mode 100644 analog.png create mode 100644 anguhashblog-logo-readme.png create mode 100644 angular-material.png diff --git a/.github/FUNDING.yml b/.github/FUNDING.yml new file mode 100644 index 0000000..b35e397 --- /dev/null +++ b/.github/FUNDING.yml @@ -0,0 +1,3 @@ +# These are supported funding model platforms + +github: [monacodelisa] diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml new file mode 100644 index 0000000..375c785 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.yml @@ -0,0 +1,52 @@ +name: 🐛 Bug report +description: Create a bug report to help us improve AnguHashBlog +title: "Bug: " +labels: [👀 needs triage, 🐛 bug] +body: + - type: markdown + attributes: + value: | + Thanks for taking the time to fill out this bug report! + - type: textarea + attributes: + label: Describe the bug + description: A clear and concise description of what the bug is. + validations: + required: true + - type: textarea + attributes: + label: Steps to reproduce + description: Describe how to reproduce the behavior. + placeholder: | + 1. Go to '...' + 2. Click on '...' + 3. Scroll down to '...' + 4. See error + validations: + required: true + - type: dropdown + attributes: + multiple: true + label: Browsers + description: Select the browsers where the issue can be reproduced (that you know of). + options: + - "Chrome" + - "Firefox" + - "Safari" + - "Edge" + - "Opera" + - "Other (add additional context)" + - type: input + id: context + attributes: + label: Additional context (Is this in dev or production?) + description: Add any other context about the problem or helpful links here. + + - type: checkboxes + id: assistance + attributes: + label: I would be willing to submit a PR to fix this issue + description: Assistance is provided if you need help submitting a pull request + options: + - label: "Yes and I have read the [Contribution Guide](https://anguhashblog.com/contributing) and I agree to follow this project's [Code of Conduct](https://anguhashblog.com/code-of-conduct)" + - label: 'No' \ No newline at end of file diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml new file mode 100644 index 0000000..0333e89 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -0,0 +1,5 @@ +blank_issues_enabled: false +contact_links: + - name: ❓ Ask a question + url: https://discord.com/invite/h3JXbADsBy + about: Ask questions about open source onboarding \ No newline at end of file diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml new file mode 100644 index 0000000..79cc457 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature_request.yml @@ -0,0 +1,52 @@ +name: 🚀 Feature request +description: Suggest an idea for this project 💡 +title: "Feature: " +labels: [👀 needs triage, 💡 feature] +body: + - type: markdown + attributes: + value: | + Thanks for taking the time to fill out this feature request! + - type: dropdown + attributes: + multiple: false + label: Type of feature + description: Select the type of feature request, the lowercase should also be the PR prefix. + options: + - "✨ Feature" + - "🐛 Fix" + - "📝 Documentation" + - "🎨 Style" + - "🧑‍💻 Refactor" + - "🔥 Performance" + - "✅ Test" + - "🤖 Build" + - "🔁 CI" + - "📦 Chore" + - "⏩ Revert" + validations: + required: true + - type: textarea + attributes: + label: Current behavior + description: Is your feature request related to a problem? Please describe. + validations: + required: true + - type: textarea + attributes: + label: Suggested solution + description: Describe the solution you'd like. + - type: input + id: context + attributes: + label: Additional context + description: Add any other context about the problem or helpful links here. + + - type: checkboxes + id: assistance + attributes: + label: I would be willing to submit a PR to fix this issue + description: Assistance is provided if you need help submitting a pull request + options: + - label: "Yes and I have read the [Contribution Guide](https://anguhashblog.com/contributing) and I agree to follow this project's [Code of Conduct](https://anguhashblog.com/code-of-conduct)" + - label: 'No' \ No newline at end of file diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md new file mode 100644 index 0000000..308b581 --- /dev/null +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -0,0 +1,34 @@ + +## This PR Closes Issue +closes # + +## Description + +## What type of PR is this? (check all applicable) + +- [ ] 🅰️ Feature +- [ ] 🐛 Bug Fix +- [ ] 📝 Documentation Update +- [ ] 🎨 Style +- [ ] 🧑‍💻 Code Refactor +- [ ] 🔥 Performance Improvements +- [ ] ✅ Test +- [ ] 🤖 Build +- [ ] 🔁 CI +- [ ] 📦 Chore (Release) +- [ ] ⏩ Revert + +## Mobile & Desktop Screenshots/Recordings +[Attach screenshots or recordings if applicable] + +## Steps to QA + +## Added to documentation? +- [ ] 📜 README.md +- [ ] 🙅 no documentation needed + +## [Optional] Post-deployment tasks +[Specify any post-deployment tasks that need to be performed] + +## [Optional] What gif best describes this PR or how it makes you feel? +[Embed gif or describe the feeling in plain text] diff --git a/.github/workflows/issue.yml b/.github/workflows/issue.yml new file mode 100644 index 0000000..06eeb41 --- /dev/null +++ b/.github/workflows/issue.yml @@ -0,0 +1,28 @@ +# This workflow posts an automated comment on every new issue +# https://github.com/marketplace/actions/create-or-update-comment (https://github.com/peter-evans/create-or-update-comment) + +name: Automatic Comment +on: + issues: + types: [opened] +permissions: + contents: read + +jobs: + comment: + permissions: + issues: write # for peter-evans/create-or-update-comment to create or update comment + pull-requests: write # for peter-evans/create-or-update-comment to create or update comment + name: Comment + runs-on: ubuntu-latest + steps: + - name: Automatic Comment + uses: peter-evans/create-or-update-comment@v2 + with: + issue-number: ${{ github.event.issue.number }} + body: | + Thanks for the issue, our team will look into it as soon as possible! If you would like to work on this issue, please wait for us to decide if it's ready. The issue will be ready to work on once we remove the "needs triage" label. + + To claim an issue that does not have the "needs triage" label, please leave a comment that says ".take". If you have any questions, please reach out to us on [Discord](https://discord.gg/SQCFCACz) or follow up on the issue itself. + + For full info on how to contribute, please check out our [contributors guide](https://anguhashblog.com/contributing). \ No newline at end of file diff --git a/.github/workflows/triage.yml b/.github/workflows/triage.yml new file mode 100644 index 0000000..ca30672 --- /dev/null +++ b/.github/workflows/triage.yml @@ -0,0 +1,21 @@ +name: "Assign issues with .take" + +on: + issue_comment: + types: + - created + - edited + +jobs: + take-issue: + name: Disable take issue + runs-on: ubuntu-latest + timeout-minutes: 10 + steps: + - name: take an issue + uses: bdougie/take-action@v1.6.1 + with: + issueCurrentlyAssignedMessage: Thanks for being interested in this issue. It looks like this ticket is already assigned to a contributor. + token: ${{ secrets.ACCESS_TOKEN }} + blockingLabels: 👀 needs triage,blocked,core team work,📛 prerequisites missing,needs design,duplicate + blockingLabelsMessage: The issue you are trying to assign yourself is blocked either by the 'needs triage' label, or by another label on the issue. Please wait until the issue is unblocked before assigning yourself. \ No newline at end of file diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 0000000..bfafa4c --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,128 @@ +# Contributor Covenant Code of Conduct + +## Our Pledge + +We as members, contributors, and leaders pledge to make participation in our +community a harassment-free experience for everyone, regardless of age, body +size, visible or invisible disability, ethnicity, sex characteristics, gender +identity and expression, level of experience, education, socio-economic status, +nationality, personal appearance, race, religion, or sexual identity +and orientation. + +We pledge to act and interact in ways that contribute to an open, welcoming, +diverse, inclusive, and healthy community. + +## Our Standards + +Examples of behavior that contributes to a positive environment for our +community include: + +* Demonstrating empathy and kindness toward other people +* Being respectful of differing opinions, viewpoints, and experiences +* Giving and gracefully accepting constructive feedback +* Accepting responsibility and apologizing to those affected by our mistakes, + and learning from the experience +* Focusing on what is best not just for us as individuals, but for the + overall community + +Examples of unacceptable behavior include: + +* The use of sexualized language or imagery, and sexual attention or + advances of any kind +* Trolling, insulting or derogatory comments, and personal or political attacks +* Public or private harassment +* Publishing others' private information, such as a physical or email + address, without their explicit permission +* Other conduct which could reasonably be considered inappropriate in a + professional setting + +## Enforcement Responsibilities + +Community leaders are responsible for clarifying and enforcing our standards of +acceptable behavior and will take appropriate and fair corrective action in +response to any behavior that they deem inappropriate, threatening, offensive, +or harmful. + +Community leaders have the right and responsibility to remove, edit, or reject +comments, commits, code, wiki edits, issues, and other contributions that are +not aligned to this Code of Conduct, and will communicate reasons for moderation +decisions when appropriate. + +## Scope + +This Code of Conduct applies within all community spaces, and also applies when +an individual is officially representing the community in public spaces. +Examples of representing our community include using an official e-mail address, +posting via an official social media account, or acting as an appointed +representative at an online or offline event. + +## Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behavior may be +reported to the community leaders responsible for enforcement at +monacodelisa@gmail.com. +All complaints will be reviewed and investigated promptly and fairly. + +All community leaders are obligated to respect the privacy and security of the +reporter of any incident. + +## Enforcement Guidelines + +Community leaders will follow these Community Impact Guidelines in determining +the consequences for any action they deem in violation of this Code of Conduct: + +### 1. Correction + +**Community Impact**: Use of inappropriate language or other behavior deemed +unprofessional or unwelcome in the community. + +**Consequence**: A private, written warning from community leaders, providing +clarity around the nature of the violation and an explanation of why the +behavior was inappropriate. A public apology may be requested. + +### 2. Warning + +**Community Impact**: A violation through a single incident or series +of actions. + +**Consequence**: A warning with consequences for continued behavior. No +interaction with the people involved, including unsolicited interaction with +those enforcing the Code of Conduct, for a specified period of time. This +includes avoiding interactions in community spaces as well as external channels +like social media. Violating these terms may lead to a temporary or +permanent ban. + +### 3. Temporary Ban + +**Community Impact**: A serious violation of community standards, including +sustained inappropriate behavior. + +**Consequence**: A temporary ban from any sort of interaction or public +communication with the community for a specified period of time. No public or +private interaction with the people involved, including unsolicited interaction +with those enforcing the Code of Conduct, is allowed during this period. +Violating these terms may lead to a permanent ban. + +### 4. Permanent Ban + +**Community Impact**: Demonstrating a pattern of violation of community +standards, including sustained inappropriate behavior, harassment of an +individual, or aggression toward or disparagement of classes of individuals. + +**Consequence**: A permanent ban from any sort of public interaction within +the community. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], +version 2.0, available at +https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. + +Community Impact Guidelines were inspired by [Mozilla's code of conduct +enforcement ladder](https://github.com/mozilla/diversity). + +[homepage]: https://www.contributor-covenant.org + +For answers to common questions about this code of conduct, see the FAQ at +https://www.contributor-covenant.org/faq. Translations are available at +https://www.contributor-covenant.org/translations. diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..9bfc3b8 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,289 @@ +# Contributing to AnguHashBlog + +First off, thanks for taking the time to contribute! ❤️ + +All types of contributions are encouraged and valued. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions. 🎉 + +- [Code of Conduct](#code-of-conduct) +- [Question or Problem?](#question-or-problem) +- [Features vs Bugs](#features-vs-bugs) +- [For all Issues](#for-all-issues) +- [Submitting an Issue](#submitting-an-issue) +- ['Needs Triage' issue label](#needs-triage-issue-label) +- [Standardization Across App Versions](#standardization-across-app-versions) +- [Before you start working on an Issue](#before-you-start-working-on-an-issue) +- [Submitting a Pull Request (PR)](#submitting-a-pull-request-pr) +- [Reviewing a Pull Request](#reviewing-a-pull-request) +- [Coding Rules](#coding-rules) +- [Commit Message Guidelines](#commit-message-guidelines) + +And if you like the project, but just don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about: + +- Star the project +- Tweet about it +- Refer this project in your project's readme +- Mention the project at local meetups and tell your friends/colleagues + +## Code of Conduct + +This project and everyone participating in it is governed by the +[Code of Conduct](/CODE_OF_CONDUCT.md). +By participating, you are expected to uphold this code. Please report unacceptable behavior +to [monacodelisa](https://github.com/monacodelisa). + +## Question or Problem? + +Do not open issues for general support questions as we want to keep GitHub issues for bug reports and feature requests. +Instead, we recommend using Discussions to ask support-related questions. + +## Features vs Bugs + +Not all issues are bug fixes! Please understand the difference between a Feature and a Bug when it comes to issue creation. + +- **FEATURE** - when you are implementing something new that has not been worked on before +- **BUG** - when you are correcting something that has been worked on before but is not functioning as intended + +## For all Issues +### First open an issue and outline your proposal so that it can be discussed. + +This process allows us to better coordinate our efforts, prevent duplication of work, and help you to craft the change so that it is successfully accepted into the project. + +## Submitting an Issue + +Before opening an issue, please search through Issues to see if a similar issue has been raised. Existing discussions may provide useful insights or workarounds. + +To expedite bug fixes, a minimal reproduction of the issue is required. This concise example helps in swiftly identifying and addressing the problem. + +Providing a minimal reproduction is crucial for saving time, increasing the chances of a quick resolution, and ensuring that focus is given to the correct issue. + +**DO NOT** erase the provided issue template! It is intended for you to use, not to replace it with random text. + +It is always a good practice to look up existing issues and ensure your new issue matches the established +format. This helps maintain consistency and makes it easier for others to understand and collaborate on the +issue + +## 'Needs Triage' issue label + +Every new issue is tagged with the "needs triage" label, signifying that it requires review and assessment by a core team member. This process ensures that issues are appropriately prioritized and assigned, fostering a collaborative environment where tasks are synchronized to prevent conflicts. While you focus on addressing an issue, it's important to recognize that others may be working on related tasks. Therefore, the "needs triage" label serves as a precautionary measure, indicating that the issue is not yet ready for immediate attention. The issue will be ready to work on, once the "needs triage" label is removed. + +# Standardization Across App Versions + +All app versions maintain consistent file structures, functionalities, and feature implementations deliberately. The variations between versions are minimal, primarily revolving around the utilization of UI components where a UI library is used. + +Once an issue has been resolved in one app version, the same implementation must be extended to all other versions, unless a superior alternative is proposed and accepted. + +Any new implementation suggestion must be discussed to verify it's suitable for adoption across all app versions. For a good visual representation use the [Issue Tracker](https://anguhashblog.com/issue-tracker) + +## Before you start working on an Issue + +Before commencing work on any issue, it is essential to confirm that it has not already been addressed. Utilize the [Issue Tracker](https://anguhashblog.com/issue-tracker) tool to check for existing implementations and their corresponding app versions. If the chosen issue has already been resolved in a different app version, consult the [Issue Tracker](https://anguhashblog.com/issue-tracker) to review the existing implementation and replicate it accordingly. + +Even if the issue is labeled as not implemented, it remains your responsibility to examine the app's codebase and confirm the absence of the issue. + +## Submitting a Pull Request (PR) + +Before you submit your Pull Request (PR) consider the following guidelines: + +1. Search [AhguHashBlog](https://github.com/AnguHashBlog) for an open or closed PR that relates to your submission. + You don't want to duplicate existing efforts. + +2. Be sure that an issue describes the problem you're fixing, or documents the design for the feature you'd like to add. + Discussing the design upfront helps to ensure that we're ready to accept your work. + +3. [Fork](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo) the `AnguHashBlog` repo of your choice. + +4. In your forked repository, make your changes in a new git branch: + + ```shell + git checkout -b my-fix-branch develop + ``` + +### The default branch is develop! + +5. Create your patch, **including appropriate test cases**. + +6. Follow the [Coding Rules](#coding-rules) and [Commit Message Guidelines](#commit-message-guidelines). + +7. Run the full test suite, as described in the developer documentation, and ensure that all tests pass. + +8. Commit your changes using a descriptive commit message. + + ```shell + git commit --all + ``` + + Note: the optional commit `--all` command line option will automatically "add" and "rm" edited files. + +9. Push your branch to GitHub: + + ```shell + git push origin my-fix-branch + ``` + +10. In GitHub, send a pull request to `AnguHashBlog/analog-material:develop`. + +**DO NOT** erase the provided PR template! It is intended for you to use, not to replace it with random text. + +It is always a good practice to look up already merged PRs and ensure your new PR matches the established format. This helps maintain consistency and makes it easier for others to understand and collaborate. + +## Reviewing a Pull Request + +I reserve the right not to accept pull requests from community members who haven't been good citizens of the community. + +#### After your pull request is merged + +After your pull request is merged, you can safely delete your branch and pull the changes from the main (upstream) repository: + +- Delete the remote branch on GitHub either through the GitHub web UI or your local shell as follows: + + ```shell + git push origin --delete my-fix-branch + ``` + +- Check out the develop branch: + + ```shell + git checkout develop -f + ``` + +- Delete the local branch: + + ```shell + git branch -D my-fix-branch + ``` + +- Update your local `develop` with the latest upstream version: + + ```shell + git pull --ff upstream develop + ``` + +## Coding Rules + +To ensure consistency throughout the source code and the different app versions, keep these rules in mind as you are working: + +### FILE STRUCTURE + +#### Components + +Store full components that can be used on their own, in the `components` folder, examples include: + +- `header`, `footer`, `posts`, `series`, `post-details`, `layout`, `sidenav` + +#### Partial Components + +Place partial components like dialogs and other smaller reusable components, in the `partials` folder, examples: + +- `follow-dialog`, `search-dialog` + +### Interfaces + +Keep interfaces in the `models` folder, examples: + +- `blog-info.ts`, `post.ts` +- Avoid duplicating existing interfaces. + +#### Services + +- Place services in the `services` folder, examples: + - `blog.service.ts`, `theme.service.ts` + +#### Pipes in the `pipes` folder + +#### Directives in the `directives` folder etc. + +#### Page Folder Exclusion + +- Omitting a pages folder due to the current absence of an extensive component count, that would justify its introduction. + +For clarification on component categorization or any other building block, cross-reference with implementations in other app versions or seek guidance through communication. + +### NAMING CONVENTIONS + +- For dialogs, ensure the inclusion of the term dialog in the name. +- Maintain consistency with established naming conventions in other app versions. +- Propose suggestions for improved and clearer naming in discussions or comments. + +### STYLE GUIDE + +#### The project utilizes SCSS. Copying and pasting CSS from other sources would be accepted only if it is formatted correctly to comply with SCSS conventions. + +#### use relative measurements in the `scss` files: + +- `rem`, `%` +- `wh`, `vh`, `dvw` `dvh` +- avoid using `px` + +### MEDIA QUERIES + +The placement for media queries is the standard placement - below all the other styles. + +## INDENTATION & FORMATTING + +Maintain the project's indentation and formatting. Do not include formatting changes in your PRs, only include code that you have changed. It doesn't look like you have done more when you submit a PR with tons of indentation changes - we all see its just indentation and that makes it even more unpleasant to deal with. + +## Commit Message Guidelines + +To maintain a clear and organized version history, we follow a standardized commit message convention. This ensures that each commit provides valuable information about the changes made. Please adhere to the following guidelines when crafting your commit messages: + +### Feature: + +``` +feat(component): add new feature X +``` + +### Bug Fix: + +``` +fix(component): resolve issue with Y +``` + +### Documentation Update: + +``` +docs(readme): update installation instructions +``` + +### Code Refactor: + +``` +refactor(service): restructure data fetching logic +``` + +### Performance Improvements: + +``` +perf(api): optimize data retrieval for faster response +``` + +### Test: + +``` +test(component): add unit tests for feature Z +``` + +### Build: + +``` +build(pipeline): update dependencies and build scripts +``` + +### Chore (Release): + +``` +chore: prepare for version 1.0.0 release +``` + +### Revert + +``` +revert: revert changes from commit abc123 +``` + +### Mandatory Compliance with [Coding Rules](#coding-rules) and [Commit Message Guidelines](#commit-message-guidelines) for PR Merges + +Kindly ensure that all pull requests strictly adhere to our Coding Rules and Commit Message Guidelines. Non-compliant PRs must be adjusted prior to acceptance. + +## Reviewer Accountability + +Reviewers who approve PRs not in alignment with the [Coding Rules](#coding-rules) and [Commit Message Guidelines](#commit-message-guidelines) may face restrictions on their approval privileges. diff --git a/LICENSE b/LICENSE new file mode 100644 index 0000000..5858d0c --- /dev/null +++ b/LICENSE @@ -0,0 +1,21 @@ +MIT License + +Copyright (c) 2024 AnguHashBlog + +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is +furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all +copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE +SOFTWARE. diff --git a/README.md b/README.md index 684df4a..4ffda0a 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,15 @@ # Analog App +Use this version of +## ![anguhashblog logo](/anguhashblog-logo-readme.png) AnguHashBlog +which allows you to connect your Hashnode Blog to +# ![analog logo](/analog.png) Analog + +without UI libraries + +
+ + This project was generated with [Analog](https://analogjs.org), the fullstack meta-framework for Angular. ## Setup diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 0000000..034e848 --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,21 @@ +# Security Policy + +## Supported Versions + +Use this section to tell people about which versions of your project are +currently being supported with security updates. + +| Version | Supported | +| ------- | ------------------ | +| 5.1.x | :white_check_mark: | +| 5.0.x | :x: | +| 4.0.x | :white_check_mark: | +| < 4.0 | :x: | + +## Reporting a Vulnerability + +Use this section to tell people how to report a vulnerability. + +Tell them where to go, how often they can expect to get an update on a +reported vulnerability, what to expect if the vulnerability is accepted or +declined, etc. diff --git a/analog.png b/analog.png new file mode 100644 index 0000000000000000000000000000000000000000..0034610e344ced15dbdb910ee39d401855bc33ca GIT binary patch literal 2634 zcmbVO3s@B88eT*Yi1Ln-Amg9{+U(5U*qxEpfJGJsLBPa^REC+^WrW=sXBKuvxrkQ? zhy$qDkyONrj!~Lsh!j#@GBZdQ%16MIFat!7k9x`@oLO#JY4x0ap4qv*|NDO5`+fhn zn;W$x^m&&TT|^?$^I=*|v~YH}9ZrtI_vg2^5W>ls)vn-0BC)sau(KRokR}p2O6b@) zQ(QziMlc33PBMv<*kWJ>v`7@Nz{280GGzi1DLrjegT1w%f&fjb!R3kwB!Ug5l4xx@ zN5!Nsi6zpL36umE%m)H2m_T5lOgLaMq!@Y3q6Ph$&eO2HFIHxQHkq znBgb@6-yujL8O2Z73*XQIi(|B0;Gsk21_I`fK3$O(AJQ8bgLW70t)4V<|YA;+a&AphD7wFuiTr zuvjoh;Un1!Hj<2)_j_UirNK><8WgG~hY%TrsA3TnCYNC{ z>0CsLA;=&!f+1<$x<5iu%m$ME1}gLniJS1h1d{}&V>kmYBupD{Jq5EyJqV20hy^n# z3?~Q+(a8p)h={<#jJydq5>%K*4GKAnX_~}T3RFqrI0~th{z?c}$aRp4P$(f%iK~fMJ1dd--B}AgXRH-5%IgStzu97E0i6kO{q_{vYM^Ra# zQa&6_Bu5Jy4NrNJ)fN>gFzWo3N;FZXgp?9o1rem2f^eMlhvZ5GM@b!tAgIpP%>xaB zX=z?4-MXRu5ksvVx=Nvefu6u{!q)3*kgye*BEg}@^i%x!TgpT0%}JC%`X|L7ROcC; z$&7PUpkDCqFPjT~X7G$LjpCjNpT#*`m@yQ`t3e&d7yz7QQ)mLWk?ftnMheAk+*n?)k~Ps22UvD)0$o$=duESq#TD>~Mt1~+yIXE?fp7g( zZC}4(DI2s}(VLk!`o1`2ltZ;$&T9@edy3!Q_;X2B_R{&|sGA3i9X@(>PU8=y`S$4e zy{hRm!g7ET{Y=jiwtsZq&514cmrs8Q!s+xqcUN&-c)ekA01+;v^Hl3k27D9CN!P!cLtu_RxFEMN?wZZ{x*}7oW2FZgunl z-rQE6G;WODTE5iX{2ty}GPZTPBDA-x)JGFofT#-ms_XV%FQ1k@)jBS=o&QMe`Fg;j zHK&4JO1&PV=)UHcxUcb*BZnKE)=XlmqS{y`v~~BlS=-;i@~<(MkcPs@qSZ&rzBxbt zV*&l%^sfs>uRQi%Z)T_!(zc%1eCMIv z(I&92BFEEn*7Shf!sC*b)N57LA#44E3!i&>RS;G#e8%FQuHG+}yG6HtvZ>3f_WkHg zwiQpf%Jj62IehFZugrBTaxRRLDPQl9&g{I{VD$k?fTq^q_3d7jJK>=C8O33ZyJ6|= z(^~VCcirN>K7%LcZVmn7VlV!m*O=p5e73y;ZUMZvsFq~)yJqL%72Y90=4>o2Rkd#?59xL8Sz>#Y?s^vHcffpe#G zAMRe{Qm@NTd4uG$vz;#bv-#i0ymhZYPjC3}pJ&?C+Omevwvjofnw|Em@-d_3uAe;3 zHRG4bSCVdA`JS12sf(!e`qtD&O3?7UyWG@Wqn1@1@Y!Biu8ALiW^TgD@FUiQg(tL% z8^F|qDC^qdLVL{9ynA3;ewFC`bJ;DAMzPZxPy85{mp!Ms8RtZnac!|JA<-=db z79mo55JH5oeS}nwN@FmK7DvcIQ3$NU3E?1#jDvq%R)xn&AP(M}#wYUSu5hq~7o~t# zM=ckKqC!M02*217w6Y#ik5mg8W@2m#I`S4fb zToDC~W7(4c5s^s7FO?>buoB|TFJ-O}^ zVCam44_2w#0U|foItWCs(l(4ghZ2a^7V?)ad1dPfJ0#^ zEK?~_S<nm6aoYZeVgW$Z~euQY4$YS0&j^7 zLc*0cYP5+BFc(z896XwGDnO(FM3#U=WRqBI3T+{g%q9}wi1HCgB98pED1}WXvMH>e ziJ}DufhzD%g&`4Jj3}fa8ZC(w41x)ASr8sKnFF>f5{f8LVAMLwxD|Xpdx=b`0%an2 z373OMU9gu(Ahu8pQ;BG`0VE1U2gqV741iRs7$CtUh{#|H8A7J`?S3vITCXk(_5L>$ zfe;a@<0n)yg~_1PU?MoVu(egP~U1>p^%^~1w-G}s@VT&v-A6QfWG zZoHt_ph!&=4ql{AG7RA-mLkx~ zf2|Y#9({h%%l|q05Y)%}o1RAaWxIPb=e{WmcXgqSpMdP&Y;1p#Q0S4!M%(&iqyLXu z@&rEe-?nx&1;!nJ=brO+3B5e2hm+SfbTWDIgJo#jQJ~klh4p=*7>v%)60Wm=mlCsE zk{SSOB(*1-X3hd+D>bf`?m&8HZy}W}hlpZ2a)N=Wcw~ z3eB2?hoW@Ntj*D0_(ewg&Bjey=`Of~tC!X94QQOYH+cm=-JG+jV5^SN+Pu3LdRmp_w)x=Y$z4+!}*7^>pdR+M3F- zQ?|+N8oKXXvkA&^7hKo%IA0XlQ`aGIzjkDI<6Xgd{)1fv3Mqz*%WR2wYIsLJ~r{dv4(A9v5tddyx7NO z>vb%nD;AB~?v{;y^!QMu*4llnw4VB0s|(4Ed0*BPHf@v+UZ>x(*fSF1%yAH8Yayj5$~59*z9@kZ)es?PcASKBxSFFlCOh(1^=-3&1C z<(vFpj@4Zo`Oc#1#7b|eoRb=s# zvYb>)@x|u3G5xpW@4leqT=Q`=@F~blE@u}nzHlr7z((Y*sx_!KTxJN5bZJg^HuiP# zB6LK@b#|rf8R}UOP!V1-Fi@8~=IYq9sd8O?>&Q(#h1+Usg3Ik~U-aY$?DIap+3(8? zBq9C;Bk^1EixMMS^Z2#8mraLRE@$e#^tG2OvaCLg_B>cm69iatYn_h;AIO{?F~Vt2 zTWnzyoA_gANm28`sTNibd~bf%l6281?d2(?-_L@1*1)>{^58eQU^_PF)D6QUD(eS*8KxGBllt){f%gs^*XhF~r=1ROQV#Cg7@Ogek8N#qDl+|n zUI{;dnoFzwhxm4a&TS(c{runu&aWPgeQgT(tUGMupSxvyL%+y%_mOOS-&v=QZ98Pp zH??FXE+EbL7#Nmao>Y9p%%iB=7MrE%ZPlcOS(vmTEV=4Ncmd<(r?IIY%&<>vzp-In zeQo#LA>F0NH)Q5(TdkgVw6?`E!p~t#Sj<4JgLfU$aMPq9bymr}T*yEdl%&dhDxatJ zAHta@n&_TcJ*K+>?s~4VDE3z6%`4}E3P;);3gsRC_jj^ylMZc7w+<60XEq!}dO6=c zKis?eacKKM!+w@oXU3t}>S(tYx_gLuIwRv-VWA9WKwN2?U z>zq5V%%VlQm6NA4?ZbJFHCvKuLSjDX`k4N&dQrdIKtRs(k*pb)pnctmQkTBa9%TJuzW;EEx@$j8z^kZ9FTYr^&!HN9tU8yZwN}Zl# zpDuS6Z0p=}*|ohmU=z>{ycF!YeLEzY;g@@MU30mQ-EaoI?-Xy$t?+DrMXjoxk)$=X9t|qYycAf!mlc<^wL#KaY*u{Kqxnb3&~S(M z`%mxaxSykgy&y)PZgUi8lJ)9P=^4yD-n9sK_QpynRhuRrHPIY187O*Ho0kb{zvzMg!Yy z4}Vl(b_h2%OM88`PUuzRj;F$lF4;bA9v-g6p#m#yC-X6;ua+5tvC`)1V+|s^ifn@Y z^Oo})>MUZOU6*?w)v4UnxIc4xe!yV$dx=k!@_@~&idG%=d%7~c;f8-8$D<~En*&^n%C!yO%`lek>>Gtt^Rt{0qOrZxCH zOE~XB3^C~w%;dk&pfXy{ef$0Ewg?PPTOJVS`HArIXld^lG}LsVaCq(h%;m^5`f;aR zE8VXIE;;fU(%Ur;k_LJnR}aQ5F-r?Mdvv#RaPw zx72;{)Uv0y(5CCu`O({-8V#!+5ZqlIzcYN#8k=gn5<7Y^_T|pkm}lt&9s9NNKT-cH Ow8U*W_qa=7{J#M~cty(q literal 0 HcmV?d00001 diff --git a/angular-material.png b/angular-material.png new file mode 100644 index 0000000000000000000000000000000000000000..237cce2450aa95ae12f513ab1a3401e6f769e694 GIT binary patch literal 3020 zcmbVO3tUWj8=fLvbh9jxbQ-s)xtzJwoY`umNrkD9l(L^Q=bWk0%$zYZHC+&0R4bGa zLeWOnQbMu0lv`~j3R^@iq1=jM3#IQ&x3%Ao-Ti&@`<*%ebI$XBp7(v;_q;Pn-kxqo z29pd(B$APbJAW~8o~SwWMiJjvp2Z`?Nnh^nuOyL1kJTJnq&<7hNTgAq*vC)hCs@cu za48i=aUn(xm&yq=iR8cwm%~U1rUHamkXYtOZZEz_2E?c%c^O+k7sy?(V6l6o0$UR4 z>4QXuAP`FCIROsgT!KJ~sbC;nDv>F<;f~~fUM{iL+@_I%euyf>k?gDy1pEZvfD5j` z0Eh}w5IP+M?1>f2j=_N-TYy1lFllr<8iP$?(7AMw%Vq#v+vtODI*YVMH2(hI|pN^ofvTw8fYb4^<$TYZwvc zR82N=u8RVLRk*?j$0b9R@*WBqV6dqmV7*K%Lvgio)@K_qKCHqV$wbvy6grbaXZU~& zF3XO~1a0UHE}cFA72v2?6!ArGC?dRi2sHU=-{R3T&;t0X#{xP#~rV zq%%2ep*;o;v3V)P#ES+?K4;ZLg%XS+A&Q9XAcz8jbPk0Dvp@>OhG7a562f+{9TS2X zOiefUHwf2VtRzYoG5CHg!B!8hBx0byC%7=8>2*gkqA4tDfcA3RayShGc=j+;~bW^rjvu;xG!XGRbX6rA{@EZ%1 z1}9$oCN@cre~h&@(E3=aOdZzn;O^b(>Z*O|QJEJlMa8MM70=T?u5oBl ze`cJ6>Bh zS#-R#NGBIt+_LC?%g9;L%C-uL$XRi=B+&QhwmUEUoOZ@XxN+j*vBdc)d3(ub>-GYD zl`A_^mo*wkys@cUvR2G{vMH}rZ6(O62YzU zPtQO67+dne=tvQX%6k4RVb`OnC1Z4Nwz|?zn|F4%Mcno(=`w;>9{j}pk#eSk6nMd8 z!M$4BLxys|YJ?T7V1G@>9@?*Lr_Wu{InmG(Od;!I)YWm-!Z@0>491Dfyu@~fq4*(z-S94&Df zwO~nol+&ufQ1|Ucldea{RKjP+Bvw@Bm$qzu;P#=s?gV3GhSe*w{$)^ES`;vGS5;=< zZ&rqKa9ZchBS~kppSv72xPHr83X5Zw-^zy*F5Tb-7xo&g>708mYyFa=R%agtn35Rt zGj8r~x}0rqhEKMueM;J6IRYyPTe@l=SU{D%n4(N?GA?b+$|?CZ7VBw_Y2Tq*v^;uz z&m6aplMA1%s_$ec+R#599G8CGz&tCzRBzKRD6s;)u{Q1Hn^z4jjCw%&$Cn?~#Fg6Eg(R~i1G z^?2UzJ?4kfx0bf%h%)lV1~|!*U&Z`kc)M@QxrExt`_*0^LEp2t@CqF!R~p_pyELV0 zX3M#bky@P0M~`6t=xFk+TeYr@Uo& zJNX%T)P^70hhDKLb9WxsxurhB-$8Qa+uPD|Plttn+{?Z;y-1j|x?nHQ%A{YgU6)A zvJ$pYZ;zE6*IKYPWPIQ$yvwAR7vZK?!feV-4!zagD7^6cPUw@AH(Cqdm+#&r?73v< ze{7@4fwY5HjqRG^mXF?cs(a45W?kc#PQ7>oR{ieCmO&OOwr$&ZwCiM_jAC zCWp2LI2^5Bvw1pC?$i_`5_)mc8=@;8KEAH*cz4_+DZ9((_{pr-4^o9a4^Px+*VOti zAHC^zRQ~q*&iS$Ut6u*;ufFSL_rA9&N&8PB?L&#hYoqAYJmqY?dfxjG$HEziN63X6 o4yvGsMG3OvchM(OuUsTW#Xh@d<&vAC`M>Sq>d8MocV*0f0V)W#Y5)KL literal 0 HcmV?d00001 diff --git a/index.html b/index.html index b2a5faa..dc7072e 100644 --- a/index.html +++ b/index.html @@ -3,7 +3,7 @@ - My App + Analog - Angular Material | AnguHashBlog