A Guide to Hashnode with Angular Development

Disclaimer

Permission was granted to use "Hashnode" in the project name. However, this project is an independent integration with Hashnode and is neither officially affiliated with nor endorsed by Hashnode.

The Project

'Hashnode with Angular' is a unique project designed to seamlessly integrate Angular into headless Hashnode blogs. Not confined to a single blog, it provides a comprehensive template that can be universally applied across any Hashnode blog. The versatility of Hashnode with Angular lies in its use of variables, ensuring adaptability and widespread applicability.

The Technology Behind Hashnode with Angular

Hashnode with Angular operates by connecting frontends to headless Hashnode blogs through Apollo Angular, a GraphQL client enabling the execution of GraphQL queries within Angular. The integration involves connecting to the Hashnode public API and adhering to query specifications outlined in gql.hashnode.com. Centralized in graphql.operations.ts, all GraphQL queries are managed, and a dedicated blog service with various methods, retrieves relevant blog data.

Multiple Versions for Diverse Preferences

Hashnode with Angular offers a couple of distinct versions to cater to user preferences:

• Angular with PrimeNG: actively being worked on, deployed live with almost all foundational features already implemented
• Analog with Angular Material: actively being worked on, deployed live with almost all foundational features already implemented

This gives users the flexibility to choose their preferred UI library. Regardless of the version, Hashnode with Angular ensures a fully functional and aesthetically pleasing blog, allowing Angular developers to customize as desired.

Guided Evolution from Hashnode

As a guiding principle, every new feature implementation in Hashnode with Angular stems from Hashnode. While improvements and enhancements are made, the goal is to never regress from Hashnode's existing offerings. Hashnode serves as a foundational guide, and any alterations aim to build upon and enhance the overall functionality.

Standardization Across App Versions

Despite differences in UI libraries and component structures, Hashnode with Angular maintains standardized practices. The core structure of all apps remains uniform, with UI library versions utilizing provided components and features. The pure Angular version is crafted from scratch, but consistency in file structure, naming conventions, and style guides is emphasized across all app variants.

Collaborative Development and Roadmap Alignment

In our collaborative development approach, it's imperative to cross-reference each version of Hashnode with Angular. Before implementing a new feature or addressing a bug, a thorough check is conducted to ascertain if the same has already been tackled in the other version. This ensures that solutions are consistently applied across all variants.

Importantly, any proposed suggestions for improvements undergo discussion before implementation to maintain a unified roadmap across all app versions. This collaborative and synchronized effort guarantees a cohesive development process, minimizing discrepancies and maximizing the collective strength of Hashnode with Angular.

Open Communication and Code Guidelines

Beyond that, this collaborative space encourages open discussions here or in comments. Before implementing changes, it's highly advisable to vocalize questions or propose ideas to prevent potential pull request rejections. Emphasizing a proactive approach, we value your input and encourage you to engage in conversations, ensuring a smooth and collaborative development environment. Additionally, I kindly remind all contributors to adhere to the specified coding rules and commit message guidelines meticulously outlined in the Contributing. Consistent compliance with these standards is vital for maintaining code quality and facilitating seamless collaboration within the Hashnode with Angular community.