BEdita | Semantic Content Management Framework
Fork me on GitHub

Give BEdita a try

Try out a typical BEdita setup.

Browse the following links to play with:

  • manage.demo.bedita.com
    the BEdita backend, the whole back-office management console
  • site.demo.bedita.com
    the public web site, an example of typical front-office pages, call it "main frontend"
  • staging.demo.bedita.com
    the front-office pre-publishing test site, a replication of the "main frontend" where you can easily test and preview your modifications (Draft items too, see below), thanks also to the precious contextual application bar. Referring to it as "staging frontend"

 

Credentials to login are:

      Username: bedita

 

    Password: bedita

[values are case sensitive]

 

N.B.: The three sites listed here are all part of the same installation and related each other, i.e. every change applied to managed content in the backend will be immediately visible in frontends.
Also note that contents marked as Draft (in Object Properties) are only visibile in staging site: they are automatically hidden in main public site, hence you can use the Draft status for testing purposes.

Notes:

  • email queuing is disabled: hence thinks like notifications or newsletter invoices will not work;
  • this demo undergoes a full reset once a day, default initial settings and publications are automatically restored every night;
  • the server hosting this demonstration has limited resources, a crowded concurrent use of the site may cause delays in response time;
  • In BEdita every single root in contents tree establishes one "Publication"; the front-office web site presented here is available only for the very first publication in the back-office management console.