QUIQQER week in review - 2019 / 14
QUIQQER week in review - 2019 / 14
Repository
Introduction
Hi all and be welcome to the QUIQQER Review 2019 / 14.
We are back again with a weekly report what happened in the QUIQQER space.
Today once a little earlier because there are a lot of meetings to be made tomorrow.
This weeks Topics
- Version 1.3 - Comfy Campeiro
- Testing phase of Order / Invoice / Plan / ERP
- E-Commerce
- Template inheritance in QUIQQER Tutorial
Version 1.3 - Comfy Campeiro
This week we started to implement and fix all new features and bugs of version 1.3. At the moment QUIQQER is in version 1.2.11, but in the last 4 months a lot of bugs and features have been implemented and it will be time to finalize version 1.3.
Comfy Campeiro is all about stability, performance and handling. We have outsourced some of the features as modules, like the new dashboard. So it's more of a stability update and not exactly full of new features. The big innovations are currently happening in the ERP area, but that doesn't mean that 1.3 has nothing great to offer.
Designers can look forward to the new version. QUIQQER Comfy Campeiro is equipped with a template inheritance feature which allows designers and developers to use other templates as a basis for their templates. Templates don't have to be started from zero anymore. You just want to overwrite a part of a template? This is then no longer a problem, define a parent template, overwrite parts of it and now you have created a completely new template.
Especially when it comes to e-commerce templates, this makes work a lot easier.
If you would like to find out personally about the status of development, you can do so at our milestone page. https://dev.quiqqer.com/quiqqer/quiqqer/milestones.
There you can see how far the development has progressed and what is still to come.
Testing phase of Order / Invoice / Plan / ERP
Anyone who has followed the last few weeks knows that we are working at full speed on our ERP and e-commerce system. This week the test phase for the last extensions started. Plans and memberships will be tested, payment methods will be carried out and the ordering process will be closely reviewed.
One of our services is of course the first test candidate. Early on we started testing our modules on ourselves until we released modules in a final version.
Eat your own Dog Food
Since we want to offer good software and above all, software that helps others. It is only logical that we always use our own things ourselves. Not only we find bugs so quickly by ourselves, many of the things only stand out in productive use.
Many things often seem logical in the development, as how a button fits exactly into that one place. It is not uncommon for this to be out of place in productive use. Especially the ERP system will be used by us. Our current invoice and estimate system will be completely replaced with QUIQQER.
Here we no longer use QUIQQER as SaaS but also as a real application in our in-house operations. Even if the beginnings are much more bumpy and complicated, in the long run this approach has proven to be successful. And how can we be convinced of our product if we don't even use it ourselves?
Template inheritance in QUIQQER Tutorial
As mentioned above, this week, the template inheritance went online and it is currently available in the master and dev branch. We have also written a small tutorial for this: How do I use template inheritance in QUIQQER?
Series Backlinks
- QUIQQER week in review - 2019 / 13
- QUIQQER week in review - 2019 / 12
- QUIQQER week in review - 2019 / 11
- QUIQQER week in review - 2019 / 10
Thanks alot for reading and see you next week!
Hen, for PCSG Developers
Hello, @pcsg-dev!
Thank you for another informative weekly report. It is good to see all the progress being made, and you managed to compose an interesting blog post that contains useful information about the recent developments.
On the content side, I think it's fair to say that you did a good job. The post is detailed, and includes valuable insights about the upcoming version. I particularly enjoyed reading about your personal knowledge and experience of working on this project; this is the kind of editorial content we like to see in blog posts. Keep up the good work.
That said, the post did have issues of style and proofreading, and I'd be happy to cite a few examples in a follow-up comment, if you wish. Nevertheless, this was a solid overall effort, and I appreciate the information you have provided us with.
I look forward to your next contribution.
Your contribution has been evaluated according to Utopian policies and guidelines, as well as a predefined set of questions pertaining to the category.
To view those questions and the relevant answers related to your post, click here.
Need help? Chat with us on Discord.
[utopian-moderator]
Yes please. We ask for improvement 😊👍
Hello!
First, my apologies for the slow reply.
I will cite a few examples for you:
This sentence should read: "We are back again with a weekly report of what happened in the QUIQQER space."
Not sure if I understood correctly, but let me rephrase that: "Today's report comes a bit earlier because there are a lot of meetings to be made tomorrow."
This would be a better sentence: "Not only do we find bugs so quickly by ourselves, but also many of the things only stand out in productive use."
I hope you will find this comment useful.
Thank you for your review, @lordneroo! Keep up the good work!
Hi @pcsg-dev!
Your post was upvoted by @steem-ua, new Steem dApp, using UserAuthority for algorithmic post curation!
Your post is eligible for our upvote, thanks to our collaboration with @utopian-io!
Feel free to join our @steem-ua Discord server
Hey, @pcsg-dev!
Thanks for contributing on Utopian.
We’re already looking forward to your next contribution!
Get higher incentives and support Utopian.io!
Simply set @utopian.pay as a 5% (or higher) payout beneficiary on your contribution post (via SteemPlus or Steeditor).
Want to chat? Join us on Discord https://discord.gg/h52nFrV.
Vote for Utopian Witness!