Fix links

Author: JulienPeloton

docs/broker/roadmap.md

@@ -24,7 +24,7 @@ Although Fink is capable to listen to various streams, its design is driven by l
 
 ### Zwicky Transient Facility
 
-Since 2019, Fink is operating on the [ZTF :lucide-external-link:](https://www.ztf.caltech.edu/){target="blank_"} public alert stream, which has constituted an excellent opportunity to engage projects with the scientific community while preparing the ground for the Rubin Observatory alert data. Have a look at the [publication list :lucide-external-link:](https://fink-broker.org/papers/){target="blank_"} for example, or the [SN Ia candidates :lucide-external-link:](https://www.wis-tns.org/search?&discovered_period_value=1&discovered_period_units=years&unclassified_at=0&classified_sne=0&include_frb=0&name=&name_like=0&isTNS_AT=all&public=all&ra=&decl=&radius=&coords_unit=arcsec&reporting_groupid%5B%5D=null&groupid%5B%5D=null&classifier_groupid%5B%5D=null&objtype%5B%5D=null&at_type%5B%5D=null&date_start%5Bdate%5D=&date_end%5Bdate%5D=&discovery_mag_min=&discovery_mag_max=&internal_name=&discoverer=Fink&classifier=&spectra_count=&redshift_min=&redshift_max=&hostname=&ext_catid=&ra_range_min=&ra_range_max=&decl_range_min=&decl_range_max=&discovery_instrument%5B%5D=null&classification_instrument%5B%5D=null&associated_groups%5B%5D=null&official_discovery=0&official_classification=0&at_rep_remarks=&class_rep_remarks=&frb_repeat=all&frb_repeater_of_objid=&frb_measured_redshift=0&frb_dm_range_min=&frb_dm_range_max=&frb_rm_range_min=&frb_rm_range_max=&frb_snr_range_min=&frb_snr_range_max=&frb_flux_range_min=&frb_flux_range_max=&num_page=50&display%5Bredshift%5D=1&display%5Bhostname%5D=1&display%5Bhost_redshift%5D=1&display%5Bsource_group_name%5D=1&display%5Bclassifying_source_group_name%5D=1&display%5Bdiscovering_instrument_name%5D=0&display%5Bclassifing_instrument_name%5D=0&display%5Bprograms_name%5D=0&display%5Binternal_name%5D=1&display%5BisTNS_AT%5D=0&display%5Bpublic%5D=1&display%5Bend_pop_period%5D=0&display%5Bspectra_count%5D=1&display%5Bdiscoverymag%5D=1&display%5Bdiscmagfilter%5D=1&display%5Bdiscoverydate%5D=1&display%5Bdiscoverer%5D=1&display%5Bremarks%5D=0&display%5Bsources%5D=0&display%5Bbibcode%5D=0&display%5Bext_catalogs%5D=0){target="blank_"} sent every night to the Transient Name Server! More information is available on the [ZTF documentation website :lucide-external-link:](https://doc.ztf.fink-broker.org/en/latest/){target="blank_"}.
+Since 2019, Fink is operating on the [ZTF :lucide-external-link:](https://www.ztf.caltech.edu/){target="blank_"} public alert stream, which has constituted an excellent opportunity to engage projects with the scientific community while preparing the ground for the Rubin Observatory alert data. Have a look at the [publication list :lucide-external-link:](https://fink-broker.org/papers/){target="blank_"} for example, or the [SN Ia candidates :lucide-external-link:](https://www.wis-tns.org/search?&discovered_period_value=1&discovered_period_units=years&unclassified_at=0&classified_sne=0&include_frb=0&name=&name_like=0&isTNS_AT=all&public=all&ra=&decl=&radius=&coords_unit=arcsec&reporting_groupid%5B%5D=null&groupid%5B%5D=null&classifier_groupid%5B%5D=null&objtype%5B%5D=null&at_type%5B%5D=null&date_start%5Bdate%5D=&date_end%5Bdate%5D=&discovery_mag_min=&discovery_mag_max=&internal_name=&discoverer=Fink&classifier=&spectra_count=&redshift_min=&redshift_max=&hostname=&ext_catid=&ra_range_min=&ra_range_max=&decl_range_min=&decl_range_max=&discovery_instrument%5B%5D=null&classification_instrument%5B%5D=null&associated_groups%5B%5D=null&official_discovery=0&official_classification=0&at_rep_remarks=&class_rep_remarks=&frb_repeat=all&frb_repeater_of_objid=&frb_measured_redshift=0&frb_dm_range_min=&frb_dm_range_max=&frb_rm_range_min=&frb_rm_range_max=&frb_snr_range_min=&frb_snr_range_max=&frb_flux_range_min=&frb_flux_range_max=&num_page=50&display%5Bredshift%5D=1&display%5Bhostname%5D=1&display%5Bhost_redshift%5D=1&display%5Bsource_group_name%5D=1&display%5Bclassifying_source_group_name%5D=1&display%5Bdiscovering_instrument_name%5D=0&display%5Bclassifing_instrument_name%5D=0&display%5Bprograms_name%5D=0&display%5Binternal_name%5D=1&display%5BisTNS_AT%5D=0&display%5Bpublic%5D=1&display%5Bend_pop_period%5D=0&display%5Bspectra_count%5D=1&display%5Bdiscoverymag%5D=1&display%5Bdiscmagfilter%5D=1&display%5Bdiscoverydate%5D=1&display%5Bdiscoverer%5D=1&display%5Bremarks%5D=0&display%5Bsources%5D=0&display%5Bbibcode%5D=0&display%5Bext_catalogs%5D=0){target="blank_"} sent every night to the Transient Name Server! More information is available on the [ZTF documentation website :lucide-external-link:](https://doc.ztf.fink-broker.org){target="blank_"}.
 
 ### Rubin Observatory
 

docs/data/ztf_to_lsst.md

@@ -34,7 +34,7 @@ In LSST, webpages are indexed by both the static identifier (`diaObjectId`) and
 
 ## Alert classification
 
-In ZTF, users had the ability to create filters that combined multiple alert fields, enabling them to generate meaningful tags tailored to their research needs. These tags were then used to propose a [single alert classification label :lucide-external-link:](https://doc.ztf.fink-broker.org/en/latest/broker/classification/){label="blank_"}. However, this method had three limitations:
+In ZTF, users had the ability to create filters that combined multiple alert fields, enabling them to generate meaningful tags tailored to their research needs. These tags were then used to propose a [single alert classification label :lucide-external-link:](https://doc.ztf.fink-broker.org/science/classification/){label="blank_"}. However, this method had three limitations:
 
 1. **Inconsistent labeling between Livestream and API**: Not all tags were utilized in creating the final (single) classification label.
 2. **Limited classification per alert**: Each alert could have only one classification label, making it impossible to represent different perspectives.
@@ -117,4 +117,4 @@ Beware of the fact that `/api/v1/objects` had another meaning for ZTF (see above
 
 ### Resolver
 
-The argument `name` for the endpoint `/api/v1/resolver` for ZTF is named `name_or_id` for LSST.
+The argument `name` for the endpoint `/api/v1/resolver` for ZTF is named `name_or_id` for LSST.

docs/science/filters.md

@@ -27,7 +27,7 @@ Check out the [tutorial](../developers/filter_tutorial.md) to construct a Fink F
 
 ### Kafka streams
 
-As we process alerts, interesting alerts are automatically picked up by filters and [Apache Kafka :lucide-external-link:](https://kafka.apache.org/){target="blank_"} queues are populated. Each stream from a particular filter is identified by a topic name. This stream can be accessed outside via its topic, and several users can poll the data independently from the same topic. All topics can be accessed using the [Fink client :lucide-external-link:](https://github.com/astrolabsoftware/fink-client){target="blank_"}, which is a wrapper around Kafka consumer functionalities (see [Livestream documentation](https://doc.lsst.fink-broker.org/en/latest/services/livestream)).
+As we process alerts, interesting alerts are automatically picked up by filters and [Apache Kafka :lucide-external-link:](https://kafka.apache.org/){target="blank_"} queues are populated. Each stream from a particular filter is identified by a topic name. This stream can be accessed outside via its topic, and several users can poll the data independently from the same topic. All topics can be accessed using the [Fink client :lucide-external-link:](https://github.com/astrolabsoftware/fink-client){target="blank_"}, which is a wrapper around Kafka consumer functionalities (see [Livestream documentation](https://doc.lsst.fink-broker.org/services/livestream)).
 
 ### REST API & Science Portal