Anyone with the Site Builder role can add new users and modify roles on their Open Berkeley site. New users will need to log in to the site first before a role can be added. Please see Add New Users and Modify Roles.
We don't typically recommend opening links in new tabs. The World Wide Web Consortium (W3C) does not recommend this practice, as it takes the control out of the user's hands (opening a new tab without the user's consent).
It's also an accessibility best practice to not have links open automatically in a new tab/window, as links opening automatically in new tabs/windows can cause confusion for screen reader users, as well as users with certain cognitive disabilities. Visitors without disabilities can always choose to open links in a new browser window or tab if they desire (e.g., right-click the link and select "Open Link in New Tab" or "Open Link in New Window").
For more information, please see "Can I have links on my website automatically open in a new tab?" on the Web Access website.
No, not unless you are using one of our built-in widget types. (See below for a list.) Content and widgets generated by third-party services may cause security, accessibility, and maintenance problems if embedded directly.
Embedding a widget that has not been properly tested with the Open Berkeley platform could have any of the following issues:
- The widget could display improperly (especially if it loads an application/product that requires some kind of authentication)
- The widget could be using insecure code that will pose security risks for your site visitors
- The widget could load functionality that is not accessible to people with disabilities (in violation of the UC accessibility policy)
In order to prevent these issues, tags used to embed external content, including but not limited to iframe tags, object and embed tags, and script tags, are stripped from your page content when saving.
Several of our widget options allow for embedding of outside content, such as charts, videos, and bConnected / Google products:
If the information you need to display is from an external site or application and is not included in the above list, you can simply link to it instead of embedding it on your site.
If you have any questions, please email firstname.lastname@example.org.
The first action you should take is to flush cache on your site - see the Site Builders Guide. You or someone else with the Site Builder role will have to do this. If flushing caches does not fix the issue, please email email@example.com with the following information:
- Which site you are working on
- An explanation of the problem you are seeing (include screenshots if possible, and include URLs to specific pages on your site)
- If applicable, provide any notes about which actions you were taking on your site before this issue started occurring
I heard that my website needs to be accessible to conform with the UC accessibility policy. Is my Open Berkeley site accessible?
Accessibility is built in to the Open Berkeley platform! This means that most of "heavy lifting" has been taken care of in regards to the overall accessibility of any standard Open Berkeley website.
However, as content creators on your site, there are additional actions you can take to ensure that your content is accessible as possible to people with disabilities. See Accessibility for more information.
Can I still use my test site after my site launches? Is there a way to "stage" edits on my test site and then move automatically to the live site?
Yes, the test site is available for use after your site launches (once your site is live, all "real" edits need to be made on the live site). However, the test site is meant only to be used as a "sandbox" (a place to experiment) once your site is live. Once you try something out on test, you will need to re-create your finalized changes on your live site.
See the details outlined in Site Launch. The Web Platform Services team will need at least two weeks' notice for a proposed go-live.
Once you have reviewed the Site Launch details (linked above), email firstname.lastname@example.org with the following information:
- Which site you would like to launch
- The name of the appropriate "Resource Proprietor" for your site
- When you would like to launch
Open Berkeley sites support the campus Berkeley Brand standards. The Berkeley wordmark, site name font, and Cal favicon (the icon displayed in the browser's tab bar) are part of the Berkeley Brand. See our documentation on Berkeley Brand theme options for information on how to configure the display of your site's header and footer. Also we encourage you to reach out to the Brand team at https://brand.berkeley.edu/contact/ to see if they can consult with you or your team on understanding campus branding guidelines.
Although the Berkeley Brand does not allow custom logos in the header, you have the option to place your own logo in the footer, or on your home page or landing page for a particular section. You can create a reusable widget that would allow you to place the same logo image on multiple pages.