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.
6 Comments
fabio
11-17-2009
Sarei curioso di vedere la demo, però sembra non funzionare ancora... riproverò più avanti...
Stefano Rosanelli
11-17-2009
Fabio,
stavamo aggiornando la demo all'ultima versione rilasciata oggi... abbiamo risolto un paio di problemi, adesso sembra tutto a posto.
grazie della segnalazione
Andrew
11-23-2009
Seems like the demo sites are down. I'm interested to check out the CMS. Let me know when they are working.
Stefano Rosanelli
11-23-2009
Andrew,
the demo sites seem to be up and running at the moment - please let us know exactly what kind of problems you see (unreachable host, or http errors like 404/500...)
Andrew
11-23-2009
According to http://downforeveryoneorjustme.com/http://manage.demo.bedita.com/ it seems like the site is up.
I get:
"The connection has timed out
The server at site.demo.bedita.com is taking too long to respond."
Stefano Rosanelli
11-23-2009
Thanks for your feedback, as your test on 'downforevery...' suggests it seems to be a network-related problem. Here everything works as expected: the demo server is not optimal/optimized, but response times are reasonable.
I will ask our sysadmins and find out if there's something we could do.
Bye
Write a comment
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.

