├── .all-contributorsrc ├── README-old.md └── README.md /.all-contributorsrc: -------------------------------------------------------------------------------- 1 | { 2 | "projectName": "Angular-Headless-Hashnode", 3 | "projectOwner": "monacodelisa", 4 | "files": [ 5 | "README.md" 6 | ], 7 | "commitType": "docs", 8 | "commitConvention": "angular", 9 | "contributorsPerLine": 7, 10 | "contributors": [ 11 | { 12 | "login": "monacodelisa", 13 | "name": "Esther White", 14 | "avatar_url": "https://avatars.githubusercontent.com/u/64324417?v=4", 15 | "profile": "https://monacodelisa.com/", 16 | "contributions": [ 17 | "code", 18 | "maintenance", 19 | "review", 20 | "tutorial", 21 | "content", 22 | "ideas", 23 | "mentoring", 24 | "design", 25 | "infra" 26 | ] 27 | }, 28 | { 29 | "login": "cleancodecraft", 30 | "name": "cleancodecraft", 31 | "avatar_url": "https://avatars.githubusercontent.com/u/132580309?v=4", 32 | "profile": "https://github.com/cleancodecraft", 33 | "contributions": [ 34 | "infra", 35 | "test", 36 | "code", 37 | "blog", 38 | "example", 39 | "ideas", 40 | "mentoring" 41 | ] 42 | }, 43 | { 44 | "login": "czBalazs98", 45 | "name": "czBalazs98", 46 | "avatar_url": "https://avatars.githubusercontent.com/u/53296597?v=4", 47 | "profile": "https://github.com/czBalazs98", 48 | "contributions": [ 49 | "code", 50 | "design", 51 | "ideas" 52 | ] 53 | }, 54 | { 55 | "login": "jhonacs2", 56 | "name": "Jhonatan Soto", 57 | "avatar_url": "https://avatars.githubusercontent.com/u/75391330?v=4", 58 | "profile": "https://github.com/jhonacs2", 59 | "contributions": [ 60 | "code", 61 | "design", 62 | "security", 63 | "ideas" 64 | ] 65 | }, 66 | { 67 | "login": "samplelittlered", 68 | "name": "Little Red Coding Hood", 69 | "avatar_url": "https://avatars.githubusercontent.com/u/127144297?v=4", 70 | "profile": "https://github.com/samplelittlered", 71 | "contributions": [ 72 | "code", 73 | "blog", 74 | "content", 75 | "design", 76 | "security", 77 | "ideas" 78 | ] 79 | }, 80 | { 81 | "login": "yshashi", 82 | "name": "Sashikumar Yadav", 83 | "avatar_url": "https://avatars.githubusercontent.com/u/21971232?v=4", 84 | "profile": "https://portfolio-latest-two.vercel.app/", 85 | "contributions": [ 86 | "code", 87 | "design", 88 | "ideas" 89 | ] 90 | } 91 | ] 92 | } 93 | -------------------------------------------------------------------------------- /README-old.md: -------------------------------------------------------------------------------- 1 | ![](/angular-hashnode/src/assets/animation/merge-animation.gif) 2 | 3 | # Angular Headless Hashnode 4 | ## [![Discord](https://github.com/monacodelisa/icons-and-graphics/blob/main/icomoon/PNG/discord.png?raw=true)](https://discord.gg/3bS3xpCj) Open Source Project 5 | 6 | ## Overview 7 | 8 | The **Angular Headless Hashnode Project** aims to seamlessly connect your Angular application to the Hashnode GraphQL database, providing a template for integrating Angular with a headless Hashnode setup. 9 | 10 | In other words - this project is very much like the starter kit that Hashnode provides, except that this project uses Angular for the frontend and deployment is set to be done through Netlify. 11 | 12 | ## Project Goals 13 | 14 | - Develop a flexible template for Angular integration with headless Hashnode. 15 | - Connect the Angular app to Hashnode's GraphQL database to retrieve posts and blog data. 16 | - Responsive layout improvements for different devices 17 | - Support Angular v17 and up 18 | 19 | ## Existing Setup & Features 20 | 21 | - [Appolo Angular](https://the-guild.dev/graphql/apollo-angular/docs) - GraphQL Client for Angular 22 | - [Font Awesome Icons](https://fontawesome.com/) 23 | - [Google Material Symbols and Icons](https://fonts.google.com/icons) 24 | - [Google Fonts](https://fonts.google.com/) 25 | 26 | ## LIVE VERSIONS 27 | 28 | | [![angular headless hashnode dark](/angular-headless-hashnode-dark.jpg)](https://angular-hashnode.monacodelisa.com/) | [![angular headless hashnode light](/angular-headless-hashnode-light.jpg)](https://angular-hashnode.monacodelisa.com/) | 29 | | - | - | 30 | 31 | ### You can see the live versions on the [DEMO SITE](https://angular.hdlshashnode.com/) 32 | 33 | ## Angular App Versions 34 | 35 | #### `angular-v17` - has no UI libraries [LIVE](https://angular-v17.hdlshashnode.com/) 36 | 37 | #### `angular-v17-AnguMAT` - has Angular Material [LIVE](https://angular-v17-angumat.hdlshashnode.com/) 38 | 39 | #### `angular-v17-PrimeNG` - has PrimeNG [LIVE](https://angular-v17-primeng.hdlshashnode.com/) 40 | 41 | 42 | ## Contributing 43 | 44 | ### Most of the open issues feature engaging YouTube videos, providing step-by-step guidance on implementing requirements. Dive in and contribute without hesitation – your skills are valued, and you can make a meaningful impact! Join us in building something great together.🌟 45 | 46 | #### the default branch is `develop`! 47 | 48 | ### Fork the repository 49 | 50 | 1. [Fork](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo) the `monacodelisa/angular-headles-hashnopde` repo. 51 | 52 | ### Working on Issues 53 | 54 | 1. In your local or forked repository, make your changes in a new git branch: 55 | 56 | ```shell 57 | git checkout -b my-fix-branch develop 58 | ``` 59 | 60 | 2. Create your patch, **including appropriate test cases**. 61 | 62 | 3. This is a monorepo that includes 6 versions of the app, make sure that you are working on the correct app version. 63 | 64 | 4. Follow our [Coding Rules](./CONTRIBUTING.md#coding-rules). 65 | 66 | 6. Commit your changes using a descriptive commit message as specified in [Commit Message Guidelines](./CONTRIBUTING.md/#commit-message-guidelines). 67 | 68 | ```shell 69 | git commit --all 70 | ``` 71 | Note: the optional commit `--all` command line option will automatically "add" and "rm" edited files. 72 | 73 | 6. Push your branch to GitHub: 74 | 75 | ```shell 76 | git push origin my-fix-branch 77 | ``` 78 | 79 | 7. In GitHub, send a pull request to `angular-headless-hashnode:develop`. 80 | 81 | ## Using the app with your Hashnode Blog 82 | 83 | This app is still in its early stages, and it currently has limited features. At this point, I strongly encourage you to contribute to its development before actively using the app. 84 | 85 | ### Fork the repository 86 | 87 | 1. [Fork](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo) the `monacodelisa/angular-headles-hashnopde` repo. 88 | 89 | 2. Go to your chosen app version, and inside the `graphql.operations.ts` file, replace the URL of the blog to point to your blog. 90 | 91 | 3. All three app versions can be deployed to Netlify or Vercel, so you just need to select an app version and deploy from an existing GitHub repo. (Your forked repo) 92 | 93 | Be advised that a lot of features are yet to be implemented. 94 | 95 | ### Run locally 96 | 97 | 1. Clone this repository. 98 | 99 | ```bash 100 | git clone https://github.com/your-username/angular-headless-hashnode.git 101 | cd angular-headless-hashnode 102 | ``` 103 | 2. Select one of the available [app versions](#angular-app-versions) 104 | ``` 105 | cd 106 | ``` 107 | 108 | 3. Install dependencies. 109 | 110 | ``` 111 | npm install 112 | ``` 113 | 114 | 4. Run the app 115 | 116 | ``` 117 | npm start 118 | ``` 119 | 120 | or 121 | 122 | ``` 123 | ng serve 124 | ``` 125 | 126 | ## Contributors ✨ 127 | 128 | 129 | 130 | 131 | 132 | 133 | 134 | 135 | 136 | 137 | 138 | 139 | 140 | 141 | 142 |
Esther White
Esther White
💻 🚧 👀 ✅ 🖋 🤔 🧑‍🏫 🎨 🚇		cleancodecraft
cleancodecraft
🚇 ⚠️ 💻 📝 💡 🤔 🧑‍🏫		czBalazs98
czBalazs98
💻 🎨 🤔		Jhonatan Soto
Jhonatan Soto
💻 🎨 🛡️ 🤔		Little Red Coding Hood
Little Red Coding Hood
💻 📝 🖋 🎨 🛡️ 🤔		Sashikumar Yadav
Sashikumar Yadav
💻 🎨 🤔
143 | 144 | 145 | 146 | 147 | 148 | 149 | 150 | This project follows the [all-contributors](https://allcontributors.org) specification. 151 | Contributions of any kind are welcome! 152 | 153 | ## Celebrate Your Achievements! 154 | 155 | If you've added exciting features or functionalities that the project currently lacks, we'd love to see what you've accomplished. Share your contributions, suggestions, or improvements to help enhance the overall app experience. Your input plays a crucial role in making the application even better, and we're eager to see the innovative strides you've taken! 156 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | # The project was given a name and was moved 4 | ## to a GitHub Organization ⬇️ 5 | 6 | # [AnguHashBlog](https://github.com/orgs/AnguHashBlog) 7 | 8 | ## Project Migration 9 | 10 | ### From a personal repository to a GitHub Organization 11 | 12 | The decision to migrate from a personal repository to a GitHub organization stems from practical considerations and the necessity for more effective project management. 13 | 14 | While GitHub itself presented no issues, challenges arose in deploying options and maintaining three distinct projects within a single repository. To address these complexities and foster improved project management, I've transitioned to a GitHub organization which was my initial intention but I needed a bit more free time to implement it - and also I wanted to verify that it was the right thing to do. 15 | 16 | This setup provides dedicated repositories for each project, streamlining code maintenance, project oversight, and access control. 17 | 18 | The transition also addresses some compliance issues. Despite the project's previous location in a personal repository, all essential open-source standards were applicable, with a particular emphasis on the simple understanding that non-adherence to the `CONTRIBUTING.md` guidelines would just result in the PR being rejected. 19 | 20 | From the project's outset, my perspective has been that contributions are aimed at the project's overall enhancement, dissociated from any specific association as the repository owner. 21 | 22 | When collaborators are requested to adhere to certain standards, it's not a personal directive but rather a commitment to established open-source standards. 23 | However, it appears that this was not universally understood by others temporarily involved in the project. 24 | 25 | ### The move to a GitHub organization emphasizes that the project's vitality isn't contingent on individual contributors but relies on collective adherence to established guidelines. 26 | 27 | Despite differing opinions on whether the project's size requires a GitHub organization, this move is aimed at providing room for growth and ensuring the project's sustained development. 28 | 29 | In summary, this migration signifies a strategic step toward enhanced project management, streamlined collaboration, and continued alignment with open-source principles. With the move to a GitHub organization, members will benefit from clearly defined roles, fostering a more structured and effective collaborative environment. I appreciate your ongoing support and commitment to project guidelines as we navigate this transition. 30 | 31 | ### Esther White 32 | Project Owner, Lead Developer and Maintainer 33 | 34 | --- 35 | 36 | Come and explore the new project's home - [AnguHashBlog](https://github.com/orgs/AnguHashBlog), existing collaborators will receive an invite to join, new collaborators are welcome. 37 | --------------------------------------------------------------------------------