Neatline

Building an interactive map using Omeka’s Neatline plugin

Neatline is a plugin for Omeka that allows for the creation of interactive maps and timelines. Neatline allows the user to plot points on geospatial layers that, when clicked, reveal text and media. Users may create records from scratch and add them to their Neatline exhibits, or import existing items from Omeka. See Neatline.org for demos of this tool in action and more documentation.

Before using this tool, you will need to:

1) Install Omeka (see “Installing Omeka”).

2) Install the Neatline plugin to your Omeka site (see the “Installing Plugins” section of the “Installing Omeka” guide).


Contents

Some vocabulary

Setting up (first time only)

Creating Collections and Items in Omeka

Managing your Neatline exhibits in Omeka

Linking your maps to your Omeka home page


Some vocabulary

Item: Omeka’s basic building block, containing text, media, and/or metadata.
Collection: A group of items, typically sharing a common theme.
Record: Neatline’s version of items. Can be created on their own, or imported from an existing item in Omeka.
Exhibit: A Neatline map or timeline; contains your records.
Widget: An add-on tool for Neatline, such as Waypoints.
Spatial layer: A navigable map that Neatline can use, typically pulled from Google Maps. The various options Neatline offers have different aesthetics.

Setting up (first time only)

1. Install the Neatline plugin (see above). Install any additional supporting plugins you’d like, such as Neatline Waypoints.

2. Go to your Plugins page in Omeka. Then, click “Configure” to the right of Neatline. On the configuration page, click the link to developers.google.com/maps/web. If possible, open this link in a new tab, since you’ll soon need to return to the configuration page.

3. On the Google page that opens, click the “GET A KEY” button at top right. Follow the prompts in the pop-up window to create a new project, named whatever you’d like (this title won’t matter for your Neatline projects). When you’re given a long string of characters, copy it. This is your Google Maps API Key. You’ll only need it once.

4. Return to the Neatline configuration page from step 2. Paste your API Key into the text box. Then click the green “Save Changes” button. Neatline is now connected to Google Maps.

5. Click Settings at top right of your Omeka dashboard. In the text box to the right of “ImageMagick Directory Path,” enter this exact text without the quotation marks: “/usr/bin”. Then click the green Save Changes button at top right. This will allow Omeka to handle your images properly.

Neatline is now ready to go!

Creating Collections and Items in Omeka

1. Optional: create one or more collections. This is an organizational tool: by creating collections now, you’ll be able to sort your items or bulk import them to Neatline more easily later. To create a collection, click “Collections” on your lefthand Omeka dashboard menu. Then, click the green Add a Collection button. On the Add a Collection page, give your collection a Title (you can leave all other boxes blank). If you want to add formatting to your text such as bolding or italics, check the box next to “Use HTML,” and more editing options will appear.

When you’re done, check the box next to “Public” and then click the green Add Collection button.

NOTE: You’ll see many fields when creating collections or items, but there’s no need to panic: almost all are optional and exist for archival purposes. Only fields with a * after them are required.

2. Begin creating items. Omeka is a tool for curating artifacts. In this step, you’ll begin this curation by creating items. To create an item, click “Items” on your lefthand Omeka dashboard menu. Then, click the green Add an Item button. On the Add an Item page, give your item a Title and a Description (you can leave all other boxes blank). This is the text that will ultimately appear to viewers of this record on your Neatline map. If you want to add formatting to your text such as bolding or italics, check the box next to “Use HTML,” and more editing options will appear.

Check the box next to “Public.” If you wish to add this item to a collection, select it from the dropdown menu under “Collection.”

If you wish to add images to your item, click the “Files” tab, then click “Choose File.” Follow the prompts to upload an image. To upload more images, click the green Add Another File button. These images will be displayed alongside your text when a viewer clicks the relevant point on your map.

If you wish to add tags to your item, click the “Tags” tab, then enter all desired tags in the text box, separated by commas. Remember to click Add Tag afterward.

When you’re done adding text, files, and tags, click the green Add Item (or Save Changes if you’re editing) button.

You can always find your list of items, with the option to edit each one, by clicking Items on your Omeka dashboard. From the Items page, you can also use the blue Search Items button to filter items by user or tag.

Clicking “Tags” on the Omeka dashboard will bring you to a list of all your tags. Click a tag’s name to edit it, or click the number to its left to view all items with that tag.

Managing your Neatline exhibits in Omeka

1. Create an exhibit. Your Neatline map will be known as an exhibit. It’s now time to create this map. Click Neatline on the lefthand dashboard menu, which brings you to the Browse Exhibits page. Then click the green Create an Exhibit button.

On the Create an Exhibit page: give your exhibit a Title, Narrative (optional but recommended), and Widgets (if you’d like to use Waypoints or another add-on you’ve previously installed). The Narrative is the exhibit’s primary textual description, and it will appear alongside your map.

Scroll down and select a Default Spatial Layer from the dropdown menu. The Default Spatial Layer is the default map style your exhibit will display. You can edit this any time, so try out a few and see which aesthetic you like best. You can also optionally use the Embed Spatial Layers field to allow your viewers to toggle between various map styles.

The only other setting you need to change here (eventually) is Public: when you check this box, your exhibit will be live. When you’re done, click the green Save Exhibit button at the bottom of the form.

2. Access the Neatline editor. Return to the Browse Exhibits page from step 1. To access the editor, click your exhibit’s title. Clicking Public View or Fullscreen View will let you preview how your exhibit will look to visitors.

Here is what the editor looks like. Notice the Records, Styles, and Plugins tabs, and the list of records below the blue New Record button (there won’t be any records until you add some):

3. Set the default focus. This is the latitude/longitude and zoom that viewers will see when they first open your map (they’ll then be able to move it however they’d like). In the editor, click the Styles tab. Click and drag on your map to move it around, and use the + and – symbols at top left to zoom in and out. When you’re satisfied with the current view of the map, click the Use Current Viewport as Default button. This will automatically fill-in coordinates and the depth of zoom. You can also manually add these. When you’re done, click the blue Save button.

4. Import items into your exhibit, which then become records. First, click the Records tab in the editor. Then, click the large blue New Record button.

New tabs will appear. Click the Item tab. You’ll see a dropdown menu called “Search Omeka items.” This will list all the Omeka items you’ve previously created. Find the item you wish to add to the map, and select it. The item’s content appears below the dropdown menu. If it looks correct, click the blue Save button. If not, click “View the item in Omeka,” edit the item, and try again.

NOTE: If you edit an item in Omeka that you’ve already imported into your Neatline exhibit, its record in the exhibit will be automatically updated.

NOTE #2: You can also create records from scratch using the New Record button and the Text tab (without making an Omeka item first). However, this isn’t recommended if you wish to include images or other media in your record, since that media would require additional HTML formatting.

5. Pin your records to the map. You can access any of your records from the list of records on the editor’s main page (see the screenshot in step 2 of this section, looking under the New Record button). Once you’re in a record, you can place it on the map. If you’ve just created a record using the Item tab from the previous step, then you’re already in that record.

Once in the record, click the Map tab. You can draw many different shapes here (and feel free to experiment!), but for our purposes, we’ll look at two buttons: “Navigate” and “Draw Point.”

When “Navigate” is selected, you can move your map around without adding anything. When “Draw Point” is selected, you can click on the map to place a blue pin. When a viewer clicks this pin, she’ll see the record associated with it. When you’re done, click Save.

For example: I have a record containing text and images about Shakespeare’s first performance of Henry V in London. I can go into my Henry V record and use “Draw Point” to place a pin on London. Now, the viewer can click the blue dot on London to bring up this record.

Optionally, you can use the Style tab in a record (to the right of the Map tab) to change the appearance of points and shapes for that record.

You can add as many interactive points or shapes as you’d like to your map.

6. Add widgets to your record (optional). If you’re using the Waypoints widget, select it by clicking in the Widgets field. See the next step for more information about Waypoints.

When you’re done, click Save. Then, you can exit out of the record and back to the editor’s main page by clicking the X above the Style tab. You can return to Omeka by clicking “Return to Omeka.”

7. Adding Waypoints: a table of contents for your map. The following guide from Neatline.org explains how to add a list of clickable records to your map, so viewers can jump from point to point without searching the map for them:
http://docs.neatline.org/working-with-the-waypoints-plugin.html

Linking your maps to your Omeka home page

1. Choose what links you’d like to display on your home page’s navigation menu. This menu may appear in a slightly different place on your home page depending on your theme. Here’s what it looks like in one of Omeka’s built-in themes (“Thanks, Roy”):

To edit this menu: from your Omeka dashboard, click Appearance in the black bar at the top of the screen. Then click the Navigation tab.

This takes you to a checklist of links. Each checked link will appear on your home page’s menu. To edit a link’s label (name) or URL, click the small black arrow to its right.

To add a new link: fill in the Label and URL fields at the bottom of this page, and then click Add Link. You can reorder the menu by clicking and dragging the links. When you’re done, click the green Save Changes button.

By default, there will be a link called “Neatline” which takes your viewer to a list of your Neatline exhibits. This is called the Browse Exhibits page, and looks like this:

If you’d rather have links on your menu to one or more specific exhibits, first pull up that exhibit’s public or full screen view (see the screenshot for step 2 under Managing Neatline exhibits and using the editor above). Copy the URL from the address bar at the top of your browser. Paste it into the URL field on Appearance > Navigation, give it a label, click Add Link, and then Save Changes.

2. OR, choose a different default home page.

To use a list of your Neatline exhibits as your home page:
On Appearance > Navigation, click on the dropdown menu under “Select a Homepage” (to the right of the link checklist). Select “Neatline” (or whatever you’ve renamed it). Click Save Changes to finish.

To use a specific exhibit as your home page (taking your viewer directly to the map):
On Appearance > Navigation, add a link to the public or fullscreen view of the map you wish to be the homepage (see the previous step). Then, click on the dropdown menu under “Select a Homepage” (to the right of the link checklist). Select the link you’ve just added. Click Save Changes to finish.

Now you can share your Omeka site’s address with whomever you’d like, and they’ll be able to explore your interactive map!

Cloning applications to a new subdomain/subdirectory

The domain name that you choose during sign up will stay with you through all of your current and future build projects. This is why we recommend choosing a general and enduring name, such as a variation of your name. However, while working on your site, you might find that the name you chose doesn’t adequately describe your project anymore. In this instance, it is possible to clone your application to a subdomain or a subdirectory of your site that has a more desirable name.

If you want to clone your site to a subdirectory (so, the URL would change from something like YOURNAME.emerson.build to YOURNAME.emerson.build/project), you can create that directory during the cloning process. To clone to a subdomain (which would change the URL from YOURNAME.emerson.build to project.YOURNAME.emerson.build), the subdomain needs to be set up ahead of time.

Once you’re ready, head to the “My Apps”/”My Applications” area from your cPanel Dashboard.

  1. To the right of the name of the app you want to clone is a row of buttons, the “clone” button looks like a forked arrow. Click it.
    Single application row in the cPanel with Clone button marked
  2. On the “Clone” screen, verify that the correct information appears in the “Source” box. Under “Destination”, choose a previously created domain or enter a subdirectory name in the “Directory” field.
    • You will see the URL and file path for the cloned site listed below these fields.
  3. The other settings can be left as their defaults to automatically create and copy databases and settings.
  4. Click the “Clone” button at the bottom of the form. Depending on the size of your application, this may take some time to complete. A progress bar will keep you updated.
  5. After verifying that the cloned site works as expected, you can delete the original.

Tip: Cloning your application can also be used to test new themes and plugins without affecting your published content.

Managing Backups

Any application that you install in Emerson.build using the cPanel/Installatron is set to automatically create a backup of the whole app every time the software updates. The backups expire after 14 days, but they can quickly eat up quota space in that time, especially since some apps (such as WordPress) update automatically. Follow the steps in each section below to take more control over the space that backups use in your account.

1. Turn off the automatic Installatron backup

  • Go to your cPanel
  • Go to Applications > WordPress > My Applications.
  • From there, select the wrench next to your site’s name.
  • Scroll down to Automatic Update Backup and set that to “Do not create a backup”​​

Application Backups screen with an arrow pointing to "Do not create a backup" under "Automatic Update Backup"

2. View restore points in JetBackup App

The JetBackup app can be found in the “Files” section of your cPanel dashboard.

Files section of the build Dashboard with JetBackup location circled

This app should already be active so there are no additional steps you need to take to set it up. JetBackup automatically creates full backups and individual backups of your site’s files and databases nightly. More information on how to navigate and use the app to restore your site is available in this post on the Reclaim Hosting Community site: “Restoring Backups Using JetBackup” (opens an external site in a new tab).

 

3. Create a manual Installatron backup before major changes

While JetBackup creates daily backups of all of your content, it’s best practice to have a backup of your application from right before you start tinkering, just in case anything goes wrong. That way you won’t lose any content that’s been added or changed since the latest daily backup. As a bonus, backups created through the Installatron are easy to restore with a single click. These manual backups can even be sent to an offsite location like Dropbox to save space.

To create a manual backup:

  • From your cPanel, click “My Apps” in the “Applications” section.
  • Click the checkbox to the far right of the application name (labeled 1 in the screenshot below).
  • Click “Backup” below the bottom of the application list (labeled 2 in the screenshot below).
  • On the next screen, enter a descriptive label and click Backup again. The backup will run with a status bar.​

Installatron "My Applications" screen. The checkbox to the far right of the application's name is labeled "1" and the "Backup" button underneath the app row is labeled "2"

 

4. Delete Installatron backups that are no longer needed

If you’ve created a manual backup or are running out of space due to the automatic backups, you should delete old Installatron backups to free up space.

  • From your cPanel, click “My Apps” in the “Applications” section.
  • Between “My Applications” and “Applications Browser”, you’ll see a “My Backups” tab. Click that to see the list of current backups.
  • Click the “X” to the right of an individual backup or check the box to the right of multiple backups, then Delete at the bottom.
    Installatron's page listing available backups with the "X" to remove one circled
  •  On the next screen, you’ll see a summary of the backup(s) to be deleted. Click “Delete” to confirm.
    The confirmation screen after clicking Delete the first time. The Delete button here is circled.

When You Leave

You retain access to your Emerson.build domain for one year after you graduate or leave Emerson. After one year, you will lose access to your Emerson account and your domain along with it. To retain ownership of your domain, you have several options: pay Reclaim Hosting a small yearly fee to keep everything; download your entire site to store on your computer; or move everything over to another hosting provider.

Using Reclaim Hosting

Emerson.build is hosted through Reclaim Hosting. Through our partnership with them, you’re eligible to have your domain and content automatically migrated to a full hosting account at a 20% discount. Follow the instructions below, and Reclaim Hosting will complete your migration for you. You won’t have to provide any login information since they control the servers on both sides.

To sign up for your own Reclaim Hosting domain:

1. Log-in to Emerson.build.

2. Hover your mouse over Manage Your Account in the top navigation menu, and click on Migration Information in the dropdown menu.

Find the Migration Information button under Manage Your Account at the top dashboard of the cPanel.

3. Click on Get Started in the Migration Offer box.

Clicking "Migration Information" takes you to a Migration Offer from Reclaim Hosting, where you can click "Get Started."

4. You will be given the option to 1) register a new domain, 2) transfer your domain from another registrar, or 3) use your existing domain and update your nameservers.

Reclaim Hosting's options for migrating from Emerson.build.

If your site’s URL ends in Emerson.build, and you have never used a different URL or purchased hosting from somewhere else, the Register a new domain option allows you to get your own personal domain with Reclaim Hosting (outside of Emerson.build). Your site will no longer be located at “yoursite.emerson.build,” and you’ll be able to purchase a new URL.

If you have purchased (or intend to purchase) a URL from a different hosting company, but still want your site to be hosted with Reclaim Hosting, select the I will use my existing domain and update my nameservers option. Your site will be migrated to a personal Reclaim Hosting account, but then you will have to update the information that tells the other hosting company (that you got your URL from) where your site is located. It’s possible to get your hosting and URL from two separate companies, but it’s often easier and cheaper to get them together.

If you already have a site that’s hosted somewhere else, and want to transfer everything to a personal Reclaim Hosting account, select Transfer your domain from another registrar.

Other Hosting Providers

If you don’t want to continue with Reclaim and would rather use a different hosting company, you can download all your site files independently, purchase a URL, and upload the files to your new domain through FTP.

Signing up on Emerson.build

Reviewing the Guidelines

Before you get started, we recommend that you review our information about Choosing a Domain Name.

Please note: Emerson College branding should not be used in any content that you create on Emerson.build. Emerson.build should not be used to publish content that in any way reflects an official position of Emerson College, its departments, organizations, etc. This tool is intended for curricular, personal, and experimental sites only. To learn about options for creating an officially branded website, please contact Web Services (web@emerson.edu).

 

The Sign-Up Process

Once you’ve reviewed the guidelines, you can proceed to the sign-up page.

Click on the top, right hand side where it says Dashboard.

Emerson.build homepage with menu item "Dashboard" circled.

You will be redirected to login for verification. You will use your Emerson username and password to login.

Emerson.build login form via Duo

Create a Free Subdomain

If this is your first time accessing Emerson.build, you’ll be asked to create your free subdomain. Enter in the domain name you want for your website. (*Note: your domain will look like name.emerson.build. ) When you’ve found an available subdomain, click the button labeled Click to Continue.

The Emerson.build registration screen, with a text box.

You will be taken to a screen where you can confirm the domain you’ve chosen and review your contact information. If you’re ready to confirm, click Register Now. Otherwise, you can Start Over or contact us for help with the sign up process.

The Review and Checkout screen, with a button to Start Over or Register Now.

After you click “Register Now,” you will be brought to the cPanel and are on your way to creating your own Emerson.build space!

Choosing your domain name

Choosing your domain name is the first step in getting started with staking your claim on the web. Your domain name is really just a unique Web address that can be used to build out your own digital presence. When you sign up for Emerson.build, your domain name will, by default, be a subdomain of the form “YOURNAME.emerson.build”. Not all of the considerations below will apply while choosing this first subdomain name. If you later choose to purchase your own custom domain name, all of the following are good to keep in mind.

Your Domain Name Must Be Available: Domain names must be unique, which means in order for you to claim your own, you need to be sure that it is currently available (and not being used by any one else or any company or organization). There are lots of tools to check on domain availability, and when you sign up on emerson.build, we’ll actually check the availability of your choice for you. If you’d like to spend some time thinking about your choice and checking availability before you actually sign-up, we recommend using whois.net.

You Must Choose a “Top Level Domain” or TLD: The TLD is the suffix (or ending part) of your domain name. Some common ones you’ve likely seen before are: .com, .net, .org., and .edu. On emerson.build, you won’t have an opportunity to change this when you first sign up. For custom domain names, you may choose which one you want to use. Note that the availability of your desired domain name may depend upon the TLD you choose. Historically, .com domains were meant for businesses and commercial entities. On the other hand, .org domains were usually used by non-profit organizations. The .net domain was meant to be used by internet service providers. All of that said, the “historic” uses of these TLDs mean very little anymore. You may find that .com domains are easier for people to remember, or you may like the “non-commercial” message of using a .org. The bottom line is that your choice of a TLD is entirely personal.

Choose a Domain You Can Live With: You should choose a domain name that you feel you can live with for quite some time. You should pick something that you won’t find embarrassing in the future. A good rule of thumb is to pick a domain that you would be comfortable putting on a future job application.

You May Wish to Include Your Name in Your Domain: There is no requirement that your domain reflect your specific identity in the form of your first and last name. However, choosing a domain name that includes your name may make it easier for you to achieve higher rankings in search engines when someone queries your real name.

Pick a Domain you Like: At the end of the day, your domain should reflect you. Pick a domain you like and are proud of. It can reflect your interests, sports you play, or your hobby. Or it could just be your name. The “right” domain for you is the one you’re comfortable with.

Using a Custom Domain Name

Emerson.build currently utilizes subdomains of .emerson.build for the initial signup, however after using your space you may decide you’d like to register a top-level domain. This is typically a .com, .net, .org address, though other options are available. You can do this by registering a domain with a service provider and adding it to your space as an Addon Domain.

To start you’ll need to get the domain registered. When choosing a domain we recommend keeping it all lower-case, avoiding hyphens, keeping it short, and of course it will need to be a unique address. You’ll also need to choose a service provider to register your domain with. Different providers offer different pricing models and features, so it’s a good idea to do some research about your options before you make a choice.

After ensuring the domain is available for purchase you might be prompted to select whether you’d like to protect the contact information associated with the domain. All domain registrations are required to have valid contact information publicly available worldwide, however a proxy service to protect your identity is available for an additional fee. You can read more about this service, ID Protect, at http://docs.reclaimhosting.com/FAQ/ID-Protect-FAQ/.

In most cases, you’ll also be prompted to enter nameservers for the domain. You’ll want to point the nameservers to ns1.reclaimhosting.com and ns2.reclaimhosting.com (if those aren’t already selected) in order for the domain to work with our system.

Once you’ve completed the checkout process with payment information the domain will be registered automatically. The last step is to add it to your existing account here at Emerson.build. To do that you’ll log into your account at https://emerson.build/dashboard and in cPanel navigate to Domains > Addon Domains.

The Addon Domains screen of the cPanel

Here you will type in the domain that you registered previously to host it within your space on Emerson.build. cPanel will also setup a subdomain and a location for files to be saved (typically a folder inside of public_html). You can leave these with their default values.

NOTE: Creating an addon domain always results in the creation of a brand new subdomain. The subdomain field here must have a unique name that doesn’t already exist in your site’s subdomains or you’ll encounter an error.

Optionally, you can also create an additional FTP account on this screen.

Additional fields appear when you check the "Create an FTP account" box

Once you’re finished going through the options, click Add Domain. The domain will now be hosted in your Emerson.build account and you can use it to install software, upload files, and any number of other actions available to you in cPanel.

Pointing an addon domain to an existing application

If you previously set up an application or from-scratch website before buying a custom domain name, you can still use that custom domain name for that application/site. You still need to go through the Addon Domain process above, but there are a couple differences:

Option 1: Changing “Document Root”

While filling out the fields in “Create an Addon Domain”, change the location listed under “Document Root” to the file path for your existing site. For example, if you have a WordPress site installed at an existing subdomain blog.dogs.emerson.build, you would enter “blog.dogs.emerson.build” as the Document Root. As another example, if you have HTML files hosted in public_html/games you would enter “public_html/games” as the Document Root. You will start to get suggestions of existing directories and subdomains as you type in this field.

Option 2: Cloning your existing site

If the above option doesn’t work or you’d prefer to keep the default directory for your addon domain, you can clone your application into the new directory or copy/move your HTML files into it.

Omeka

Installing Omeka

Omeka is an open-source web application that can be used to create and display online digital collections. Developed by programmers at George Mason University, Omeka was designed to be user-friendly, both during installation and daily usage. To install Omeka, follow these steps:

1. Log-in to your cPanel (https://emerson.build/dashboard) using your Emerson username and password.

2. Click Omeka in the cPanel’s Applications section.

The Omeka button in the cPanel is circled.

3. Click Install this application in the upper-righthand corner.

The Install this Application button in Installatron is circled.

4. The next page asks for some information.

First you’ll decide where to install the site, which will determine its address. If you want to install Omeka on your main directory (the same address as your domain), you can leave the directory field empty. If you’ve created a subdomain, you can select it from the dropdown menu.

Continuing down the page: under Automatic Update Backup, select “Do not create a backup.” See Managing Backups for more information about how to create backups.

Under Settings, choose your administrator username and password for the new site. Write these down and don’t share them with anyone!

Under Advanced, leave “Automatically manage advanced settings for me” checked and the installer will create a database for you (recommended). If you’ve already created a database for this website, you can choose “Let me manage these settings” and enter the details.

Click Install to continue.

5. Omeka will take a few moments to install, and a progress bar will keep you updated. When it is complete, you will see a link to the front-end of your new Omeka site as well as a link to the back-end administrative section for your Omeka site. Click the back-end link (ending in “/admin”). Write down this address: it’s where you go to edit your site.

Log-in using the administrative username and password you chose in step 4.

The link to a newly-created site's dashboard is indicated.

6. Click Settings in your Omeka site’s top admin bar. Enter an Administrator Email and a Site Title. In the “ImageMagick Directory Path” field, enter “/usr/bin“. This will allow Omeka to properly process and display images.

The Administrator Email is the address that messages from the system (e.g. a forgotten password reminder) will be sent from. You might want to create a custom email address using these instructions, for example webmaster@yourdomain.com or omeka-admin@yourdomain.com, to use for this purpose.

The Site Title will appear at the top of your visitors’ browser windows.

Congratulations! Omeka is now installed and configured. Click your site’s title at top-left to visit its front-end (the part that visitors see), or use the Dashboard (vertical menu at left) to begin adding content.

Installing Plugins

There are a variety of plugins that enable additional functionality in Omeka. See all plugins available for Omeka and their descriptions.

1. Download the desired plugin from the page linked above by clicking the Download button to its right. A zip file will download.

The Plugins page for Omeka Classic.

2. Next, go to your cPanel (https://emerson.build/dashboard). Click on File Manager.

The File Manager in cPanel is circled.

3. Go to the public_html > plugins folder by clicking the + left of the public_html folder to expand it, then clicking on the revealed Plugins folder.

NOTE: If you installed Omeka in a subdirectory, you’ll need to add the subdomain to the above path. For example, if you installed Omeka in the “archive” subdirectory, the path to the Plugins folder will be public_html > archive > plugins.

The Plugins folder is circled in the File Manager.

4. Next, you will need to upload the zip file from step 1 into the Plugins folder. Click Upload in the top menu to open a new window. Click Select File to browse your computer, or drag-and-drop the file into the window.

When the upload is complete, click “Go back to home/yourdomain/public_html/plugins” at the bottom of the page to return to the File Manager. You will see that the zip file has appeared in the Plugins folder.

The uploader in File Manager.

5. Make sure the zip file is selected (it should be highlighted in blue), then click Extract from the menu at the top of the page. A small window will open up to confirm where the file will be extracted to. If you clicked Upload from the Plugins folder, it should read public_html/plugins. Leave this field as-is. Click Extract File(s).

The path and Extract File(s) button is circled.

Another pop-up window will list the extracted contents. Click the Close button.

6. The new plugin should now be available on the Plugins page, accessible by clicking Plugins in the black admin bar at top-right of your Omeka dashboard. Find it and click the Install button to its right. Your plugin is now active.

The Plugins button in the top nav bar and the Install button next to the plugin are circled.

Note: Some plugins will create a new button on the dashboard, like so. Click on their button to use them!

A newly-added Neatline button on the dashboard is circled.

Using Omeka

You can learn how to use this application in the official Omeka Support Documentation.

Or, see the next guide to learn how to use the Neatline plugin to create interactive maps!

WordPress

WordPress is an open source content management system (CMS). It was originally released as a simple blogging platform in 2003–as a fork of b2/cafelog, for those interested in the code origin–and has grown into one of the most-used CMS on the web. As of this writing, “WordPress is used by 28.7% of all the websites, that is a content management system market share of 59.5%.” (Data provided by W3Techs “Usage Statistics and Market Share of Content Management Systems for Websites, September 2017”.)

Installing WordPress

Setting up a WordPress install on your own domain can be done by following these steps:

  1. Access your cPanel (https://emerson.build/dashboard) by logging in with your Emerson username and password.
  2. Under “Applications“, click “WordPress“.
  3. You will be taken to a page with more information about the WordPress software. To begin the install click “+ Install this Application” to the right of the application title.
    Installatron view of WordPress application and install button
  4. On the next page the installer will ask for some information about this install:
    • Under “Location”, specify where to install WordPress. * For more information about these options, visit the “Subdomains vs. Subdirectories” section of this documentation.
      • To have WordPress be what users see when they go to “yourdomain.emerson.build”, leave that as your selection under “Domain” and leave the “Directory” field blank.
      • If you’ve previously created a subdomain to use for WordPress, you can select it from the “Domain” dropdown and leave “Directory” blank.
      • You can also install WordPress in a subdirectory of your site by entering a folder name in the “Directory” field.
    • Under “Version”, we recommend to leave most of the default options, with the exception of “Automatic Update Backup”. We recommend changing this to “Do not create a backup.” You can read more about this recommendation and alternative options in the “Managing Backups” section of this documentation.
    • Under “Settings”, you will be asked to set an administrator username and password. Randomized defaults will already be entered for you, but you have the option to change these. These credentials will be different from your Emerson account, but by using your Emerson account to access your cPanel dashboard, you shouldn’t need to login separately to your WordPress blog (see “Understanding Emerson.build’s Accounts & Passwords” for information on how to recover this account info in the future). The other options under “Settings” allow you to change your site’s Title and Tagline as well as the administrator email address.
  5. When you’re happy with the settings you’ve chosen, click “+ Install” at the bottom of the page. The installer will take just a few moments to install WordPress and a progress bar will keep you updated. When it is complete you will see a link to your new WordPress site as well as a link to the backend, administrative dashboard for your WordPress site (this will end with /wp-admin/).
    "My Applications" in the Installatron link for access to the WordPress dashboard without logging in.

Congratulations, you’ve now installed WordPress! Now you can start customizing it with themes, plugins, and more.

Resources for configuring and using WordPress

Visit your WordPress site’s Dashboard by clicking the /wp-admin/ link in your “My Applications” list (From the cPanel: Applications > My Apps). This is where you will configure your WordPress site’s settings and add content. There is extensive documentation on using WordPress online. We’ll be linking to topics of interest in the WordPress.org documentation below.

First Steps with WordPress

Glossary of terms (includes advanced topics)

Settings
Appearance and Themes
Plugins
Publishing Content

The primary activity that you’re likely to be doing on your WordPress site is publishing content. The content could be 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.

Special note: 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 through 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.

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.