Scaffold-Stark / ss2-docs

Docs for scaffold stark
https://docs.scaffoldstark.com/
MIT License
3 stars 14 forks source link

Documentation regarding UI libraries #4

Closed 0xquantum3labs closed 3 months ago

0xquantum3labs commented 3 months ago

Issue Overview

Suggestions are being made to better support other UI libraries.

Proposed Solutions or Ideas

Current implementation only makes use of DaisyUI and low level vanilla implementations. This should provide flexibility to install any UI libraries people may want to use. Documentations or FAQ entries can be written to address the question

Iwueseiter commented 3 months ago

I am applying to this issue via OnlyDust platform.

My background and how it can be leveraged

Hi @0xquantum3labs can I work on this please?

onlydustapp[bot] commented 3 months ago

Hey @Iwueseiter! Thanks for showing interest. We've created an application for you to contribute to Speedrun & Scaffold Stark. Go check it out on OnlyDust!

od-hunter commented 3 months ago

I am applying to this issue via OnlyDust platform.

My background and how it can be leveraged

Hello can I be assigned this please? I am a full-stack developer and I'm also good at documentations.

fishseabowl commented 3 months ago

I am applying to this issue via OnlyDust platform.

My background and how it can be leveraged

Hello, may I be assigned to this, please? I am a seasoned developer with strong documentation skills. I have contributed to several open source projects, including Madara and Dojo.

How I plan on tackling this issue

I will review the Quantum3-Labs/scaffold-stark-2 project and provide instructions on how to install popular UI libraries.

ShantelPeters commented 3 months ago

Hi , please can I be assigned to this project

ShantelPeters commented 3 months ago

I am applying to this issue OnlyDust Background and Leverage: As a frontend developer with experience in building modular and adaptable UI components, I'm excited to help enhance the project's UI library support. My background in software development, particularly with UI libraries like React, Angular, and Vue, has equipped me with the skills to create flexible and reusable UI components.

Approach to the Problem:

  1. Research Popular UI Libraries: I'll research popular UI libraries (e.g., Tailwind CSS, Material-UI, Bootstrap) to understand their requirements and integration processes.
  2. Decouple UI Components: I'll decouple the current UI components from DaisyUI and vanilla implementations, making them more modular and reusable.
  3. Create Adapter Pattern: I'll implement an adapter pattern to enable seamless integration with various UI libraries.
  4. Develop Plugin Architecture: I'll design a plugin architecture to allow users to easily install and use their preferred UI libraries.
  5. Document New Features: I'll write documentation and FAQ entries to guide users on installing and using different UI libraries.

Solution: My proposed solution involves researching popular UI libraries, decoupling UI components, creating an adapter pattern, developing a plugin architecture, and documenting new features.

Technical Details:

Whevalmeze commented 3 months ago

I am applying to this issue via OnlyDust platform.

My background and how it can be leveraged

Based on a user perspective of using several libraries and frameworks and my experience in writing technical articles. I understand how competitors and big software companies write their docs for UI libraries support which involves installing a few packages, creating a config file in most cases.

How I plan on tackling this issue

Firstly, I would understand the software by installing it and reading the documentation. Then, I would implement major libraries like MaterialUI, Shadcn, ChakraUI, and TailwindCSS. During this process, I would note the procedures I took into a number of simple steps I would compare each step to filter the unnecessary down to the most important to ensure it takes only a few steps to get it done. I would ensure to reach out to the team, in case of any technicalities. After this, I would write the documentation with some FAQs about the installation process.

ScottyDavies commented 3 months ago

I am applying to this issue via OnlyDust platform. As a frontend developer, I would approach this problem of providing better support for other UI libraries in the following way:

  1. Assess the Current Implementation:

    • Understand how the application currently integrates with DaisyUI and the vanilla implementations.
    • Identify areas where the UI library integration is tightly coupled or hardcoded.
  2. Design a Flexible UI Library Integration:

    • Create an abstraction layer or UI library adapter to encapsulate the integration logic for different UI libraries.
    • Provide a consistent API for components, styles, and functionalities, allowing the application to interact with the UI library in a standardized way.
  3. Implement the Adapter Pattern:

    • Define adapter interfaces that specify the contract for UI library integration.
    • Implement concrete adapters for each supported UI library (e.g., DaisyUI, Material UI, Ant Design).
    • Ensure the adapters handle differences in component APIs, styling, and functionality across libraries.
  4. Update the Application Code:

    • Refactor the existing codebase to use the UI library adapter interfaces instead of directly interacting with the underlying UI library.
    • Provide a mechanism (e.g., configuration, dependency injection) to allow users to specify the desired UI library at runtime.
  5. Enhance the Documentation:

    • Update the project's documentation to explain the UI library integration approach and how users can select the desired UI library.
    • Provide examples and guides for integrating different UI libraries with the application.
    • Add a FAQ section to address common questions and concerns related to the UI library integration.
  6. Implement a Smooth Migration Path:

    • Ensure the existing DaisyUI-based components and functionality can be easily migrated to the new UI library adapter-based implementation.
    • Provide a gradual migration path, allowing users to transition to the new UI library integration at their own pace.
  7. Test the Integration:

    • Create comprehensive tests to ensure the UI library adapter-based implementation works as expected, focusing on component rendering, functionality, and styling.
    • Validate the integration with various UI libraries to ensure consistency and correctness.

As an experienced frontend developer, I can leverage the following skills and knowledge to address this issue:

By addressing this issue, I can help make the project more flexible, extensible, and user-friendly, benefiting a wider range of developers and users.

DavidOredu commented 3 months ago

I am applying to this issue via OnlyDust platform.

My background and how it can be leveraged

Experience in game development with Unity using C#. Comfortable with the Python programming language.

How I plan on tackling this issue

Read through existing documentation on DaisyUI. Look out for possible outlets to enable add-on of other UI libraries and denote them.

oceanlvr commented 3 months ago

I am applying to this issue via OnlyDust platform.

My background and how it can be leveraged

im good at javascript & typescript. im graduated from East China Normal University. Computer Science & engineering.

How I plan on tackling this issue

solve this issue till this week