Hello. I want to create a new theme. I saw the chapter create a theme and his starter theme. It's a basic good starter theme, but a little too much. For example, there are no folders for scss that are very useful for easily starting a theme.

Do you know other starter theme ? with scss folder for exemple or an other way to make a theme (not a child theme).

PS: I'm not a fan of Boostrap and other framework css

PS2: I use VSCode to connect with server and Live Sass Compiler to compile my scss. Like this no need composer.json or package.json. 

Comments

Hi

I'm not aware of any SCSS starter themes.  I myself use SCSS a lot using the native Dart Sass compiler and also don't use composer.

I started with the Bedrock theme and am slowly building an SCSS based fork; each client theme I build gets a bit closer, but it is still quite messy and not suitable to share.

Sorry that I can't be of more help.

Modules you may find helpful:

  • Devel (exposes the core setting of enabling "theme debug" (you can also set this with bee (the command line tool) if you're using it). It also has a setting to rebuild theme registry on each page, which can help keep things updated.
  • Style Guide - provides a page of common Backdrop elements to help you target all the things you need to theme.
Enthusiast's picture

If your goal is to learn how to create your own themes, I recommend using the Stark theme from the core and adding whatever you need to accomplish the task as you build your site. It would be a good learning curve. I can't comment on SCSS, as I don't use it.

Here's my rough ToDo for creating my own theme fron Stark.

• Copy the Stark theme, rename the folder and .info file.

• Create a template.php file, css, fonts, icons, img, js, and templates folders.

• Download and include the necessary fonts (https://gwfh.mranftl.com/fonts).

• Include an icon font (optional).

• Edit template.php to add additional classes to the 'body' tag.

• You might also copy header.tpl.php, block.tpl.php, and similar files to the 'templates' folder and edit them.

• Next, edit the CSS and JS files to suit the needs of the project.
 

This way, it's easier to add everything you need to the theme than to search for and remove everything you don't need.

My goal is to test BACKDROP in depth to see if it is possible for a client with small projects to suggest this CMS. DRUPAL is a big Machine with a lot of work and WORDPRESS also needs a lot of work to get it serious and performant. 

At this moment, I have to redo the SCSS folder and I also try a migration with the wordpress api, but the only valid module seems to be Migrate with a custom module. So, honestly I don't know what to think...

Yes. Work well but custom-posts are not considered and the html like <h2> are removed but in that case i'm not sure if it's not my fault. I left this option.

Enthusiast's picture

There are no modules that can magically transfer an entire website, down to the smallest detail. I recommend looking into migration using the Feeds module. Of course, the choice depends on the site structure, some elements may require manual copying and take up time, but if you have many pages in an identical format, it is simpler to export them to a CSV file and import them into a prepared Content type with the necessary fields to Backdrop. This ensures a clean and controlled data transfer. The site's visual styling is a separate topic.

About SCSS — why is this topic relevant to Backdrop CMS? If you use SCSS, you are working with your favorite development tools. In the end, standard CSS must be uploaded to the any website.

A Backdoor CMS is not complicated. Here, almost any task is performed using mouse clicks in the admin area. The creation of the theme is very simple, simple universal templates that do not require deep knowledge of the programmer.

Feeds give me multiples php error due to last version of php. I thought that the authors had abandoned the module ?

In CSV, okay I'll test it.

I can recreate a SCSS folder, but Backdrop like Drupal has specifics like block, region, etc... It's a particular logic (and I like it) and it's necessary to reflect a little. If this work was already done it would help the themers a lot. Like underscore of Wordpress.

 

Enthusiast's picture

I use PHP 7.4 for all my sites so that I don't have any problems. I'm currently transferring data from a Backdrop to another Backdrop site using Feeds and CSV. In fact, it doesn't matter where this data came from, the main thing is to have the right CSV to import into Feeds.

Thank you for these clarifications.  In a few days I'll tell you more...

After some hesitation as to how much BACKDROP CMS work is needed to create a custom theme for a website, I am pretty sure that this CMS is a good alternative between DRUPAL(welcome in Symfony) and WORDPRESS. 

I didn't attack the style part, but I found devel with the pleasure to  surcharge template. Very pleasant for a themer ! I also made a custom module to import via the api rest Wordpress. With 1 day, it's done and work very well. The interest of the api compared to CSV, is that the datas are inline, not in a file. Like this it's possible with a URL to switch between post, page or custom-post with possible options like 'exemple.fr/wp-json/wp/v2/pages?_embed=true&per_page=100'. It's very simple and i can manage each fields.

Thank you for your positive response. I guess English is not your first language but it seems like you found the Devel setting for theme debug where it suggests templates and found that useful. You haven't looked at the style guide module - though that is less important if for your own sites rather than a contributed theme. Please correct me if I have misunderstood.

Your approach to importing from WordPress sounds interesting and something, if you are willing, that the wider community could benefit from if you were willing to share somehow, even if you don't want to maintain a module.

It's not English.  It's Globish :-) (Global + English). 
Like for Drupal Devel is not an option - I looked style guide but for me, it's not interesting. It's useful but it's just a one page with all HTML. It's easy to make this page without module. 

The real novelty is the layouts. I'm going to create a new one because a layout without <main></main> is strange to me. For example the layout BOXTON, put the "top" layout outside of "the content". And I don't like too much the naming of class. I just try to stay true to HTML standards, without creating a new one, with the risk of losing myself.

My wp-api-rest-import module for the community. Why not. But I need to put in a bit of performance. It's a test right now.