(9 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
[[File:PageSync logo.png|frameless]]
 
[[File:PageSync logo.png|frameless]]
  
'''FlexForm''' is an enhanced HTML5 Form rendering engine.
+
The '''PageSync''' MediaWiki extension allows for storing any wiki page content to a file on the server. Allowing for it be e.g. pushed to git or bitbucket and deployed on another server. The reason for development of PageSync was to have all application artifacts, including templates, forms and other pages in the wiki, under version control.
  
It renders HTML5 form elements and allows editing or creating one or more pages with one form.
+
'''PageSync''' has a maintenance script to import pages from file. This enables automatic deployment of wikis and transfer of content from one wiki to another.
  
When you are familiar with creating HTML5 forms you will have no problem using '''FlexForm'''.  
+
'''PageSync''' is able to sync all Multi Revision Content slots and will also sync Files in the File namespace. Additionally you can save all synced files as a ZIP Archive and exchange the ZIP archive.  
  
To get started for the first time, have a look at the get started documentation.
+
Pages that have been added to '''PageSync''' can also be given ''tags'' and ''descriptions''. With these tags you can pick certain pages and files and combine them into one '''PageSync Share file'''. Such a share file can be shared with others that have '''PageSync''' installed and will only install the pages and files inside the Share file without adding them to '''PageSync'''. A one time pages and files instalment.
  
 +
For more information on installing and usage, please have a look at the documentation.
  
 +
== Scenario ==
 +
We usually have a developing environment. When developing is done, we push our code to a repository. From there we create a Docker container and we deploy it to a Testing server. From there it is deployed to an Acceptance server and finally to production.
  
'''FlexForm''' is a complete rewrite from the previous '''WSForm'''.
+
This is all fine with PHP and or JavaScript code, but we also create templates and widgets that are fundamental for it all to work properly.
  
=== Why FlexForm ===
+
With '''PageSync''', we can now also push our Templates, Widgets or any important Wiki page to our repository. When deploying a container, the '''PageSync''' maintenance script is automatically run and therefore also updating pages in the Wiki.
Currently there are several MediaWiki extensions that help you create Forms for your website.
 
  
What makes '''FlexForm''' different from the other extensions, is that it is really flexible. You can create a simple form (or a complex one) on any page and in any namespace.
+
== Need some help? ==
  
You do not have to use any special page to setup a form or to render it.
+
Need some help ?
  
It is also not bound to any kind of styling. This means that a simple form will not look very nice by default, but adding some css styling classes to the form gives you all the freedom in styling the form to any and all your needs. For those who are a bit less stylish, '''FlexForm''' will be supporting MediaWiki OOUI styling in the future by means of Themes.
+
Try the PageSync Discord channel at https://discord.gg/T8VTjtXGnV
  
'''FlexForm''' has Themes support.
+
or
  
 
+
Join the PageSync and FlexForm element channel : https://matrix.to/#/#wsform:matrix.org
'''FlexForm''' is very powerful.
 
 
 
'''One''' singe form can:
 
 
 
* create a page in the Wiki
 
* create several pages in the Wiki
 
* can edit a page in the Wiki
 
* can edit several pages in the Wiki
 
* can edit Multi Revision Content slots
 
* can send an email
 
* can upload a file
 
* can upload multiple files
 
 
 
Or do a combination of all of the above.
 
 
 
There are also Show on Select options, Multiple instances options and submit a form through Ajax (so the user stays on the page without any reload).
 
 
 
If you still want more features, check the documentation on the right.
 
 
 
=== How is it different from PageForms? ===
 
Some of the main difference are:
 
 
 
* PageForms will render forms through its Special page. The only exception is the ''autoedit'' parser function that will allow to edit a parameter in a template on a page using Ajax.
 
* PageForms renders an edit button on a page. With it you can edit Template parameters on a page.
 
* FlexForm can render a form on any page or render several forms on page. It allows for editing multiple Template parameters on a page or different pages.
 
* FlexForm will not read the content and template of a page and render an edit form. It does allow for you to create a very simple form that gives you all the freedom to show only relevant information to be edited.
 
* FlexForm is designed to handle multiple tasks with one form. Create or edit page(s), send an email, upload one or multiple files or a combination.
 
* FlexForm can be combined with the Chameleon skin and Bootstrap (or with custom js/css) to render forms in a popup, tab or collapsible element to create a more user-friendly experience where editing is part of the same page where you are also displaying information.
 
ws-class-props
Line 1: Line 1:
 
+
{{Doc properties
 +
|Doc subject=DevOps:Doc/PageSync
 +
|Subject version=1.5,2.0,2.1
 +
|Doc parent=
 +
|Doc sort order=10
 +
|Doc target group=User
 +
|Doc synopsis=About PageSync
 +
}}

Revision as of 22:21, 3 November 2022

PageSync logo.png

The PageSync MediaWiki extension allows for storing any wiki page content to a file on the server. Allowing for it be e.g. pushed to git or bitbucket and deployed on another server. The reason for development of PageSync was to have all application artifacts, including templates, forms and other pages in the wiki, under version control.

PageSync has a maintenance script to import pages from file. This enables automatic deployment of wikis and transfer of content from one wiki to another.

PageSync is able to sync all Multi Revision Content slots and will also sync Files in the File namespace. Additionally you can save all synced files as a ZIP Archive and exchange the ZIP archive.

Pages that have been added to PageSync can also be given tags and descriptions. With these tags you can pick certain pages and files and combine them into one PageSync Share file. Such a share file can be shared with others that have PageSync installed and will only install the pages and files inside the Share file without adding them to PageSync. A one time pages and files instalment.

For more information on installing and usage, please have a look at the documentation.

Scenario

We usually have a developing environment. When developing is done, we push our code to a repository. From there we create a Docker container and we deploy it to a Testing server. From there it is deployed to an Acceptance server and finally to production.

This is all fine with PHP and or JavaScript code, but we also create templates and widgets that are fundamental for it all to work properly.

With PageSync, we can now also push our Templates, Widgets or any important Wiki page to our repository. When deploying a container, the PageSync maintenance script is automatically run and therefore also updating pages in the Wiki.

Need some help?

Need some help ?

Try the PageSync Discord channel at https://discord.gg/T8VTjtXGnV

or

Join the PageSync and FlexForm element channel : https://matrix.to/#/#wsform:matrix.org