Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What do you expect in Stisla 3 (Bootstrap 5)? #203

Closed
nauvalazhar opened this issue May 21, 2021 · 16 comments
Closed

What do you expect in Stisla 3 (Bootstrap 5)? #203

nauvalazhar opened this issue May 21, 2021 · 16 comments
Labels

Comments

@nauvalazhar
Copy link
Member

Thank you for always supporting this little project.

As the title said.

From me:

  • Improve the documentation
  • Not everyone uses NPM/Yarn (there's should be a pre-compiled version for conservative users)
  • A new dashboard design
  • No jQuery (so it's not difficult to adapt to frameworks like React)
  • UI kit (not only admin template)
  • Figma file would be cool
@nauvalazhar
Copy link
Member Author

designing the dashboard is not that easy 😂

gambar

@cyberhck
Copy link
Contributor

For me, modular please,
Also TypeScript,

And if I want only navbar for example, it should only pull in navbar from bootstrap, and overwrite your values, BUT it shouldn't include button in this case, and if I import button, it shouldn't include navbar :)

@ma3ain
Copy link

ma3ain commented Jun 15, 2021

Thank you for keeping updating Stisla.

The thing I want to see the most is support RTL support in the new version.

Best.

@raikasdev
Copy link

I personally like top navigation, have you thought how that would look?

@cyberhck
Copy link
Contributor

I was just trying out a theme my friend bought (Landkit) which also is bootstrap5.

I absolutely hated the codebase, I found the design to be pretty nice, but the usage was shit.

I'm trying to use it in nextjs framework, now I'm having to import ALL css that I'll need into 1 styles.css and use that,

What I'd have liked is that me being able to import navbar only if I'm using navbar in a page,

If I'm in profile sign in page, there's no need for navbar in my case, why would I want to import that? That doesn't work.

I think while bootstrap is moving towards correct direction, it's not doing it fast enough, it doesn't do scss modules, which means nothing works.

Now I'm having to basically go without much optimization.

@owf18916
Copy link

integration with laravel 8.x would be cool !

@raikasdev
Copy link

integration with laravel 8.x would be cool !

Personally I don't think making Stisla integrated with a framework, so as much people could use it.

@cyberhck
Copy link
Contributor

cyberhck commented Jul 28, 2021

no, there's no integration needed.

all we gotta do is release css modules for individual components, when you use css modules, it should work for any framework.

But that's not possible with bs5, so simply updating to use latest bootstrap should be enough, I already am using bootstrap 5 and it's working fine, only thing I hate is the no css modules in bs5.

@ProjectLinde37
Copy link

integration with laravel 8.x would be cool !

Keep Stisla clean - integration should be done by the developer who will use it.
And a php-framework has nothing to do with an good layout.

@ProjectLinde37
Copy link

ProjectLinde37 commented Nov 7, 2021

Thank you for always supporting this little project.

As the title said.

From me:

* Improve the documentation

* Not everyone uses NPM/Yarn (there's should be a pre-compiled version for conservative users)

* A new dashboard design

* No jQuery (so it's not difficult to adapt to frameworks like React)

* UI kit (not only admin template)

* Figma file would be cool

Pre-compiled version a must.
Keep is clean from jquery - Native javascript if needed - keep the same idea as BS5

@Aloha276
Copy link

Any news about Stisla 3 ?

Anyway thank you for the hard work you put in it, keep it up!

@github-actions
Copy link

This issue has been automatically marked as stale because it has been open for 14 days without activity. It will be closed if no further activity occurs within the next 14 days. If this is still an issue, just leave a comment or remove the "stale" label.

@github-actions github-actions bot added stale and removed stale labels Jun 27, 2022
@github-actions
Copy link

This issue has been automatically marked as stale because it has been open for 14 days without activity. It will be closed if no further activity occurs within the next 14 days. If this is still an issue, just leave a comment or remove the "stale" label.

@github-actions github-actions bot added stale and removed stale labels Jul 12, 2022
@github-actions
Copy link

This issue has been automatically marked as stale because it has been open for 14 days without activity. It will be closed if no further activity occurs within the next 14 days. If this is still an issue, just leave a comment or remove the "stale" label.

@eerison
Copy link

eerison commented Nov 21, 2022

Maybe this issue should be reopen?

@rizkytegar
Copy link

Maybe this issue should be reopen?

yes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

9 participants