You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2025-04-29-mgs6123-campuspulse-access.md
+10-53Lines changed: 10 additions & 53 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,69 +9,26 @@ categories:
9
9
- Contribution
10
10
11
11
# Enter your name below
12
-
author: Adrian Edwards
12
+
author: Michael Shortell
13
13
---
14
14
15
-
For my contribution, I decided to create this website and post this sample blog post. I decided to do this because I wanted to help provide a blogging platform for SJ to allow the students of HFOSS to have a place to submit their blog posts for the last half of the semester.
15
+
For my contribution, I decided to update the content of the CampusPulse Access 'About' page.
16
16
17
-
This blog post can be used in several ways:
18
-
- Reading it should provide a tutorial explaining some of the basics of howto use this blog for HFOSS students who will be adding posts to it
19
-
- Looking at its source code can provide a template that can be reused to help kickstart the writing of new blog posts, or to demonstrate some examples of how to use markdown
20
-
<!-- - Demonstrate (to some extent) what a well-written, detailed blog post looks like. (That said this post will probably be longer than is expected for the actual HFOSS assignments because it may contain a lot of tutorial content) -->
21
-
- As documentation for any future readers who are interested in the rationale behind the existence of this site (such as Future HFOSS students, TA's, or FOSSRIT org admins)
17
+
## What is CampusPulse access?
18
+
CampusPulse access is a project with the goals of making it easier to report problems with accessability-related "access points" around campus (notably elveators, wheelchair lifts, automatic doors, etc.), avoid broken access points, and keep up-to-date with the status of access points. Of course, if you want to learn more, I'd reccomend checking out the [About page](https://access.campuspulse.app/about) itself. The actual site itself was forked from the [TunnelVision](https://github.com/wilsonmcdade/tunnelvision) site.
22
19
23
-
## What is this site?
24
-
This is a site that is built using Jekyll. A tool that allows you to build websites that is natively supported by [GitHub pages](https://docs.github.com/en/pages) - a free website hosting service provided by GitHub. It is quite commonly used by developers to create their own personal or portfolio websites.
20
+
## How did I get involved?
21
+
Well, my original plan was to work on an open-source CSH project (Devcade). Specifically, the plan was to work on the onboard. However, we ultimately decided to redo the whole thing, which couldn't have had substantial progress done before the deadline. So, instead, I simply asked Adrian Edwards if there was an open source project on campus that I had enough skill to contribute to. Thus, I was added to the CampusPulse Discord. From then, I was informed about the out-of-date 'About' page. It was still identical to the [TunnelVision About Page](https://tunnelvision.csh.rit.edu/about).
25
22
26
-
## Why not something else, like WordPress?
27
-
HFOSS is a class designed to help teach some of the basics behind open source. By using git and GitHub to submit the blog posts, there are more opportunities to practice using the tools that are used by real-world projects. Additionally, the WordPress sites from previous classes are no longer around and are hard to point to as examples that are particularly positive or negative
23
+
## Actually working on the page
24
+
I came into the project knowing HTML and CSS. Most of the content was already written in a Google Doc, so it mostly just needed minor edits to fit it onto the page. Something I didn't know before working on this was Bootstrap. While I'd heard of it before, I didn't know how to use it, much less what it actually was. After some work and two group meetings, the page was completed.
28
25
29
-
## How do I use it?
30
-
This repository may look like a mess of many, many files, but realistically the only files you will likelyc are about as an HFOSS student are in the `_posts` folder. This is where you will upload your blog posts. The basic process goes something like this:
31
-
32
-
1. Log into your GitHub account
33
-
2. Create a fork of this repository and clone it to your computer if that's how you prefer to work (feel free to try a few different ways)
34
-
3. Create a new branch on your fork starting from the `main` branch
35
-
4. Find the `_posts` folder and create a copy of this sample post, giving it a new, dated filename (Jekyll requires blog post files to be named according to the following format `YEAR-MONTH-DAY-title`) and changing the contents accordingly (ideally making commits and pushing to your new branch as you go)
36
-
-[Optional] If you wish, you can also
37
-
5.[Optional] You can also configure github pages (through the settings tab of your forked repository) to host a website site based on your new branch, so you can preview your changes and make sure your post looks the way you want. There are also ways to assemble the website on your computer if you prefer a more hands-on process (Ask in class or come to office hours if you want to learn more about this!)
38
-
6. When you are ready to submit, create a "pull request" back to the original repository. This will take the contents of your new branch and submit it as a proposed change to the main class website. Once approved, your blog post will be added to the main class web page.
39
-
7.[Recommended] Whenever the main class webpage updates, it may be helpful to also update the main branch of your fork (github provides a handy "sync" button) so that you can stay up to date
40
-
41
-
42
-
43
-
## More Markdown features
44
-
In addition to the formatting used so far in this document, Markdown offers several other things that may be useful to blog posts.
26
+
## Pull requests
27
+
The first pull request was just a simple edit to remove a reference to the TunnelVision murals that
45
28
46
29
### Images
47
30
48
31

49
32
50
33
51
-
[Here](https://www.markdownguide.org/basic-syntax/#images-1) is a link to more documentation on markdown images.
52
-
53
-
### Tables
54
-
55
-
| Item | Price | # In stock |
56
-
| ------------ | -------- | ---------- |
57
-
| Juicy Apples | 1.99 |*7*|
58
-
| Bananas |**1.89**| 5234 |
59
-
60
-
[Here](https://www.markdownguide.org/extended-syntax/#tables) is a link to more documentation on markdown tables.
61
-
62
-
## More Jekyll Features
63
-
Jekyll can also provide some formatting and other useful features. Check out the [Jekyll docs][jekyll-docs] for more info on how to get the most out of Jekyll. Here are some notable examples:
0 commit comments