samiranghosh04/acckit-ui

AccKit UI: Cutting-edge UI component library prioritizing accessibility and performance. As of now its in the pre-revenue, pre-code stage. Highly customizable, future-proof, and open source. Join us in creating a more inclusive web. Let's build together! ✨

Welcome to My GitHub Profile!

Hey there! I'm Samiran Ghosh, a BCA graduate currently pursuing MCA. I'm passionate about coding and technology, and I love exploring various aspects of web development and software engineering. This GitHub profile is a collection of my projects and contributions, reflecting my fundamental knowledge in various programming languages and technologies.

Skills

Here are some of the languages, libraries, frameworks and tools I'm proficient in:

Projects

Here are some of the projects you'll find in this repository:

1. BBC Article Scraper: This is a simple web scraper built using Node.js, Express, Cheerio, and Axios. It fetches the latest articles from the BBC's website and prints an array of objects called "articles" to the console. Each object contains the headline and the link to the article. (https://github.com/samiranghosh04/bbc-article-web-scraper)

2. cryptopulse: Free price tracker of over 120+ cryptocurrencies built with React, Axios and a free public/third party API. (https://github.com/samiranghosh04/cryptopulse)

Feel free to explore and provide feedback or suggestions. I'm always open to learning and improving my skills!

Current Focus

As I pursue my MCA, I'm currently focusing on enhancing my knowledge in distributed systems, data structures, and algorithms. Additionally, I'm interested in exploring new frontend frameworks and cloud technologies.

Contact

If you want to reach out to me for collaboration or have any questions, feel free to connect with me on LinkedIn or drop me an email.

Let's learn and grow together in the vast world of programming! 😄

acckit-ui's Issues

I think we need to work on a robust meta design framework

Discussed in #2

^{Originally posted by samiranghosh04 August 1, 2023}
As we embark on this journey to build an awesome OSS UI component library, we realized that obtaining enough data from our initial market research was challenging. But, fear not! We're determined to make this design system a success, so we've kicked off the ideation phase.

We believe in an inclusive and collaborative approach. So, if you have any insights, data, or suggestions to contribute, we'd love to hear from you! Let's work together to shape this design system into something truly remarkable.

Remember, this is just the beginning, and we welcome any feedback and tweaks as we progress. Once we have enough data for analysis, we'll make sure to incorporate the insights to deliver a powerful and user-centric UI component library.

Join us in this exciting journey! Share your ideas, participate in discussions, and let's create something extraordinary together. 🌟

---

name: Feature request
about: Suggest an idea for this project
title: Building a Meta Design Framework for Seamless Integration of Multiple UI Design Trends
labels: enhancement, UI/UX Design
assignees:

---

Is your feature request related to a problem? Please describe.
We are building an open-source UI component library, and we aim to create a flexible and scalable system that can support multiple design systems, each following entirely different UI design trends. However, currently, we lack a cohesive framework that allows for the seamless integration of these diverse design approaches. We need a solution that will enable our UI library to adapt and stay relevant in the ever-evolving world of UI design.

Describe the solution you'd like
We propose building a Meta Design Framework that serves as the foundation for our UI library. This framework should be capable of accommodating various design principles, such as Atomic Design, while also supporting different UI design trends like flat design, neumorphism, skeuomorphism, glassmorphism, 3D, neubrutalism, and more. By having a robust Meta Design Framework, we can ensure that our UI library is versatile, customizable, and capable of meeting the diverse needs and preferences of developers and designers.

Describe alternatives you've considered
One alternative we've considered is developing separate, isolated design systems for each UI design trend. However, this approach could lead to a fragmented and hard-to-maintain library. Instead, we believe that a single Meta Design Framework that intelligently integrates multiple design trends would be more efficient and user-friendly.

Additional context
Having a Meta Design Framework would provide consistency and coherence to our UI library, making it easier for users to adopt and implement various design systems without unnecessary conflicts. We envision this framework as a collaborative effort, welcoming contributions from the community to ensure it caters to a wide range of design preferences and requirements.

Any insights, ideas, or feedback from the community would be highly valuable in shaping this ambitious feature for our UI component library. Let's work together to create a UI library that sets new standards and inspires innovation!

---

Consideration of a Cautious Approach to Long-Term Development

Consideration of a Cautious Approach to Long-Term Development

Background:

1. BunJS 1.0: BunJS claims to be a faster alternative to Node.js and Deno. This announcement suggests a potential shift in the runtime environment for JavaScript applications. Before fully adopting BunJS, it's important to evaluate its performance claims, stability, and community support. We may want to consider running some benchmarks and test cases to gauge its suitability for our projects.

2. Shift Away from TypeScript: Projects like Svelte and Turbo 8 have opted to move away from TypeScript in favor of Vanilla JavaScript. While TypeScript has gained popularity for its static typing benefits, this shift could signify a trend towards simpler and more lightweight development. We should assess whether this trend aligns with our project goals and whether we should follow suit or continue with TypeScript based on our specific project requirements.

3. Type Annotations Proposal: The TC39 proposal for type annotations in ECMAScript is an exciting development, especially for those interested in statically typed JavaScript. However, it's currently in the early stages (stage 1) and not yet part of the ECMAScript standard. We should closely monitor its progress and consider how it might affect our codebase if it advances further. This includes evaluating whether adopting type annotations would improve code quality, maintainability, and developer productivity.

Proposal:

1. Monitoring: Continuously monitor the development and adoption of BunJS and other emerging technologies. Subscribe to their official channels, participate in relevant communities, and follow their progress on platforms like GitHub. This will help us make informed decisions about adopting these technologies when they mature.

2. Assess Impact: The shift away from TypeScript in projects like Svelte and Turbo 8 indicates a shift in the JavaScript ecosystem's preferences. We should assess how this change impacts our projects. It may involve revisiting our codebase to determine if transitioning to Vanilla JavaScript aligns with our project's goals and improves development velocity.

3. Type Annotations: Stay informed about the TC39 proposal for type annotations. Engage in discussions about its potential benefits and drawbacks within our specific project context. Consider conducting feasibility studies or experiments to understand how introducing type annotations might affect our codebase, development workflow, and overall code quality.

4. Experimentation: Allocate dedicated time and resources for experimentation and prototyping. This provides us with a safe space to test new technologies and practices before incorporating them into our production code. We can create isolated environments to assess the viability and practicality of BunJS, Vanilla JavaScript vs TypeScript, or type annotations.

5. Community Input: Engage with the broader JavaScript development community, both online and offline. Attend conferences, webinars, or local meetups to gain insights into how other developers are responding to these changes. Collaborate with peers to share experiences, best practices, and potential challenges.

Conclusion:

In conclusion, while it's essential to stay innovative and adaptive in the fast-evolving JavaScript ecosystem, it's equally crucial to approach these potential shake-ups with a balanced and cautious mindset. By following these proposed steps and fostering open discussions within our team and with the broader community, we can make informed decisions that align with our project's long-term success and goals.

This issue should serve as a foundation for ongoing discussions and decision-making as we navigate the ever-changing landscape of JavaScript development. It's essential to remain flexible and responsive to emerging trends while maintaining a focus on the stability and sustainability of our projects.