Merge im, teamchat and video-voice into real-time-communication #1136
@ -5,6 +5,7 @@ sass:
|
||||
style: compressed
|
||||
plugins:
|
||||
- jekyll-sitemap
|
||||
- jekyll-redirect-from
|
||||
|
||||
sitemap:
|
||||
file: "/sitemap.xml"
|
||||
include: [".well-known"]
|
||||
|
@ -49,14 +49,12 @@
|
||||
<a class="dropdown-item" href="/software/email/"><i class="fas fa-envelope fa-fw"></i> Email Clients</a>
|
||||
<a class="dropdown-item" href="/software/encryption-tools/"><i class="fas fa-lock fa-fw"></i> File Encryption</a>
|
||||
<a class="dropdown-item" href="/software/file-sharing/"><i class="fas fa-file-export fa-fw"></i> File Sharing</a>
|
||||
<a class="dropdown-item" href="/software/im/"><i class="fab fa-telegram-plane fa-fw"></i> Instant Messenger</a>
|
||||
<a class="dropdown-item" href="/software/teamchat/"><i class="fas fa-users fa-fw"></i> Team chat</a>
|
||||
<a class="dropdown-item" href="/software/passwords/"><i class="fas fa-user-lock fa-fw"></i> Password Manager</a>
|
||||
<a class="dropdown-item" href="/software/productivity/"><i class="fas fa-briefcase fa-fw"></i> Productivity Tools</a>
|
||||
<a class="dropdown-item" href="/software/real-time-communication/"><i class="fab fa-telegram-plane fa-fw"></i> Real-Time Communication</a>
|
||||
<a class="dropdown-item" href="/software/file-sync/"><i class="fas fa-copy fa-fw"></i> Secure File Sync</a>
|
||||
<a class="dropdown-item" href="/software/networks/"><i class="fas fa-user-secret fa-fw"></i> Self-contained Networks</a>
|
||||
<a class="dropdown-item" href="/software/cloud/"><i class="fas fa-hdd fa-fw"></i> Self-Hosted Cloud Server</a>
|
||||
<a class="dropdown-item" href="/software/voip/"><i class="fas fa-phone fa-fw"></i> Video & Voice Messenger</a>
|
||||
</div>
|
||||
</li>
|
||||
<li class="nav-item dropdown">
|
||||
|
@ -1,8 +0,0 @@
|
||||
---
|
||||
layout: page
|
||||
permalink: /software/im/
|
||||
title: "Instant Messaging"
|
||||
description: "Discover secure and private ways to message others online without letting any third parties read your messages."
|
||||
---
|
||||
|
||||
{% include sections/instant-messenger.html %}
|
20
pages/software/real-time-communication.html
Normal file
20
pages/software/real-time-communication.html
Normal file
@ -0,0 +1,20 @@
|
||||
---
|
||||
layout: page
|
||||
permalink: /software/real-time-communication/
|
||||
redirect_from:
|
||||
- /software/im/
|
||||
- /software/voip/
|
||||
- /software/teamchat/
|
||||
title: "Real-Time Communication"
|
||||
description: "Discover secure and private ways to communicate with others online without letting any third parties read your messages."
|
||||
![]() I thought that this was the best applying description to them all together. I thought that this was the best applying description to them all together.
![]() That sounds good to me. That sounds good to me.
|
||||
---
|
||||
|
||||
{% include sections/instant-messenger.html %}
|
||||
|
||||
<hr/>
|
||||
![]() I wish to have some separator between the different sections, even if they are on the same page. I wish to have some separator between the different sections, even if they are on the same page.
![]() And I think this ordering makes the most sense as I think people are most often looking for instant messengers, then VoIP and team chat is a bit rarer scenario as I think that is mostly forced on people from whichever the team founder prefers. And I think this ordering makes the most sense as I think people are most often looking for instant messengers, then VoIP and team chat is a bit rarer scenario as I think that is mostly forced on people from whichever the team founder prefers.
![]() Yeah the breaks work well in my perspective. Yeah the breaks work well in my perspective.
|
||||
|
||||
{% include sections/voice-video-messenger.html %}
|
||||
|
||||
<hr/>
|
||||
|
||||
{% include sections/teamchat.html %}
|
@ -1,8 +0,0 @@
|
||||
---
|
||||
layout: page
|
||||
permalink: /software/teamchat/
|
||||
title: "Team chat"
|
||||
description: "Discover secure and private ways to communicate with your team online without letting any third parties read your messages."
|
||||
---
|
||||
|
||||
{% include sections/teamchat.html %}
|
@ -1,8 +0,0 @@
|
||||
---
|
||||
layout: page
|
||||
permalink: /software/voip/
|
||||
title: "VoIP"
|
||||
description: "Find a voice and video messenger that supports completely End-to-End encrypted calls."
|
||||
---
|
||||
|
||||
{% include sections/voice-video-messenger.html %}
|
Reference in New Issue
Block a user
I think @JonahAragon said that he would do this with nginx which is more elegant, but I guess it won't hurt being here too as Nginx is going to take a preference and in case nginx got forgotten, the user wouldn't see that much of a difference.