My turn this week to update you on what the Community Platform Team have been up to, and what a busy week it has been.
Let's jump right in, shall we?
Saying goodbye to 3 team members
Today, we say a fond farewell to @meezaan, @shivanshuit914 and Rupert from our team, as they're all off on exciting new adventures outside of giffgaff. All three have been instrumental in preparing Flarum as our new platform, and we certainly would not be where we are today without them. I'd like to extend my personal thanks, and I'm sure the wider community's thanks to them for all their hard work, and wish them every success in the future.
In their place, we welcome Mags and @harrycollins97 to the team, who I'm sure you'll be hearing from in a future dev diary, so do look out for more from them over the coming weeks.
@meezaan has been making excellent progress towards our overall search performance this week, with the first version now up and running on our internal testing community.
Early results are amazing, with general search terms being displayed almost instantly - a vast improvement, I'm sure you'll agree. In turn, this also increases the speed of pageloads when switching between tags or visiting large discussion threads.
This has been the area I've been working on over the past couple of weeks, so firstly may I offer my apologies for the delay in getting these calculations out to you.
Having decided to dedicate my pre-launch development time to migrating almost 10 years worth of member content over from Lithium, developing the payback calculations was always top of the post-launch plans. As you know, payback is unique to giffgaff, so a custom solution, built from scratch is needed.
It's fair to say that this has been a painful journey from the start, with a couple of rapid fails to boot. Late last week however, everything started falling into place. The last piece of the puzzle fell neatly into place on Tuesday of this week, and the end result is we now have a semi-automated payback data extraction tool built for Flarum. Over the coming weeks and months, we'll be further improving this so that by the end of the year the entire extraction process is automated - hoorah!
This week, @andrewdyer and @harrycollins97 have been working on a complete revamp on the Flarum 'Private Discussions' feature. I'll also now be joining the effort here now Payback is finished 🙂 From your feedback, we learnt that in their current state, many of you found PDs 'clunky' to use, to say the least.
Changes made so far include:
- Removed the ability to start a private discussion from the 'Start discussion' button
- Created a dedicated 'Start private discussion' section within the member profile page
- Removed the requirement to select a tag for a private discussion
- Added a warning if you try to send a PD to yourself only
- Option to receive notifications (web and/or email) for new Private Discussions
Still to go (but being worked on as we speak)
- Option to receive notifications for follow up posts in a private discussion
- Ability to remove yourself from a private discussion
I fast-tracked the PD notification work, which was deployed in the early hours of yesterday morning, hopefully you've already noticed the extra setting in your profile page 😉 I’ve also contributed this code back to the Flarum open source repository, so that the wider Flarum world may also benefit.
We've pencilled in releasing the Private Discussions update around the middle of next week, so keep an eye out for that.
Testing, testing, and more testing
@tariqthedev has been focused this week on writing more and more tests for the entire community platform. The more tests the better in our book.
That wraps up our lowdown on the week! Do feel free to fire any questions to us, and please keep leaving us your feedback - we really do appreciate it 🙂