MaxiBlocks Theme Beta Feedback V1.0.8

[ckp267]

From our support channel:

I've been working on Avada so far, but MaxiBlocks is more flexible in my opinion. There are still a few options missing and it has some minor bugs that I hope you will overcome.

1. 👉 To create my main page I had to edit the provided Home Page template and delete practically all the blocks. This site is really pretty, but I couldn't use it. Perhaps for future projects it will be convenient for me. ❓Is that why you created a full pre-built homepage for fast build home page? But why use such a prepared, content-packed Home Page template for each new page?

2. 👉 I don't remember what the default font is used, but it certainly doesn't support Polish fonts (like ą, ę, ć).

3. 👉 When you set your own new style, fonts and size were not taken into account. My Lato font set in Style Cards did not replace the default font from the provided beta template. I had to manually replace all the texts. In every newly added text block, the default font from the Maxi Beta Template was always inserted, instead of the one from the Style. The same was true of the font size.

4. That is all on this time 🙂

=== Breakdown for clarity ===

1. The user is comparing two website building tools: Avada and MaxiBlocks. They prefer MaxiBlocks for its flexibility but note that it still has some missing features and minor bugs.

2. Main points about the Home Page template:

   • The user had to heavily edit the provided template, deleting most blocks.
   • They found the template attractive but not suitable for their needs.
   • They're asking if that's why you created a pre-built homepage for quick building.
   • They're questioning the use of a content-heavy template for each new page.

3. Font issue:

   • The default font doesn't support Polish characters (ą, ę, ć).

4. Style and font problems:

   • When setting a new style, fonts and sizes weren't applied correctly.
   • The Lato font set in Style Cards didn't replace the default font from the beta template.
   • The user had to manually replace all text.
   • New text blocks always used the default font from the Maxi Beta Template instead of the chosen Style.
   • Font size settings were also not applied correctly.

[elzadj]

1. Homepage: That's more of a design issue, but makes sense. Maybe we should make the homepage as "Header" + "content area" + Footer? Or at least create a custom template "Blank Homepage" (Clean homepage, whatever, with basically just header, content and footer?).
2. Font: we have an issue about it.
3. SC styles: Lato and custom font size worked just fine for me, both frontend and backend. And any other font too. Could it be that the user changed the "Light tone globals" values instead of the Dark? If no, then it would be nice to get a video or at least the template name that was not working with SC.