hackforla / website

Hack for LA's website
https://www.hackforla.org
GNU General Public License v2.0
324 stars 776 forks source link

Develop page for 404 Error Invalid URL page #1482

Closed qaz6209031 closed 3 years ago

qaz6209031 commented 3 years ago

Overview

It's a good idea to create a page for invalid url, so instead of seeing 404, user could have more clue to see what's going on.

Details ![Screen Shot 2021-04-27 at 8 09 45 PM](https://user-images.githubusercontent.com/44656685/116340764-9151fd00-a794-11eb-8195-120a0f873ee4.png)

RIght now if the invalid url is provided, out page will look like this

We could improve it to something like youtube did: ![Screen Shot 2021-04-27 at 8 11 31 PM](https://user-images.githubusercontent.com/44656685/116340942-e0982d80-a794-11eb-81e0-8f9f90d2b3ae.png)

or

Netflix ![Screen Shot 2021-04-27 at 8 12 49 PM](https://user-images.githubusercontent.com/44656685/116340997-f60d5780-a794-11eb-8bb1-e99360900d96.png)

Action Items

Design

Development

Resources

404 Error page in Figma (final design in pink rectangle) Template of a credit.yml file Credits page Sample invalid url (Hack for LA): https://www.hackforla.org/hahaha Sample invalid url (Youtube): https://www.youtube.com/asd Sample invalid url (Netflix): https://www.netflix.com/hahaha

akibrhast commented 3 years ago

@qaz6209031 This is a great idea! @daniellex0 Can the design team cook up something?

daniellex0 commented 3 years ago

Sure, I'll add UI/UX labels and see if anyone wants to take this on! Good idea @qaz6209031 ! 👍

qiqicodes commented 3 years ago

@Rosalyn-broddie Can you let us know your progress in regards to this issue? Thank you =]

Progress: Blockers:

Rosalyn-broddie commented 3 years ago

Progress: Started looking for more examples to pull inspiration from Blocks: Haven't gotten a chance to start designing the page yet Availability: I'll have some extra time this week to start designing some options for this page ETA: Uncertain

Rosalyn-broddie commented 3 years ago

Progress: Designed a couple of potential options for the 404 error page, but haven't fleshed them out yet Blocks: Stopped working on the 404 page for a little while in order to focus attention on the homepage Availability: I'll have some time to work on some more options this week ETA: 1 week

Rosalyn-broddie commented 3 years ago

Progress: Have a couple of options ready for an MVP, but I'll continue working on other options (animated, gifs, etc.) for the future

Availability: Since the focus has been on the homepage lately, I may not have extra time this week for other options, but I'll do some work on it if I do ETA: MVP options are finished, but I'll continue to look for more options that could be more fun (gifs, etc.)

Sihemgourou commented 3 years ago

@Rosalyn-broddie Please add update

  1. Progress
  2. Blockers
  3. Availability
  4. ETA
Sihemgourou commented 3 years ago

This looks good, great job @Rosalyn-broddie we can move this to development !

Lets go with this option : https://www.figma.com/proto/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website?page-id=9616%3A0&node-id=9630%3A97224&viewport=1648%2C761%2C0.284930020570755&scaling=min-zoom

akibrhast commented 3 years ago

@Rosalyn-broddie Could you please restructure the Figma designs for the error page such that it uses the grid system. Using the grid system is typically more industry standard and on top of that it also allows for easier creation of responsive UI, faster.

Something like this:

github-actions[bot] commented 3 years ago

@sena-ji Please add update

  1. Progress
  2. Blockers
  3. Availability
  4. ETA
sena-ji commented 3 years ago
  1. Progress: Thought it would be a good challenge for me to work on this issue. Asked Akib for some points to help me get started. Will talk about it on the meeting on Tuesday.
  2. Noted above.
  3. Available to work on it this week.
  4. Will get a pull request up by next week's meeting for review.
sena-ji commented 3 years ago
  1. Progress: I added the image used to the credits page. I created a skeleton of the page seen below: image
  2. Blockers: I think the fonts and sizes used on Figma are not showing correctly on my screen. Also need some help with container sizing.
  3. Availability: Will be asking for some help on Slack and the team dev meeting if someone is available.
  4. ETA: Hopefully by dev team meeting this week!
averdin2 commented 3 years ago

@sena-ji I spoke to Danielle about the font issue. She said not to worry about it for now. I think that there is a larger issue regarding the font that I am going to try and look into.

sena-ji commented 3 years ago

@averdin2 Thank you for the quick update! I will disregard the font for now and work on the mobile view :)

sena-ji commented 3 years ago
  1. Progress: I made some adjustments to the mobile view to align with Figma.

  2. Blockers: I did some research to try and rearrange items on mobile view. Having a hard time getting the image to align between text boxes, Asked Alex for some help.

3, Availability: Will work on the issue throughout the week! Been lagging because of work.

Here is the mobile preview at the moment: image

Sihemgourou commented 3 years ago

Hey Sena, what's your ETA please ?

github-actions[bot] commented 3 years ago

@sena-ji Please add update

  1. Progress
  2. Blockers
  3. Availability
  4. ETA
Aveline-art commented 3 years ago

@jbubar Sent a message on Slack, will encourage @sena-ji to do pair-programming to get unstuck

github-actions[bot] commented 3 years ago

@sena-ji

Please add update using this template (even if you have a pull request)

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures: "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) ask for help at a Tuesday or Sunday meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

You are receiving this comment because your last comment was before Tuesday, August 3, 2021 at 7:53 AM.


Note: This comment was created as part of a GitHub Action during its trial phase. If you find this GitHub Action to be disruptive/unhelpful, or if you believe there might be a bug, please leave a comment on this issue. All feedback will be used to further improve it. Thank you for your time.