For this experience, you will start designing a simple Meteor application called Digits. When you are finished, the home page should look something like this (although the picture and color scheme might be different):
First, find a picture to use for the cover image. Make sure it’s at least 1000px wide. The image should have a light background, nothing too dark.
Second, I suggest you watch my screencast before trying this WOD for the first time. I have not been able to find suitable resources for you to read prior to doing this WOD to cover all the Meteor concepts I will cover. So, it’s best for you to watch the solution one time through to orient yourself. You may want to take notes if you see things you need to remember.
Third, be sure to watch my video on branching and merging in GitHub desktop. You will be required to branch and merge for this series of practice WODs.
Finally, be sure to review the chapters of the Meteor Guide listed in the Readings section. They provide a wealth of information to help you understand application development in Meteor.
Prior to starting the timed part of the WOD, you should set up your repo and install the template.
Create a private repo called “digits”, using meteor-application-template-react as a template. Clone this repo to your laptop, run meteor npm install
and then meteor npm run start
to bring it up.
Create an IntelliJ project called digits that points to your repo. An easy way to do this is to press the ‘Open in JetBrains IntelliJ Idea’ button in GitHub Desktop. Be sure to Trust the Project
. Check to make sure that ESLint is running by creating an ESLint error, such as two newlines at the end of the file.
Now you’re ready to do this practice WOD. There are two rounds to this WOD, each timed individually.
Start your timer.
1. Create a branch to hold your work.
Create a branch called landing-page-1 using GitHub Desktop, and publish this branch to GitHub.
If you haven’t already, start up your application using meteor npm run start
. Check to see that it’s running at http://localhost:3000. Take a look at the console to be sure there are no errors.
Pro Tip: run your app within the Terminal window in IntelliJ, and keep Chrome Dev Tools open during development. Install Meteor Dev Tools Enhanced if you haven’t already.
2. Update titles to say “digits”.
Edit app/client/main.html and app/imports/ui/components/NavBar.jsx to say “digits” rather meteor-application-template.
3. Add background image.
Add your background image to the body:
body
CSS style in app/client/style.css to specify the background and background-size properties as you’ve done previously for background images.When you’ve gotten to here, your landing page should look similar to this:
4. Change the NavBar and footer from bg-light to bg-dark
Change to a dark header and footer:
--matr-navbar-text-color
in the :root
element and setting its value to white./* Set up some CSS variables to theme the application. */
:root {
--matr-navbar-bg: #ECECEC;
--matr-navbar-bg-rgb: 236, 236, 236;
--matr-navbar-text-color: white;
}
footer
and footer a
to have the --matr-navbar-text-color
.footer, footer a {
color: var(--matr-navbar-text-color);
}
darkblue
or rgb(0, 0, 139)
. Update the two CSS variables --matr-navbar-bg-color
and --matr-navbar-bg-rgb
. To override the Bootstrap CSS variables we can assign them in the body
element set --bs-dark
and --bs-dark-rgb
to use our variables./* Change bootstrap variable values.
See https://getbootstrap.com/docs/5.2/customize/css-variables/
*/
body {
--bs-dark: var(--matr-navbar-bg);
--bs-dark-rgb: var(--matr-navbar-bg-rgb);
background: fixed center url("images/<your image filename>");
background-size: cover;
}
Notice when you click the digits brand or the Login dropdown, they turn black, and you can’t see the dropdown text since it is white.
--matr-navbar-highligt-text
and choose a light color that goes with our theme. I chose khaki. Then we can override the Bootstrap nabar CSS variables by using the selector body .navbar
body .navbar {
--bs-navbar-active-color: var(--matr-navbar-highlight-text);
--bs-navbar-brand-color: var(--matr-navbar-text-color);
--bs-navbar-brand-hover-color: var(--matr-navbar-highlight-text);
--bs-navbar-color: var(--matr-navbar-text-color);
--bs-navbar-hover-color: var(--matr-navbar-highlight-text);
}
.bg-dark a.dropdown-item {
color: var(--matr-navbar-bg);
}
When you’ve gotten to here, your landing page should look similar to this:
5. Update landing page text.
Replace the text and images appearing in front of your image in the Landing component:
Container
to get some nice margins.PeopleFill
. The text is “This address book enables any number of users to register and save their business contacts. You can only see the contacts you have created.”FileEarmarkTextFill
. The text is “For each contact, you can save their name, address, and phone number.”Calender2CheckFill
. The text is “Each time you make contact with a contact, you can write a note that summarizes the conversation. This note is saved along with a timestamp with the contact.”When you’ve finished this part, your landing page mockup should look like this:
6. Check for ESLint errors.
Finally, exit Meteor, and invoke meteor npm run lint
to run ESLint over your entire program. If you discover any ESLint errors, then fix them.
7. Commit your finished work.
When you’re done:
To ensure that you understand this material, you should do this WOD a second time.
Switch back to the main branch. This will revert your local repo to its state just after the installation of the template.
Create a new branch called landing-page-2.
Go through the WOD again. When you’re done, commit and push your landing-page-2 branch to GitHub with the message ‘landing page mockup finished in NN minutes.’, where NN is the number of minutes it took you to do it according to your timer.
Your TA will check whether both branches are in GitHub. Remember to give your TA access to your repository.
Rx: <20 min Av: 20-25 min Sd: 25-30 min DNF: 30+ min
Here’s a screencast of me working through this problem. You can watch this prior to attempting it for the first time yourself.
By the time and date indicated on the Schedule page, submit this assignment via Laulima.
You must grant read access to this repo to the TA for your section. To do this:
Your submission should contain:
You will receive full credit for this practice WOD as long as you have attempted it the required number of times and submitted the email with all required data before the due date. Your code does not have to run perfectly for you to receive full credit. However, if you do not repeat each practice WOD until you can finish it successfully in at least AV time, you are unlikely to do well on the in-class WOD. To reduce the stress associated with this course, I recommend that you repeat each practice WOD as many times as necessary to achieve at least AV before its due date.