Naar inhoud springen

Hoofdpagina/en: verschil tussen versies

Uit KB Van Loenhout
FuzzyBot (overleg | bijdragen)
Bijgewerkt vanwege een nieuwe basisversie van de bronpagina
Geen bewerkingssamenvatting
 
(9 tussenliggende versies door 2 gebruikers niet weergegeven)
Regel 1: Regel 1:
<languages />
<languages />
<span id="Welkom_op_onze_wiki_voor_onze_WebsiteBaker_producten!"></span>
<span id="Welkom_op_de_wiki_voor_onze_WebsiteBaker_producten!"></span>
<div class="mw-translate-fuzzy">
== Welcome to the wiki for our WebsiteBaker products! ==
Welcome on our wiki!
</div>


<div lang="nl" dir="ltr" class="mw-content-ltr">
==== History ====
==== Geschiedenis: ====
When we switched hosting providers, we had to look for a new development environment for our websites. After an extensive process of research and testing, we settled on WebsiteBaker. Some of our criteria were: it must have a solid development history, be used by a large group of users or organizations, and, above all, be open source. And last but not least: it must be future-proof. As it has become clear that WebsiteBaker is no longer being actively developed, we have decided to switch to WBCE: a modern framework with active, future-proof ongoing development. We are currently in the process of converting all our modules, tools and templates for use within WBCE.
Door te wisselen van hosting provider moesten we op zoek gaan naar een nieuwe ontwikkelomgeving voor onze websites. Na een uitgebreid proces van uitzoeken en uitproberen zijn we op WebsiteBaker uitgekomen. Enkele criteria van ons zijn: het moet een gedegen ontwikkelgeschiedenis kennen, door een grote groep gebruikers cq organisaties gebruikt worden en bovenal Open Source zijn. En niet in de laatste plaats: toekomstbestendig zijn.
</div>


<div lang="nl" dir="ltr" class="mw-content-ltr">
==== Development ====
==== Ontwikkeling ====
We initially started with the standard WebsiteBaker platform, supplemented with third-party templates and modules. For various reasons, we began developing more and more of our own templates and modules, which better align with our vision of user-friendly, modern software. Our approach is to build a layer on top of the WebsiteBaker environment, based on WebsiteBaker’s features and supplemented with our own.
We zijn aanvankelijk gestart met de WebsiteBaker standaard, aangevuld met templates en modules van derden. Vanwege diverse redenen zijn we zelf steeds meer templates en modules gaan ontwikkelen, die beter aansluiten op onze eigen visie van gebruiksvriendelijke, moderne software. In onze visie bouwen we een laag bovenop de WebsiteBaker omgeving, gebaseerd op de WebsiteBaker functionaliteiten en aangevuld met onze eigen functionaliteiten.
</div>


<div lang="nl" dir="ltr" class="mw-content-ltr">
==== Ecosystem ====
==== Eco systeem ====
Ultimately, we decided to develop our own ecosystem, identifiable by the “FR” prefix in the names. Within this ecosystem, themes, templates, modules, and tools work well together. We believe it’s important that even a “less experienced” end user should be able to work with our products. This wiki is part of our commitment to user-friendliness.
Uiteindelijk zijn we uitgekomen op een eigen eco systeem te ontwikkelen, te herkennen aan de ''FR'' titels in de benamingen. In dit eco systeem werken de thema's, templates, modules en tools met elkaar goed samen . We vinden het belangrijk dat ook een 'minder ervaren' eindgebruiker met onze producten moet kunnen werken. Deze wiki is onderdeel van ons streven naar gebruiksvriendelijkheid.
 
</div>
==== Products? ====
We view what we have built—and continue to develop—as products. Created out of our passion and vision, they are freely available to everyone under the terms of the GNU General Public License 3 (GPL3). We follow the guidelines of the Dutch government; see [https://www.digitaleoverheid.nl/overzicht-van-alle-onderwerpen/open-source/beleid/ Open Source]
{| class="wikitable"
|+
!style="text-align:left"| Type
!style="text-align:left"| Target Area
!style="text-align:left"| Description
|-
|Theme
|back-end
|Appearance and functionalities for the website administrator/developer
|-
|Template
|front-end
|Appearance for website visitors
|-
|Module
|front-end
|Specific layout for displaying content, sometimes with interactive features
|-
|Tool
|back-end
|Functionalities / tools for the website administrator
|}


<div class="mw-translate-fuzzy">
== Get started quickly with... ==
== Get started quickly with... ==
* [https://wiki.vloenhout.nl/wiki/Media Media management]
* [https://wiki.vloenhout.nl/wiki/Media Media management]
* [https://wiki.vloenhout.nl/wiki/Pagina_inrichting Page layout]
* [https://wiki.vloenhout.nl/wiki/Pagina_inrichting Page layout]
Regel 28: Regel 43:
* [https://wiki.vloenhout.nl/wiki/FR_User_Management User management]
* [https://wiki.vloenhout.nl/wiki/FR_User_Management User management]
* [https://wiki.vloenhout.nl/wiki/WB_Backup Backups]
* [https://wiki.vloenhout.nl/wiki/WB_Backup Backups]
</div>
<div lang="nl" dir="ltr" class="mw-content-ltr">
== Snel aan de slag met... ==
* [https://wiki.vloenhout.nl/wiki/Media Media beheren]
* [https://wiki.vloenhout.nl/wiki/Pagina_inrichting Pagina inrichting]
* [https://wiki.vloenhout.nl/wiki/WYSIWYG_editor WYSIWYG editor]
* [https://wiki.vloenhout.nl/wiki/FR_User_Management Gebruikersbeheer]
* [https://wiki.vloenhout.nl/wiki/WB_Backup Backups]
</div>

Huidige versie van 31 aug 2026 09:03

Welcome to the wiki for our WebsiteBaker products!

History

When we switched hosting providers, we had to look for a new development environment for our websites. After an extensive process of research and testing, we settled on WebsiteBaker. Some of our criteria were: it must have a solid development history, be used by a large group of users or organizations, and, above all, be open source. And last but not least: it must be future-proof. As it has become clear that WebsiteBaker is no longer being actively developed, we have decided to switch to WBCE: a modern framework with active, future-proof ongoing development. We are currently in the process of converting all our modules, tools and templates for use within WBCE.

Development

We initially started with the standard WebsiteBaker platform, supplemented with third-party templates and modules. For various reasons, we began developing more and more of our own templates and modules, which better align with our vision of user-friendly, modern software. Our approach is to build a layer on top of the WebsiteBaker environment, based on WebsiteBaker’s features and supplemented with our own.

Ecosystem

Ultimately, we decided to develop our own ecosystem, identifiable by the “FR” prefix in the names. Within this ecosystem, themes, templates, modules, and tools work well together. We believe it’s important that even a “less experienced” end user should be able to work with our products. This wiki is part of our commitment to user-friendliness.

Products?

We view what we have built—and continue to develop—as products. Created out of our passion and vision, they are freely available to everyone under the terms of the GNU General Public License 3 (GPL3). We follow the guidelines of the Dutch government; see Open Source

Type Target Area Description
Theme back-end Appearance and functionalities for the website administrator/developer
Template front-end Appearance for website visitors
Module front-end Specific layout for displaying content, sometimes with interactive features
Tool back-end Functionalities / tools for the website administrator

Get started quickly with...