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

Premium Themes are missing - Tweeper and instapaper #16984

Open
barak-haviv opened this issue Aug 13, 2019 · 1 comment
Open

Premium Themes are missing - Tweeper and instapaper #16984

barak-haviv opened this issue Aug 13, 2019 · 1 comment
Labels
discussion enhancement This is not a bug, nor a new feature

Comments

@barak-haviv
Copy link

Hi there
It looks like the premium theme Tweeper and Instapaper are remove from the source code.
I would like to know if there is a "good" reason for that?
I build my project base on it so I am a little worry. Should I?
Does these theme use methods that will not be supported in future versions?

Any info/help about this subject will be very appreciated

@oliviertassinari
Copy link
Member

oliviertassinari commented Aug 13, 2019

@barak-haviv Yes, I have removed Tweeper and Instapaper. I think that having two is enough for Material-UI to handle. I think that we should use them to explore the best practices for overring Material-UI from an end-to-end perspective. But this part of the library is still fuzzy. For instance, there is this double notion of template and theme. A template a piece of code that focuses on the UX, while the theme focuses on the UI. We host a few templates in the naked domain and a few themes in the themes subdomain. It's inconsistent, the proof that we are still exploring and looking for the right approach. And yet, it's important. I like how WordPress engages the community to build original themes. However, Wordpress is x100 our scale. So I think that it's way too early to benchmark against them.

A few next steps I have in mind:

  • Create a dedicated page for each template. It will make them easier to find with Google. It will be easier for us to track the popularity of each template and know on which to double down. Startbootstrap approach is interesting: https://startbootstrap.com/templates/sb-admin/.
  • Create a dedicated page to host the themes the community build under: /getting-started/themes/. We have recently renamed /customization/theme/ to /customization/theming/. So I hope it's free of conflicting sense.
    The free themes under themes.material-ui.com and material-ui.com will have different goals. The ones in themes.material-ui.com are a free version of richer paid content, it's 60% about template and 40% about theme. The OSS versions on material-ui.com will be much more about theming, with no upsell option, provided as is, by people who enjoy doing it.
  • Move the two existing themes to their own GitHub repository: [material-ui][docs] Make the free premium templates easier to use #14604 (5+ people having this pain). The same approach is used by Startbootstrap, it works great for them. If we start to have too many (I wish) then we can do something similar to WordPress, with a backend and co. Maybe somebody will resurrect the two deleted themes and handle the maintenance, we can link them.

cc @mbrookes. Do you have a long term vision on how we should structure the information?

@oliviertassinari oliviertassinari added the priority: important This change can make a difference label Aug 13, 2019
@oliviertassinari oliviertassinari removed the priority: important This change can make a difference label Dec 1, 2019
@oliviertassinari oliviertassinari added the enhancement This is not a bug, nor a new feature label Jan 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion enhancement This is not a bug, nor a new feature
Projects
None yet
Development

No branches or pull requests

2 participants