https://github.com/ozantekin/primereact-ui-blocks

PrimeReact/ui blocks built with Tailwind CSS, Next.js, and PrimeReact. (👨‍🍳 Cooking)
https://github.com/ozantekin/primereact-ui-blocks

contentlayer nextjs primeicons primereact reactjs tailwindcss typescript vercel

Last synced: 3 months ago
JSON representation

PrimeReact/ui blocks built with Tailwind CSS, Next.js, and PrimeReact. (👨‍🍳 Cooking)

• Host: GitHub
• URL: https://github.com/ozantekin/primereact-ui-blocks
• Owner: ozantekin
• Created: 2024-09-10T21:30:11.000Z (4 months ago)
• Default Branch: main
• Last Pushed: 2024-09-19T06:09:50.000Z (3 months ago)
• Last Synced: 2024-09-27T10:23:01.298Z (3 months ago)
• Topics: contentlayer, nextjs, primeicons, primereact, reactjs, tailwindcss, typescript, vercel
• Language: TypeScript
• Homepage: https://primereact-ui-blocks.vercel.app
• Size: 1.46 MB
• Stars: 6
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# PrimeReact/ ui blocks

PrimeReact UI Blocks offers customizable, user-friendly components for fast interface creation. Built with Tailwind CSS, PrimeReact, and PrimeIcons, these blocks simplify your development process.

## Screenshots

![Screenshot 1](./readme/home.png)

![Screenshot 2](./readme/preview.png)

![Screenshot 3](./readme/code.png)

## To-Do List

### September

- [x] Complete basic features for the initial release

- [ ] Create 10 blocks

- [ ] Add dynamic metadata

- [ ] Enhance user experience for preview/code functionality\*\*

- [ ] Redesign layout to include a sidebar

## Contributing

We welcome contributions from the community! Here's how you can help:

1. **Fork the repository**: Click the "Fork" button at the top right of this page to get your own copy of the project.

2. **Create a new branch**: Create a new branch from `main` to work on (`git checkout -b feature/your-feature-name`).

3. **Make your changes**: Improve the code, add new features, fix bugs, or enhance the documentation.

4. **Submit a pull request (PR)**: Once your changes are ready, submit a pull request with a clear description of what you’ve done and why.

### Contribution Guidelines

#### Commit Messages

- Use clear and concise commit messages that describe **what** and **why** you made changes (e.g., `Add user authentication feature`, `Fix bug in preview layout`).

- Keep your commit messages in English and follow the general format:  

  `type(scope): description`

  - **type**: The type of change (e.g., `fix`, `feat`, `chore`, `docs`, etc.).

  - **scope**: The area of the project affected (optional).

  - **description**: A brief description of the changes.

#### Pull Request (PR) Guidelines

- Ensure your PR has a descriptive title and provides details about the changes introduced.

- Reference the issue number in your PR if it solves an existing issue (e.g., `Closes #123`).

- Keep your PR focused: group related changes together. Avoid including unrelated modifications.

- Run all tests locally before submitting your PR to ensure no breaking changes.

- Add relevant documentation and update any affected README sections.

- Engage in the PR review process by addressing feedback and suggestions promptly.

We look forward to your contributions!