This is the demo for OCIM Theme Customizer, which was supposed to be OCIM UX 2.1 all though we were able to achieve a lot of work here and revamp the look and feel of the OCIM interface.
The learnings for upcoming epics (Things that I should have done better):
When relying on newcomers for tasks, try not to give critical tasks to the newcomers.
Continuous follow-ups if the tasks are lagging or you feel they are lagging - there is a thin line between micromanagement and follow-up.
If you are very sure that a critical task is going under a spillover, raise a flag and clip the scope , re-orient the epic .
Try to control over-engineering , this can be ideated upon planning the epic but not while implementing the tickets. Remember all the discussions that are happening on the tickets they are also pushing the work for another day.
I feel good about the work done but how much ever I think I feel I could have done a better job at managing the Epic.
Major Kudos :
@giovannicimolin for helping me with forming the ticket and understanding the Epic.
@Ali for the work on the design and pitching in whenever we needed help.
@cassie for all the work and for helping me make those crucial decisions.
Let me know if there are any questions and Thank you.
Question: does this bring us any closer to being able to get rid of the “old” UI at manage.opencraft.com? I went to check this new UI out but it says “This page is not accessible by staff users yet.”
@braden these changes touch client/customer-facing interface, so a short answer to your question
is No, it doesn’t touch that part of the codebase.
The long answer will be the origination of OCIM UX 2.1 started with the intention to make the UX of the customer-facing interface more appealing to help to make onboarding new customers easy while the UI on manage.opencraft.com is only used by the staff.
yes this UI is only accessible to the customers, you can create a test account to check it out.
@Ali and I are happy with how it all turned out Great work to you, and @giovannicimolin! We look forward to improving it further when we get the chance.
@farhaan Kudos for managing this epic, as well as to @cassie@Ali and everyone who worked on the implementation – it’s a significant step up from the old clunky Ocim interface
And thanks also for the nice demo and the post-mortem – that’s something I wish we did more often at the end of projects, either internal or external ones, it’s really useful to see what has been accomplished, and get everyone to benefit from the experience.
PS: Would you mind moving this thread to the public category? I don’t think there is anything in here that needs to remain private? Also it would likely fit more in the “Discussions” section, since there is no urgency to get it seen by everyone within 24h, which is what the “Announcements” section is for.
- there is a thin line between micromanagement and follow-up.
and clip the scope 
, re-orient the epic 
.
, this can be ideated upon planning the epic but not while implementing the tickets. Remember all the discussions that are happening on the tickets they are also pushing the work for another day.
and Thank you.
This is a very neat improvement upon the previous version!
Great work to you, and 