olivcamj / apiary

Apiary Landing Page

Hi 👋🏿, I'm Olivia

A Software Engineer (frontend focused) currently living in Florida

🔭 Right now, my main focus is honing my skills for coding interviews, preparing to tackle challenging problems head-on.

🌱 In my journey of continuous growth, I'm diving deep into Next.js, exploring its powerful features and enhancing my proficiency in building robust web applications.

Below where my contribution graph is empty, it's likely because I was tending to my family, enjoying walks with my dog 🐾, hitting the weights, or doing light cardio 🫀 to stay energized and focused. Because life's too short not to embrace every moment!
Let's connect and collaborate on exciting projects! Feel free to explore my repositories and contact me on linkedin.

Languages and Tools:

apiary's Issues

Create ServiceCard Component

Add CMS to Examples

Create Projects Component

Contains grid of projects
Type of project is passed in as a prop, which will determine the type of card it contains (ProjWithImg or ProjWithoutImg)
It also needs the "ghost card" that appears until the real card loads (like a spinner)

Create Steps Component

Add Images

Note:

• Optimize images (compress images to save disk space without sacrificing quality)
• Add internal images to /src/images and external (or vendors) to assets directory

Create Services Component

Create FAQ Component

Create BenefitCard Component

Add requests section

Create Wireframe

Create StepCard Component

Initial File Structure

Add Button Component

There are a least two different sizes of buttons in the figma design.

There are also 2 style - filled and outline

Add README.md

It would be nice to include:

• The project's name
• description
• images
• link
• demo video (optional)
• contributor list (optional)

Set up CMS in Contentful

Create ProfServiceCard Component

Create Card Component

Must have:

• Image
• Heading
• description

Create Form

Create ProjWithImg Component

Create with static data first (will add CMS fields in Phase 3)

Create NavLinks Component

Will have different links passed in according to page

Create Nav Component

Image

Contains image, links (MainLinks or ProfessionLinks), and Button

Create Footer Component

Must have:

• footer nav
• Link to top

Add Font

Create SpeechBubble Component

This will pass in the type="question" or "answer" prop and that will determine:

• background color
• text color
• position
• icon or no icon

Connect buttons

Functionality for buttons needs to be added.

Create CardRow Component

This will contain the 3 cards for all the blocks that need it. It will have card type (AboutCard, ServiceCard, BenefitCard, ProfServiceCard) passed in as a prop

Create ProjWithoutImg Component

Create with static data (CMS fields will be added in Phase 3)

Create CardBlock Component

This is a generic block that holds title, subtitle, and CardRow component. The types are:

• Benefits
• Services
• About
• ProfServices (won't have title/subtitle passed in)

Props for this component:
-Background color
-text color
-type

fotter hover names

Create ServiceCard Component

Create ProjectTabs Component

These are the 3 buttons that act like "tabs" to change type of project examples.

I'm not sure if this would be better as it's own component and added to the greater "examples" section on the Main page, or if it needs to be part of the Projects section since the functionality affects it. I'm trying to reuse the Projects component on the Professions page, and it doesn't have the buttons over there.

Create Intro Component

(I couldn't come up with a great name for this one - feel free to rename!)

This one appear before the projects on the Main page and at the top of the Professions page

Create Header Component

Add useful section

Create Header Component

Must have:

• Logo
• Navbar
• Button

Create Examples Component

Will contain:
Intro Component
ProjectTabs Component
Projects Component
Buttons

Create Benefits Component

Create Wrapper

In App.js