Ftrtch teamdays

looking back & ahead

products

Hubs

We have made a large amount of new hubs. Most of them were Google hubs, but we also made hubs for PGGM, the future of Google, APG and the outside world. We are adding new features and improving the 'hub-train' each itteration

Websites

Although we often say we aren't website builders, we have build and maintained websites for the outside world, Noordzeker, nieuwe collectiviteit (rip) and of cource our own ftrprf website. 

Dashboards

We started our dashboard journey with Ears, but sincethen have come a long way with possibilities. This year we have build 2 pggm dashboards and we are currently working on a dashboard for the outside world, which is hopefully the next step in our dashbboard journey.

Monitors

Dashboards are a good way to get insights from the data in ftrlbs, but with the first outside world monitor we have taken this to the next level. There is still a lot to improve, but we are very proud on how far we've come with the monitor!

numbers

0

people who asked if they have to go to 'the old' or 'the new' cms

62

test emails in 1 day for testing the new google contact form

a lot

of google articles added in our own cms

84

trainrides to Amsterdam

152

user accounts in the database reached

35

new libraries (ftrlbs) for the outside world

systems

ftrlbs

ftrlbs has improved a lot this year. We have added a lot of features, especially since the arrival of the outside world. A few of these features include the possibility of importing sources directly out of meltwater, making connections between libraries and the possibilty of adding comments. Furthermore, ftrlbs is become Jeroen's very own playground, so please challenge him to make even more cool features. He has a lot of fun with mindmaps and generating pdf's.

ftrcms

The CMS is always evolving. Thanks to the amount of Google hubs we made, we improved the process of generating outreaches by a lot. If you want information on all the new things possible, ask Anne ;). We also worked on tracking if attendees opened pages (or even a personal PDF, also ask Anne..).
Furthermore, the page builder has improved a lot this year as well. We always work as generic as possible, instead of building something for single use. This was the year that Jesper found out why, because it started to really pay off. It's quite easy to transfer widgets across projects or to build new projects that are simular to others. 

Looking forward

Jeroen is now going to tell you all about ftrtch's plans for next year :)

  • (Generative) AI
  • ftrlbs / cms
  • Google Cloud Spaces (flutter & rive)