-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue 8/create our projects section #32
Conversation
|
This PR should be narrowed to just the Projects page. Can't do a ton of coding at the moment but hopefully this is enough to start testing. The only change for now is splitting into two branches. All "Futures Steps" that concern this section still apply. |
Not fully complete yet. Still a couple of things left to finish (namely rendering the icons and finalizing logos). But should be fairly close and I want to see what everyone thinks so far. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
needs a fair amount of work still, I can dissect further when I have more time but would like to see some of the commented changes fixed first.
{ | ||
href: 'https://github.com/codeforpdx/recordexpungPDX', | ||
icon: '<FaGithub size={45} />', | ||
ariaLabel: 'Github link' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would make these all something more specific by just leading with the project name record sponge github link
otherwise to screen reader they will all say the same thing regardless of project.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Besides the commented things...
The file structure in general.
It seems you built the full Projects page in another file (ProjectBox.jsx
.)
If want to keep ProjectBox
separate, then put the <section>
and Header Typography
in Projects.jsx
. But, I think this filename is misleading.
ProjectBox
I read as an individual project's box - as in a single project (a reusable component), so that's why there were multiple ProjectBox
's in the Projects.jsx
page file. Something like:
projectsList.map(project => {
<ProjectBox .... />
})
creating a ProjectBox
for each project.
It's fine, if you envision it different - but then I would change filename to ProjectsBox
or ProjectsSection
/ but again then there's the debate of whether or not that's just the whole page and code should live in the Projects.jsx
file.
Just currently no real purpose to Projects.jsx
- it has an empty Typography
and just a container
wrapping your ProjectBox.jsx
. The ProjectBox
as is, isn't really a reusable component - it's the whole section.
Made the edits Scott recommended, including making the I also moved the code from If we do decide to keep it this way, would we then want to move Next is working on rendering the icons. |
To fix the Icons. react is expecting a
links: [
{
href: 'https://github.com/codeforpdx/recordexpungPDX',
icon: <FaGithub size={45} />
},
{
href: 'https://discord.gg/x6b573et',
icon: <FaDiscord size={45} />
},
{
href: 'https://codeforpdx.github.io/recordexpungPDX',
icon: <FaEarthAmericas size={45} />
}
] on a side note in |
Okay should (hopefully) be very nearly complete. Just need some (hopefully) final feedback. Icons are ready and I did some coding abstraction, which may not even be necessary Logos should look a little nicer now too. I added a divider, per Scott's suggestion. Looks good but I could could go either way with it. Also, a few commits ago I hid the title on small viewports since it felt redundant. Looks better in my opinion but it can be put back. Otherwise I did a whole bunch of messing with padding, margins, spacing, and all that. If we agree there's more to be done with that, perhaps we can hold until the next meeting? We're already planning on discussing layout more there, as I understand. I'm pretty content with this. Let me know what you all think. |
I think for these projects, hiding the title works (could even do it sooner at |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In my opinion, we can discuss codestyle throughout full app at meeting (consistency with what to abstract and what not to & what to pull into own file vs leave in parent.)
Think this looks good
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Talked in discord, pushing changes to merge.
src/pages/Projects.jsx
Outdated
<Typography | ||
variant="body1" | ||
// TODO: Keep textAlign here? | ||
sx={{ textAlign: 'justify' }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This weirdly gaps the text and we don't do that anywhere else. Don't see any reason to keep it.
src/pages/Projects.jsx
Outdated
minWidth: { xs: '95vw', sm: '80vw' }, | ||
maxWidth: { sm: '85vw' }, | ||
background: | ||
index % 2 === 0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
something you had commented on secondary partners, can we make the gradient go up and down on smaller viewports. If we want to change how the gradient looks after that we can figure out at the meeting but at least it will be consistent for now.
background: {
md:
index % 2 === 0
? 'linear-gradient(270deg, rgba(217, 217, 217, 0) 38.54%, rgba(217, 217, 217, 0.4) 82.29%)'
: 'linear-gradient(90deg, rgba(217, 217, 217, 0) 38.54%, rgba(217, 217, 217, 0.4) 82.29%)',
xs: 'linear-gradient(0deg, rgba(217, 217, 217, 0) 38.54%, rgba(217, 217, 217, 0.4) 82.29%)'
}
src/pages/Projects.jsx
Outdated
mb: { xs: 5, sm: 15 }, | ||
p: 5, | ||
borderRadius: '25px', | ||
minWidth: { xs: '95vw', sm: '80vw' }, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This Doesn't constrain within the xl
containers and needs to be refactored to cap.
the padding is too much for mobile. This styling fixes these issues.
const boxStyle = (index) => ({
mb: { xs: 5, sm: 15 },
py: 5,
px: 2,
borderRadius: '25px',
background: {
md:
index % 2 === 0
? 'linear-gradient(270deg, rgba(217, 217, 217, 0) 38.54%, rgba(217, 217, 217, 0.4) 82.29%)'
: 'linear-gradient(90deg, rgba(217, 217, 217, 0) 38.54%, rgba(217, 217, 217, 0.4) 82.29%)',
xs: 'linear-gradient(0deg, rgba(217, 217, 217, 0) 38.54%, rgba(217, 217, 217, 0.4) 82.29%)'
}
});
</Container> | ||
<Box | ||
as="section" | ||
sx={{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
needs to have max size container, currently content can go full width.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
spoke in discord, pushed fixes for merge.
This PR:
Resolves #8
Adds both projects sections: a brief one on the main page and more detailed ones on the projects page.This isn't done and I'm not thrilled with it. But I've stretched myself too thin lately and will be out of town for a couple of days, and it's taken long enough already.
Edit: This PR now only updates the detailed section on the projects page. The brief section is detailed under issue #34 and will receive its own PR.
Screenshots (if applicable):
Future Steps/PRs Needed to Finish This Work (optional):