Join

Discord

ICF Church

ICF EQUIP

Check-in Church

huulo

ICF Website

Changed

Search thumbnails are retrieved via tiny.pictures

Subcategories are shown before the categories' resources to allow for quicker access

LazyCron is now triggered via the system cron instead of on page load - which should improve performance by lowering the load on our webservers

Admin login via email now works (previously only worked using the internal username)

Fixed

When resending an invite to a user, the invitations expiration date is reset

## Hey there, and welcome back!
It's been a really long time since you last heard from us. Sorry about that. We did however try to make this release count - and **we think we did just that!** 💪

While it might seem like a minor thing, actually improving the search makes all the difference for the user. You see, searching is at the core of almost all online behaviour. There's a reason that "googling" has become a verb, and I always chuckle when I hear sentences like "Just Google it on YouTube!" (which is technically less wrong than it first sounds - but I disgress... 🤔)

We wanted to give our users the search experience they deserve and are used to on the internet, which is far more difficult than it first sounds - if we try to do it ourselves.
Our search worked, and mostly returned the results one would expect - but the performance was, let's say, mediocre at best. 😐
We spent a lot of time investigating what could be improved to boost performance - and I mean **a LOT** of time - without much success. After all, building search is *not easy.* **... or is it?**

#### Enter Algolia!

[Algolia](https://www.algolia.com/) offers a hosted search API for sites like ours to use. Basically we just provide the data to be searched, and they handle the actual search request - complete with typo tolerance, custom rankings and more advanced features like synonyms or rules. All those features are nice and all - but they're not what we were after. Our #1 priority was improving the performance of our search, while still making sure our users receive the results they'd expect.
That was our requirement to Algolia... and boy, did they deliver! It's not just fast, it's - well, look: 👀
![Screenshot](https://i.postimg.cc/bNSWxWwz/Bildschirmfoto-2020-11-17-um-16-19-14.png)

Yes, that's one ms. No, I didn't click multiple times to get that result. 🤷‍♂️

Just [try it for yourself! It's **really** fast!](https://icf.church/equip/)

#### While we're at it...

Just as the search got so fast, it became really apparent that large images take some time to load. I mean, who wants to wait on the images loading after you already see the search results being generated?
So - we fixed it. Usually one would go about and automatically resize the image to the required dimensions on their own servers (requiring processing power), save it for future requests (requiring storage) and then deliver it to the user (requiring bandwidth). What if there was someone who already did all that? **Turns out: there is!**

[tiny.pictures](https://tiny.pictures/) is a service that acts both as a reverse proxy and as a CDN, all while being able to apply a variety of operations on the source image.
Sorry, what was that? 🤔 Alright, again:
The search thumbnails are now loaded from tiny.pictures. If they don't have the image yet, they load it from our server once, then resize it, crop it (even trying to keep faces in focus) and save it on *their* servers. For every following request they just immediately return the small version - resulting in lightning fast image load times! ⚡️


### Alright, but what else?

Of course, there are a few other things here and there. Most of them are minor reworks, some small tweaks here and there. We'll list a couple of them below.👇

### Thanks for reading!
As always, if you have any suggestions or ideas, or just wanna give us feedback: we're more than happy to hear from you! Get in touch! 🙂

<h2>Hey there, and welcome back!</h2>
It's been a really long time since you last heard from us. Sorry about that. We did however try to make this release count - and we think we did just that! 💪
While it might seem like a minor thing, actually improving the search makes all the difference for the user. You see, searching is at the core of almost all online behaviour. There's a reason that "googling" has become a verb, and I always chuckle when I hear sentences like "Just Google it on YouTube!" (which is technically less wrong than it first sounds - but I disgress... 🤔)
We wanted to give our users the search experience they deserve and are used to on the internet, which is far more difficult than it first sounds - if we try to do it ourselves.
Our search worked, and mostly returned the results one would expect - but the performance was, let's say, mediocre at best. 😐
We spent a lot of time investigating what could be improved to boost performance - and I mean a LOT of time - without much success. After all, building search is not easy. ... or is it?
<h4>Enter Algolia!</h4>
<a href="https://www.algolia.com/" target="_blank">Algolia</a> offers a hosted search API for sites like ours to use. Basically we just provide the data to be searched, and they handle the actual search request - complete with typo tolerance, custom rankings and more advanced features like synonyms or rules. All those features are nice and all - but they're not what we were after. Our #1 priority was improving the performance of our search, while still making sure our users receive the results they'd expect.
That was our requirement to Algolia... and boy, did they deliver! It's not just fast, it's - well, look: 👀
<img src="https://i.postimg.cc/bNSWxWwz/Bildschirmfoto-2020-11-17-um-16-19-14.png" alt="Screenshot" class="img-fluid">
Yes, that's one ms. No, I didn't click multiple times to get that result. 🤷‍♂️
Just <a href="https://icf.church/equip/" target="_blank">try it for yourself! It's really fast!</a>
<h4>While we're at it...</h4>
Just as the search got so fast, it became really apparent that large images take some time to load. I mean, who wants to wait on the images loading after you already see the search results being generated?
So - we fixed it. Usually one would go about and automatically resize the image to the required dimensions on their own servers (requiring processing power), save it for future requests (requiring storage) and then deliver it to the user (requiring bandwidth). What if there was someone who already did all that? Turns out: there is!
<a href="https://tiny.pictures/" target="_blank">tiny.pictures</a> is a service that acts both as a reverse proxy and as a CDN, all while being able to apply a variety of operations on the source image.
Sorry, what was that? 🤔 Alright, again:
The search thumbnails are now loaded from tiny.pictures. If they don't have the image yet, they load it from our server once, then resize it, crop it (even trying to keep faces in focus) and save it on their servers. For every following request they just immediately return the small version - resulting in lightning fast image load times! ⚡️
<h3>Alright, but what else?</h3>
Of course, there are a few other things here and there. Most of them are minor reworks, some small tweaks here and there. We'll list a couple of them below.👇
<h3>Thanks for reading!</h3>
As always, if you have any suggestions or ideas, or just wanna give us feedback: we're more than happy to hear from you! Get in touch! 🙂

Hey there, and welcome back!

It's been a really long time since you last heard from us. Sorry about that. We did however try to make this release count - and we think we did just that! 💪

While it might seem like a minor thing, actually improving the search makes all the difference for the user. You see, searching is at the core of almost all online behaviour. There's a reason that "googling" has become a verb, and I always chuckle when I hear sentences like "Just Google it on YouTube!" (which is technically less wrong than it first sounds - but I disgress... 🤔)

We wanted to give our users the search experience they deserve and are used to on the internet, which is far more difficult than it first sounds - if we try to do it ourselves.
Our search worked, and mostly returned the results one would expect - but the performance was, let's say, mediocre at best. 😐
We spent a lot of time investigating what could be improved to boost performance - and I mean a LOT of time - without much success. After all, building search is not easy. ... or is it?

Enter Algolia!

Algolia offers a hosted search API for sites like ours to use. Basically we just provide the data to be searched, and they handle the actual search request - complete with typo tolerance, custom rankings and more advanced features like synonyms or rules. All those features are nice and all - but they're not what we were after. Our #1 priority was improving the performance of our search, while still making sure our users receive the results they'd expect.
That was our requirement to Algolia... and boy, did they deliver! It's not just fast, it's - well, look: 👀
Screenshot

Yes, that's one ms. No, I didn't click multiple times to get that result. 🤷‍♂️

Just try it for yourself! It's really fast!

While we're at it...

Just as the search got so fast, it became really apparent that large images take some time to load. I mean, who wants to wait on the images loading after you already see the search results being generated?
So - we fixed it. Usually one would go about and automatically resize the image to the required dimensions on their own servers (requiring processing power), save it for future requests (requiring storage) and then deliver it to the user (requiring bandwidth). What if there was someone who already did all that? Turns out: there is!

tiny.pictures is a service that acts both as a reverse proxy and as a CDN, all while being able to apply a variety of operations on the source image.
Sorry, what was that? 🤔 Alright, again:
The search thumbnails are now loaded from tiny.pictures. If they don't have the image yet, they load it from our server once, then resize it, crop it (even trying to keep faces in focus) and save it on their servers. For every following request they just immediately return the small version - resulting in lightning fast image load times! ⚡️

Alright, but what else?

Of course, there are a few other things here and there. Most of them are minor reworks, some small tweaks here and there. We'll list a couple of them below.👇

Thanks for reading!

As always, if you have any suggestions or ideas, or just wanna give us feedback: we're more than happy to hear from you! Get in touch! 🙂


Improved Search Behavior

Improved previews of files and videos

Added

Over the past few weeks, we have reworked large amounts of our code base to make the site faster and more secure. We have also improved the way files are previewed:

**Old way:**
![Screenshot-2019-04-09-at-16-50-58.png](https://i.postimg.cc/zvF8QvDh/Screenshot-2019-04-09-at-16-50-58.png)

**Shiny new previews:**
![Screenshot-2019-04-09-at-16-53-14.png](https://i.postimg.cc/d3YJnrFv/Screenshot-2019-04-09-at-16-53-14.png)

Over the past few weeks, we have reworked large amounts of our code base to make the site faster and more secure. We have also improved the way files are previewed:
Old way:
<img src="https://i.postimg.cc/zvF8QvDh/Screenshot-2019-04-09-at-16-50-58.png" alt="Screenshot-2019-04-09-at-16-50-58.png" class="img-fluid">
Shiny new previews:
<img src="https://i.postimg.cc/d3YJnrFv/Screenshot-2019-04-09-at-16-53-14.png" alt="Screenshot-2019-04-09-at-16-53-14.png" class="img-fluid">

Over the past few weeks, we have reworked large amounts of our code base to make the site faster and more secure. We have also improved the way files are previewed:

Old way:
Screenshot-2019-04-09-at-16-50-58.png

Shiny new previews:
Screenshot-2019-04-09-at-16-53-14.png


Backend Updates 🖥️

![New Homepage](https://cloud.headwayapp.co/changelogs_images/images/big/000/024/204-f6899ae636f5af9377da5d97162aebb922b45415.png)
We have redesigned our homepage for you. Featured resources are now front and center and the resources of categories you follow are now more prominent. We also redesigned and streamlined the navigation.There you'll find a new category overview as well as your user settings.

<img src="https://cloud.headwayapp.co/changelogs_images/images/big/000/024/204-f6899ae636f5af9377da5d97162aebb922b45415.png" alt="New Homepage" class="img-fluid">
We have redesigned our homepage for you. Featured resources are now front and center and the resources of categories you follow are now more prominent. We also redesigned and streamlined the navigation.There you'll find a new category overview as well as your user settings.

New Homepage
We have redesigned our homepage for you. Featured resources are now front and center and the resources of categories you follow are now more prominent. We also redesigned and streamlined the navigation.There you'll find a new category overview as well as your user settings.


New Homepage 🎉

Church-Email-Domains: The user can now register for an Equip account if she/he logs in with a social account and an email address that is linked to an existing church email domain.

Invite related functions have been refactored to a module

In this release, we improved the onboaring for new users:

In this release, we improved the onboaring for new users:

In this release, we improved the onboaring for new users:


Social Login with E-Mail Domain 

User Login with accounts of Gmail, Facebook and Microsoft

Church Admins can invite other members

You can now also search for resource types and categories

Collections can feature a set of related resources

Clicking on overview pages from the breadcrumb redirects to the homepage instead of throwing a nasty error.

[ICF Equip](https://www.icf.church/equip/) is our new resource platform, created to empower you and your local church. 


<a href="https://www.icf.church/equip/" target="_blank">ICF Equip</a> is our new resource platform, created to empower you and your local church.

ICF Equip is our new resource platform, created to empower you and your local church. 
