WordPress Themes

When it comes to WordPress, customizing the look of your site is simple and straightforward. When you install WordPress, the default (or pre-set) theme is called Twenty Seventeen (as of WordPress version 4.8). It is a very customizable theme.

You can find general information about Twenty Seventeen here.

In addition to Twenty Seventeen, you’ll have other themes available to you. (What themes you have depends upon if you did a default WordPress installation, or if you installed a special package.) If Twenty Seventeen doesn’t meet your needs, you can activate another theme on your site or install a completely new one.

Activating Themes

  1. Start at your site’s Dashboard.
    Screenshot of WordPress dashboard
  2. Navigate to Appearance > Themes.
    screen shot of WordPress theme options
  3. You will see thumbnail images representing each of the themes that you currently have available on your site. Simply mouse over any one of them, and click the Activate link.
    screen shot of activating different wordpress theme

That’s all you need to do to change the look of your site with a new theme.

Installing Themes

If none of the themes that were provided when you installed WordPress are what you’re looking for, you can always search for and install other themes from the WordPress Theme Repository.

  1. Navigate to Appearance > Themes.
    screen shot of WordPress theme options
  2. Installing new themes is quite simple. You start by going to the Add New Button.
    Screen shot of
  3. The initial page is the Search Theme page, and it’s not visually helpful. You can check a few filter boxes to see what comes up, but there is a more visual way. Click the Featured link at the top and you’ll get visual (screenshot) examples of other themes you can install. You can also click Newest or Recently Updated.
  4. Under the thumbnail picture of each theme (when you hover your mouse over the theme) are three choices – InstallPreview, and Details & Preview. Those choices should be pretty self-explanatory so click Install to add a new theme to your site.
  5. After you install the theme, it is still not active on your site. You will need to Activate it to use it.
    Activate desired theme by clicking

Once activated, your site will be using the new theme. Visit your site’s homepage to view your new theme.

Creating a Book

To get started in Scalar, you will need to create a book.

  1. Go to your Scalar site via the My Apps link or the Scalar URL you established during the setup process.
    Access Scalar site and click the Sign-in link
  2. Log in to Scalar using the username and password you set up during the installation process.
    log into scalar with your email and Scalar password
  3. Go to the top right corner and click, Dashboard.
    Scalar landing page and dashboard link
  4. Select the My Account tab and at the bottom of the page type in a title for your book. This can be changed at a later time if needed. Click Create.
    Scalar create new book
  5. You now see your book in the “My books” list. From there you will be able to build your Scalar book.

What is Domain Mapping?

Domain mapping, simply put, is deciding where visitors should be directed when they visit various pieces of your website. Domains and subdomains can be mapped directly to folders located within your webhosting account, where you may have installed WordPress, Omeka, MediaWiki, or other web applications. Domains and subdomains can also be mapped to some third-party providers.

Static and Dynamic Websites

Static Websites

In the early days of the Web, almost all Web sites were what is known as 'static sites.' Content (text, images, video, audio, etc), was placed or embedded in a file in which HTML tags were used to format it. If you looked at the actual contents of the file, you might see something like this:

example of static HTML code

The content and the tags lived side-by-side. To edit the page, you’d open up the file (on your own computer) in a program capable of editing HTML files and make changes to either the content or the presentation. Every page had to be edited individually, even if the edits you were making were for common elements that appeared on many pages (like menu bars).

From a technical perspective, accessing a static Web site is fairly straightforward. When your computer is connected to the Internet, you can use a Web browser to access files on a Web server (as long as you know the address). The Web server delivers the contents of those files to your browser, and your browser displays them.

Dynamic Websites

Over time, as the Web became more sophisticated, new systems emerged for creating and managing Web sites. These moved beyond the model of having content and HTML tags live in a simple HTML page which your browser accessed and displayed. Instead, these systems were Web applications – software that literally runs on the Web server and makes it possible to manage a Web site, often with very sophisticated features. One feature of these applications is that they separate content and presentation by storing most content (your text, images, etc) and data about the site (the title, options, etc). in a database.

On the Web server, the Web application installs files that are written in some kind of programming language. The server reads this code and obeys any requests in it to access data in the database (which lives on a separate server) and displays it according to the instructions in the code.

example of dynamic HTML code

Essentially, the data for the site (living in a series of tables in a database on the database server) is entirely separate from the actual presentation of the site (living in the code of the programmed files on the Web server). Special software on both the Web server and the Database server enable the two to speak to each other and work together.

One of the benefits of using a Web application is that you usually don’t need to touch (or even look at!) the code in order to make changes to your content. In addition, editing the site usually involves accessing some kind of control panel through your Web browser and filling out a form, instead of having to download and access files in software on your own computer.

Dynamic vs Static Content

Sometimes when we talk about the difference between dynamic and static content we get bogged down in the idea of whether or not the content is “fresh” (dynamic, regularly updated) or “old” (static, never updated). How frequently you update your content has nothing to do with what kind of system you are using to manage your site. You can manage a static Web site (as described above) and update the content every day. You can also have a dynamic Web site (running something like WordPress) and never change the content after you create it.

Generally speaking, it is easier to regularly update content on a dynamic Web site because the Web application just makes it easier. Sometimes, even when you just want a very basic page or placeholder, it’s easier to install a Web application (and only put up a single page) then to manually create an HTML page and upload it.

A Side Note about Separating Content from Presentation: Style Sheets

Another aspect of separating content from presentation involves the use of 'Cascading Style Sheets' (CSS). These are special files that live on your Web server and are linked to your Web pages. They contain information (written in a special markup language) about how to make elements on your site look. For example, they allow you to define in a single location what all Level 1 Headings look like on your site. They are an important aspect of understanding how to separate content from presentation, but they’re not really an aspect of the difference between static and dynamic sites. Both static and dynamic sites can use style sheets.

Publishing Content

The primary activity that you’re likely to be doing on your WordPress site is publishing content. The content could be the text you write, pictures you take, videos or audios (which may be hosted on another site), or other media that you’ve found elsewhere on the Web. WordPress makes it very easy to publish media content of all types, whether hosted on your actual Web server or elsewhere.

Posts vs. Pages

Out of the box, WordPress provides two primary content types for you two work with: posts and pages. If you read blogs or have ever written for a blog before, the concept of a post is probably a bit familiar. Posts often are content that appear on your blog in some kind of scheduled way. They usually are presented on your site in reverse-chronological order. Posts might be what you use to share your regular thoughts, reflections, or ideas about a topic. Posts make up a kind of “river” of content that you’re producing as part of your blogging activity.

Pages usually correspond to our more traditional concept of what makes up a Web site. Pages are presented outside of the “river” of content that are posts. They are more likely to stand alone and be organized according to a traditional hierarchy. Pages might be content that is less frequently updated or changed.

If you were using WordPress to build a business Web site with a lot of information content, you would probably use Pages. If you added a feature to that site where you started to advertise special events or news, you would probably use Posts.

A few other things to know about Pages vs Posts:

  • If you want your content to be accessible to your users via RSS/syndication, you’ll need to use Posts. By default, Pages do not appear in a site’s RSS feed.
  • Categories and Tags (which are used in WordPress to help you organize your content) are ONLY available on Posts. Page organization is done by customizing your site’s menus.
  • Okay, this get’s a little tricky: WordPress, by default, also creates “Category Pages” and “Tag Pages” that display all the Posts in a category or tag. These are NOT related to the regular Page type.

Media

Upon occasion, you may want to include media (images, audio, video) in your site’s posts and pages. There are generally two approaches to handling media in WordPress:

Uploading: You can upload the files to your site’s Media Gallery and then link to them in your posts/pages. This works very well for images, and when you take this approach for images you have the added benefit of being able to make use of WordPress’ built-in (albeit rudimentary) editing tools. Also, when you upload images to WordPress, it automatically creates different sizes that you can use, as needed. This approach works less well for audio and video. In order to have your media files actually show up in a “player” (with controls for stopping, pausing, etc.) you’ll need to install a plugin. Otherwise, you’ll only be able to include links to the files. How people view/listen to them will depend a bit on the setup on their own computer and in their own browser. They may, for example, have to download the media file and then open it in another program on their computer.

Embedding: You can embed media from other sites easily in WordPress. Embedding an image just means providing a URL to its location elsewhere on the Web. Instead of uploading it to the server, WordPress grabs that image from the external source and displays it on your post/page. However, with this approach, you lose your editing capabilities as well as the resizing feature. Embedding audio and video from external sources becomes easier with every version of WordPress it seems. These days, you can embed video and audio from many external services (YouTube, Vimeo, SoundCloud, complete list here) by simply placing the full URL of the audio/video location on its own line in your post/page. There is a complete list of supported external services, and you can learn more about embedding from external sources at the WordPress site. Our general advice is to use externally hosted media whenever it makes sense and works. This is usually the case when you need to use audio or video; without plugins, well-presented audio and video in WordPress is tricky. For images, if you need to do basic editing and/or require different sizes of images, upload them to your site. Otherwise, consider referencing them from another location (your Flickr account, for example).

Post Formats

Recent versions of WordPress have built out a new “post format” feature which, if you are using a theme with the feature enabled, will style post formats differently depending on what they are. The formats that are built-in to WordPress (and are available for theme developers to use) are the following:

  • aside – Similar to a Facebook note update.
  • gallery – A gallery of images.
  • link – A link to another site.
  • image – A single image.
  • quote – A quotation.
  • status – A short status update, similar to a Twitter status update.
  • video – A single video.
  • audio – An audio file.
  • chat – A chat transcript.

Those of you familiar with Tumblr may recognize this approach to post formats.

For the most part, post formats are designed as a way to style a site (and customize styling depending on the kind of content that is being displayed). They have no special functionality, and their use depends entirely upon the theme you are using. Many older themes, for example, do not recognize post formats.

Managing Permissions

The default Mediawiki installed has been customized to make it a bit harder for spammers to overwhelm wikis with illegitimate content and comments. This is done by modifying the LocalSettings.php file (a file that is included in every install in which it is possible to provide configurations details).

By default, Mediawiki allows anonymous users to create pages and edit pages in the wiki. The modifications change this in the following ways:

  • Anonymous users cannot edit existing pages
  • Anonymous users cannot create pages
  • Registered users must click the confirmation link in the registration email in order to edit or create pages

This approach should drastically reduce unsolicited content and comments on Mediawiki installations. One further step that administrator might take is to turn registration off after a predetermined amount of time. Users must create accounts by this date; after that, the settings are changed so that registrations are no longer open.

To add this setting, you must edit LocalSettings.php in your Mediawiki install:

  1. Login to cPanel and browse to your File Manager.
  2. In the File Manager, browse to the folder within public_html that contains your Mediawiki install. If you installed the wiki at the root of your domain, you won’t need to go any further than public_html. If you installed the wiki in a subdomain or subdirectory, you’ll need to find the directory that is associated with that space.
  3. Locate LocalSettings.php. Once selecting the file, click download in the top menu bar to download the file as a backup before proceeding. Then click Edit in the top menu bar to edit the file.
  4.  Confirm that you want to edit the file.
    Confirm that you want to edit the file
  5. Browse to the bottom of the document, and locate the custom settings that were added during the Mediawiki install and the following line:
$wgGroupPermissions['*']['createaccount'] = false;

What is DNS?

Remember back before everyone had computers that fit in their pocket, how companies would ship a book full of phone numbers to your doorstep? We might have known who we were looking for, but we needed to look up phone numbers unless they were your crazy relatives that you learned to memorize. When you get your own domain name, by default it’s nothing more than a shortcut, an address, or (to fit this very imperfect analogy) a phone number. When you type a domain name into the address bar of your browser, someone has to identify it and tell it what to display. That’s where a name server comes in.

A name server is a computer, running as a server, that keeps a record of all the domain names that are associated with it and keeps track of where those domains should go. In the case of digitalscholar.rochester.edu, the nameserver is the same computer that runs the hosting. You can peek under the hood and see this in action by going to the Websites and Domains tab of your cPanel account and clicking on DNS Settings. DNS stands for Domain Name System and the name server on digitalscholar.rochester.edu gives control to it to identify what should be displayed when someone types in your domain. Consider the fact that you might have one or more subdomains in your account. The name server and DNS are able to identify those subdomains and let the world wide web know that they exist and point to some files/folders on a computer somewhere.

When you signed up for a domain through the digitalscholar.rochester.edu system your nameservers were chosen for you. So when people type in your address, the server responds with information about your account. When you migrate an account away from one hosting platform like digitalscholar.rochester.edu and onto a new service, it will require you to change the nameservers so that your domain name points to a new server with its own files and structure. It’s also possible to have subdomains that point to entirely different servers than digitalscholar.rochester.edu. For example, you could have a subdomain that looks to Tumblr for files.

What Exactly is a Web Application?

In the most general terms, a Web application is a piece of software that runs on a Web server. A Web server is a just a specialized computer designed to host Web pages.

Most Web applications are comprised of two components: files and a database. When you install a Web application, you will need to make sure all of the files are copied over into the appropriate location AND that a database (and database user) has been set up to connect to those files. Often, you will have to do some configuration to make sure the application knows how to access the database.

The system we use for University of Rochester uses a special script installer called Installatron (in cPanel) that allows you to automatically install dozens of open source applications. When you use Installatron, you don’t need to worry about moving files, creating databases, or doing the initial configuration. It’s all taken care of for you.

In order to run on the University of Rochester server, Web applications must be able to run on a LAMP server, which is the particular kind of Web server that we use. Occasionally, a Web application may require additional components or modules that need to be installed on the server.

Reading Settings – Front Page

WordPress is a very flexible platform for creating full-blown websites, not just blogging sites. This page will show you how to change the “front page” of your website.

As we have said before, WordPress provides two primary content types for you two work with: posts and pages. Posts, as in blog posts, are a somewhat complex form of a webpage. Each blog post gets published in reverse chronological order, on the front page of a WordPress site. You write a new post, and it gets published at the top of the front page. Pages are a more static form of content. They are additional areas to put information that doesn’t change much. So what if you would like to make the front page of your WordPress site based on a page instead of your blog posts?

  1. Start at the Dashboard.Screen shot of WordPress Dashboard
  2. Navigate to Settings > Reading.screen shot of WordPress reading settings
  3. Normally, the front page displays your latest blog posts. What we want to do instead is select a Page from the website. Obviously, this page has to exist before you can select it. Select the “A static page” radio button and choose the About page from the Front page drop-down menu (an About page was created for you when you installed WordPress). Press the Save Changes button and now you will have the “About” page as your Front page. Edit it as you see fit and provide a good welcoming page for your visitors. screen shot of Word press reading settings
  4. But wait. What will happen to your blog posts? Most people will want them as the “dynamic” part of your site. First, create a new Page.screen shot of
  5. Title it Blog (you can title it whatever you want but Blog is common and descriptive). Leave the page blank (don’t type any text in the edit box) and Publish it.screen shot of adding a new post
  6. Now go back to Settings > Reading. Under the static page area choose Blog from the Posts page drop-down.select new WP post page
  7. Click the Save Changes button. Now your “home” page will actually display the About page. You will also have a Blog item in your menu (depending on your theme, you may have to customize your page display to see pages).
  8. If you click on the Blog menu item, you will then see your blog posts. Notice the /blog added to the web address.

Installing Mediawiki

  1. To get started you’ll need to login to your control panel (https://digitalscholar.rochester.edu/dashboard) using your University of Rochester username and password.
  2. Once logged in you’ll be at the homepage of your control panel. Navigate the Applications section of the cPanel and click All Applications.
  3. Find and select MediaWiki.
  4. The next page gives you more information about the MediaWiki software. To begin the install, click install this application in the upper-righthand corner.
  5. On the next page, the installer will ask for some information about this install. The first thing you’ll want to do is decide where to install it. If you’re wanting to install MediaWiki on your main (the root) domain, you can leave the directory area empty. If you created a subdomain, you can select it from the drop-down menu. You also have the option of installing MediaWiki in a subfolder by typing in the folder name in the Directory field. Click here for more information about subdomains and subfolders.

    (By default the installer will automatically backup your MediaWiki website and update it anytime a new version comes out. While we recommend you keep this option, it is possible to only do minor updates, or turn them off completely. The installer will also create a database for you automatically, but if you’ve already created one for this website you can choose Let me manage the database settings and enter the details.)
  6. Finally, you’ll need to create an initial username and password for the MediaWiki install. Enter those credentials in the Settings section and click Install.
  7. The installer will take just a few moments to install MediaWiki and a progress bar will keep you updated. When it is complete you will see a link to your new MediaWiki site as well as a link to the back-end administrative section for your MediaWiki site.

Congratulations, you have now completed the installation of MediaWiki! You can now start to create collaborative documents on your own domain.