It has been argued quite persuasively to me, that the term 'recipes' implies a list of instructions on how to do something. In Drupal land there is a recipe initiative which centers around a collection of "best practices" and or tested instructions on how to acheive specific goals.
Is our use of "recipes" confusing? Is there a better term?
Personally, I think that this concept is still new enough that we could change the terminology with little cost (and potentially an improved understanding of what we intend).
In Drupal 7 these were "features," but the term features has a very specific meaning to former Drupal 7 users and we think it would be confusing to use it for this purpose in Backdrop land.
Many of my D7 modules rely on adding controls to existing settings pages, and looking to porting to Backdrop CMS I wonder what the strategy is for doing this sort of thing without the page array.
I was once told by a Drupal colleague that he wasn't sure how seriously to take Backdrop until he saw businesses and developers that were dependent upon it's success for their livelihood.
We already have a number of developers in our community that make significant portions of their income working with Backdrop. But, in my view we need to see more Backdrop based businesses promoting Backdrop and helping to build it's infrastructure.
Triplo has been working on a SASS idea based upon Backdrop CMS - https://simplo.site/
I'd like feedback on Simplo.site as a product AND as importantly, where it fits in the Backdrop community. I'd also like to hear more about how others are making a living by working with Backdrop and how we better support the Backdrop business community.
My team still uses SASS on all our big Drupal client projects. I used to love the Zen theme for Drupal 7, because it came with config files and instructions for SASS tools, first Compass and then Gulp.
When I use SASS I still use Gulp. I've done some Drupal Camp presentations on how to set up and customize Gulp in a Drupal 7 theme, based largely on this excellent blog post: https://chenhuijing.com/blog/drupal-101-theming-with-gulp/
I would not recommend using Gulp and SASS for anyone that is only theming a single site. But, if you plan to theme a bunch of sites, you might find it useful. It does add complexity to a site and I've spoken to some prolific and talented front end developers that prefer to work in straight CSS.
I think it might be helpful if we had better starter themes for Backdrop that include an optional SASS starter kit.
I'm interested to learn something about the mechanics behind: How user settings are working? Why a registered user can't be deleted? Where is a possibility to solve this?
How could I carry a group membership to a user (enter a group), set automatically the group membership for content, while carrying this membership (content autotag) and how could I release it (leaving a group)?
How could I display all group content or group members, just while carrying the membership info?
Please realize, that this is different than to register to a group for membership.
My idea:
To enter a group, should go trough a gateway or link on the groups main page (the group itself). The membership to a group is already required to be allowed to enter this group. The state is carried like a flag (entered or not). A view should be able to act as a group menu.
If you're new to Backdrop, come in for a discussion on how Backdrop can be the best option for creating your new website. As we all know, WordPress has been the goto for new sites and it has a large user base. But if you plan to do anything other than a basic site of a few pages and a blog, WordPress can require custom code for most things that are even a little bit off the beaten path.
Backdrop allows users to create custom views easily and to create pages that draw from databases, and it doesn't require custom code. You may not need this now, but it's good to have this power in the future.
Backdrop is built on expanded Drupal 7 code. Drupal 7 still powers over 50% of Drupal sites, but it is coming up on End of Life, not immediately, but the modules may not receive updating even though Drupal 7 does for a while yet.
It's time for both new users and Drupal 7 users to step up to a powerful CMS built on proven code.
It has been argued quite persuasively to me, that the term 'recipes' implies a list of instructions on how to do something. In Drupal land there is a recipe initiative which centers around a collection of "best practices" and or tested instructions on how to acheive specific goals.
https://foxvalleydrupal.org/article/announcing-drupal-recipes
Is our use of "recipes" confusing? Is there a better term?
Personally, I think that this concept is still new enough that we could change the terminology with little cost (and potentially an improved understanding of what we intend).
In Drupal 7 these were "features," but the term features has a very specific meaning to former Drupal 7 users and we think it would be confusing to use it for this purpose in Backdrop land.
Are there potential core features that have been blocked by the lack of references in core in the past?
What kinds of features have been added to Drupal 8/9/10 that are related to references (if any)?
Not sure where to put this...
Many of my D7 modules rely on adding controls to existing settings pages, and looking to porting to Backdrop CMS I wonder what the strategy is for doing this sort of thing without the page array.
I need to port a D7 site that makes heavy use of
I have no experience with Backdrop yet, and I'm trying to estimate the required effort...
This is really cool! We are so happy to have the folks at Stanford as part of the Backdrop CMS community.
@laryn, thanks for your message. Hope you can attend. But agreed in any case that we should take notes.
I was once told by a Drupal colleague that he wasn't sure how seriously to take Backdrop until he saw businesses and developers that were dependent upon it's success for their livelihood.
We already have a number of developers in our community that make significant portions of their income working with Backdrop. But, in my view we need to see more Backdrop based businesses promoting Backdrop and helping to build it's infrastructure.
Triplo has been working on a SASS idea based upon Backdrop CMS - https://simplo.site/
I'd like feedback on Simplo.site as a product AND as importantly, where it fits in the Backdrop community. I'd also like to hear more about how others are making a living by working with Backdrop and how we better support the Backdrop business community.
@olafski I may not be able to attend sessions on the 12th due to a prior commitment. Take good notes? :)
My team still uses SASS on all our big Drupal client projects. I used to love the Zen theme for Drupal 7, because it came with config files and instructions for SASS tools, first Compass and then Gulp.
When I use SASS I still use Gulp. I've done some Drupal Camp presentations on how to set up and customize Gulp in a Drupal 7 theme, based largely on this excellent blog post:
https://chenhuijing.com/blog/drupal-101-theming-with-gulp/
Here is a recorded version of my Gulp session:
https://www.midcamp.org/2019/topic-proposal/introduction-gulp
I would not recommend using Gulp and SASS for anyone that is only theming a single site. But, if you plan to theme a bunch of sites, you might find it useful. It does add complexity to a site and I've spoken to some prolific and talented front end developers that prefer to work in straight CSS.
I think it might be helpful if we had better starter themes for Backdrop that include an optional SASS starter kit.
I'm interested to learn something about the mechanics behind: How user settings are working? Why a registered user can't be deleted? Where is a possibility to solve this?
How could I carry a group membership to a user (enter a group), set automatically the group membership for content, while carrying this membership (content autotag) and how could I release it (leaving a group)?
How could I display all group content or group members, just while carrying the membership info?
Please realize, that this is different than to register to a group for membership.
My idea:
To enter a group, should go trough a gateway or link on the groups main page (the group itself). The membership to a group is already required to be allowed to enter this group. The state is carried like a flag (entered or not). A view should be able to act as a group menu.
Unfortunately I don't know, how to realize it.
If you're new to Backdrop, come in for a discussion on how Backdrop can be the best option for creating your new website. As we all know, WordPress has been the goto for new sites and it has a large user base. But if you plan to do anything other than a basic site of a few pages and a blog, WordPress can require custom code for most things that are even a little bit off the beaten path.
Backdrop allows users to create custom views easily and to create pages that draw from databases, and it doesn't require custom code. You may not need this now, but it's good to have this power in the future.
Backdrop is built on expanded Drupal 7 code. Drupal 7 still powers over 50% of Drupal sites, but it is coming up on End of Life, not immediately, but the modules may not receive updating even though Drupal 7 does for a while yet.
It's time for both new users and Drupal 7 users to step up to a powerful CMS built on proven code.
Looking forward to a great discussion with all!
An issue created on github to work on job board https://github.com/backdrop-ops/backdropcms.org/issues/842
Further notes will be in the issue.
Hosted Apache Solr search by Jeff Geerling (geerlingguy) who is part of the Drupal community.
https://hostedapachesolr.com/
> I would love to see a job board - jobs.backdrop.org - where employers can post jobs/gigs related to Backdrop CMS.
I love this idea. Let's talk about how to move this forward.