-
-
Notifications
You must be signed in to change notification settings - Fork 94
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
Vote on New Features #41
Comments
Logo Upload |
Footer Menu |
Header & Footer Widget Areas |
Breadcrumbs |
Hello Bryan, After spending hundreds of hours fixing theme - plugin conflicts, I realized that BlankSlate is the salvation. And, because I so desperately wanted to use it, I had to learn some PHP basics in order to add breadcrumbs, sidebars, menus... So, my assumption is that other users are like me and don't need any features. (Still fateful to the vision) Thank you for asking |
Remove jQuery |
Add dir template-parts |
jQuery has definitely become less popular in recent years.
I almost did this a couple times. The problem with both changes and with most big/structural changes is that it would break A LOT of websites. I get nervous making any updates at all, knowing that people who are using BlankSlate without a child theme or taking other precautions will have their entire site wiped out by merely upgrading. It's a difficult balance to be responsible for: stability vs progress. Unfortunately, without a lot of feedback (#57), there are too many unknowns, so I have to err on the side of caution. |
Hi bhadaway, Is it possible to include SASS compiler function in the future? Thank you, Steve |
While I think you could make a good case for it, why can't BlankSlate be Sass-ready if it's jQuery-ready? But, this was added at a time when jQuery was much more popular, and only because it's natively available in WordPress already: https://core.trac.wordpress.org/browser/trunk/src/wp-includes/script-loader.php If the dependencies for Sass were already available here, I'd consider it. The problem is that it would add too much bloat to the theme to support it, requiring everyone who's not using Sass to have to either remove it or ignore it, which is antithetical to this project's objective. Also, I'm all for an open community, that helps direct the future of the project, but it's hard to get people to vote on features. I may try again. |
Hi bhadaway, Understood, thank you for your reply. Steve |
Full Page iFrames (no border) |
That's not really a feature, so much as it is a customization request. If that's what you're trying to achieve, feel free to start a new issue and I'll help. |
Find proposed features listed below and give them a πβ(for yes) or a πβ(for no).
I understand, greatly, the importance of keeping BlankSlate simple and staying the hell out of designers' and developers' way, but surely there are some main features that you find yourself constantly having to add in yourself through a child theme when starting a new project on top of BlankSlate, which could cut down on development time if they were officially made staples of the default theme?
The text was updated successfully, but these errors were encountered: