Jump to content
thirty bees forum

cienislaw

Members
  • Posts

    96
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by cienislaw

  1. 23 minutes ago, jollyfrog said:

    Would you suggest that Niara should be improved instead? Or do you feel that Niara is sufficient?

    IMO Niara is just a 'skin' for Community Theme. there are no major differences between those two in terms of functionality. so as Community Theme was outdated, Niara still is too, but looks a bit fresher.

  2. from my perspective it's simple:

    1. point out where current themes suck and address those issues

    • mobile experience
    • shopping process ux
    • cart...
    • code duplication to achieve the same thing in different places

    2. give it modern look with minimal set of features

    3. reduce quantity of modules used to achieve that

    anything else should be in merchant hands or someone hired by him.

    • Like 1
  3. yup, it's time to move on. current state is unacceptable in a long run. theme architecture is archaic, with a lot of teeny-tiny modules for very specific outcome. as many of you said before - you really don't need a bunch of modules, a successful shop can be build with just a few of them. for sure, building a new theme in community style will not be easy, but IMO it's the only way. TB user base is too small to invest a lot to build new modern theme and frankly, I really don't like commercial themes as those are bloated with too much stuff.

    if someone starts such a project, I will try to help.

  4. 3 hours ago, nickz said:

    I don't think that the newsletter module get a lot of attention.

    Neither do I think that TB should compete with prestashop but rather develop a model where Prestashop falls short. Smaller buniess with 300 to 1500 articles are ignored by the market. Woocommerce and shopify take on those.

    Less features but easier to handle and ultra stable in questions of updates is the future IMHO.

    read again what @rubben1985 wrote.

    for those who don't have account on prestashop marketplace (is it possible?;-), message is below.

    Quote
    Dear customers,
     
    We would like to inform you of a major change coming soon to the PrestaShop Addons marketplace, which will result in the modification of our Terms and conditions of use (https://preview.prestashop.com/e2t/sc2/MmZ-8yjWgpzW65vG9s9l7r96W75Zv-w4-7SH7W1w4JCy6lGwVkdBzP8N04  ) .
     
    As of June 1, 2021* for all Addons developed by PrestaShop, and as of July 1, 2021* for all other Addons, the Zen Option will be replaced by our new subscription-based 'Business Care' offer.
     
     
    Services included in the 'Business Care' subscription
     
    Security updates
     
    All Addon updates, both minor and major, will be available as soon as they are released.
     
    Compatibility updates
     
    With each new version of PrestaShop software, your Addon's compatibility is ensured with an update.
     
    Future developments and features
     
    No need to buy your Addon again to benefit from its new features. Access all its developments as soon as they are released.
     
    Unlimited support
     
    Don't be left without answers to your questions! Our sales team will provide you with a response within 1 business day in order to help you develop your business as quickly as possible.
     
    You will be able to subscribe from June 1st* for all the Addons developed by PrestaShop, then from July 1st* for the entire PrestaShop Addons marketplace catalog.
     
    💡 Good to know!
     
    The 'Business Care' subscription will be linked to your Addon purchase. This means that as soon as the new service goes live, you will no longer be able to buy an Addon without the accompanying 'Business Care‘ subscription.
     
    This subscription lasts for 12 months as of the date you purchase the Addon, renewable on a rolling basis. You can terminate this subscription at any time without notice, and it will end once the current subscription expires.
     
    Do not hesitate to consult our FAQ for more information on this new offer.
     
     
    We are confident that this 'Business Care' subscription will allow you to reinforce your online store with more powerful and secure Addons, and to benefit from a better support to make your business grow!
     
    See you soon,
     
    The PrestaShop Addons team
     
    *estimated date. Subject to technical difficulties that may slightly delay the launch.

     

    • Like 1
  5. 9 hours ago, Briljander said:

    Why aren't you interested in staying with Thirtybees and help out? .

    he is helping, but on his terms. code is public, so if TB core team finds something interesting in ME, they can use it.

  6. 1 hour ago, jollyfrog said:

    I guess there is a necessary balance we must find between configurability and simplicity (for the merchant). For example, Panda (created by the same developers as Transformer) is a highly configurable theme, However, most of the shops I have seen using it are poorly constructed.

    ...

    This theme doesn't need to compete with Panda or Transformer. This theme needs to compete with corporate sites in both search and sales. For the thirty bees merchants, these are the competition.

    Well said. IMO Commercial themes pack too much stuff and tempt users to use it all as on examples, which are there not to show you how to achieve good and simple look (not basic!), but present all theme features. This is a snake eating own tail situation, when with too much stuff and freedom you bloat the site with fancy stuff, which doesn't help sales at all and frustrates users.

  7. We need a modern look, ux design and shopping process/experience.

    Community Theme Default is several years old. It has flaws, it isn't mobile friendly at all. Don't get me wrong guys, but another face lifting will get just a bit better theme, not a new perspective this project needs. I'm not saying that existing code can't be reused in some way, but for sure shouldn't be used as a base for a new template.

    Also there is a need to change a way of expanding theme features. I know that no one is forcing you to use a lot of modules, but currently there is a module for every little thing, with a lot of duplicated data and so on. This, beside removal of useless modules from a theme, can be addressed in favor of using HTML Block, so module bloat will be minimalized.

    I don't think that there is a need for mobile and desktop version - more space doesn't mean that you should bloat it with something and a good RWD designed theme will look good on both platforms.

    Feature voting - I'm against it. Most of us merchants on this forum are not graphic or ux designers, and you can see it clearly by visiting our shops. Of course users can suggest something, but the final look and feel of theme should be decided by professionals.

    There is also need of translations proofreading. Even the best theme shopping experience will be ruined with bad translation, and if the rest of them is as bad as Polish one... I understand how works community translation and I know that it's hard to get quality with multiple people translating something they don't even use. Proofreading will take time, but it will be worth it.

    That's my five cents which should explain my point of view on this matter.

  8. I hope that new owners have a new default theme for 30b on the roadmap. By new I mean done from scratch, because any other way will be only face lifting without heavy lifting. By a new default theme I don't have in mind anything close to Panda or other commercial themes, not at all. But we need a new theme, based on 2021 design rules, with heavy focus on mobile version and so on.

  9. 19 hours ago, Traumflug said:

     

    @zen wrote some "image laundry" code about a year ago, which does all such cleaning as a background task. But this didn't make it into the distribution, yet.

    there is a lot of code waiting months to be merged. I hoped that after take over github will be flooded with commits, but last one was 4 months ago.

    • Like 1
  10. edit coresponding php files and add a hidden-print class to elements you dont want to have on printed page.
    
    <div class="hidden-print">content for non print</div>
    
    <div class="visible-print">content for print only</div>
  11. let me copy & paste it for you:

    https://nodejs.org/en/

    Download and install node.js + npm, LTS version will do.

    With npm up and running you can finally compile SASS to CSS. To do that, make sure you first set up build environment. Steps to do that you can find below. Be aware, that you have to do this on your local machine and use Niara theme from GitHub repo, not release from your store.

    https://github.com/thirtybees/niara

    Building

    This theme works as-is on thirty bees, all built files are committed to the repository.

    CSS files shouldn't get edited directly, but their Sass counterpart in sass/ instead. After doing so, CSS gets compiled from that. For contributions, please create commits including both, source file changes together with their build results.

    Setting up the build environment

    npm install
    

    Building CSS from Sass

    npm run compile-css
    

    Linting JavaScript

    npm run lint-js
    
×
×
  • Create New...