ucfai / tasks

The administrative bot. Dubbed `autobot` – handles the overall maintenance of each group, each semester.
4 stars 2 forks source link

Discussion of website implementation / updates #17

Closed jmuchovej closed 4 years ago

jmuchovej commented 5 years ago

Semi-public discussion on some changes to be made to the website – https://ucfai.org/

SirRoboto commented 5 years ago

@ionlights @causallycausal Here are the things I would like to see added to the website:

*1. Sign-in button for members

  1. Links to our other content
  1. An actual menu bar from the main page
  1. Meet our Team and Contact Us pages
  1. A slide deck window on the front page to display some general pictures
  1. A page to view our recent announcements (possible cross-implementation with a discord bot)

*7. Updating our wordage from the main page, including a more detailed description of our vision

*8. Releasing Data Science

*Note: We've already discussed these items, or at least some version of them, prior to this post here, meaning they aren't necessarily novel but worthwhile to deliberate more on and continue keeping at our focus.

These items aren't ranked in any order of importance but rather things to throw out. If we are focusing our efforts on specific tasks, I would stress the importance of items 1, 3, 7 and 8.

This list is also not exhaustive, but simply the things that come to mind when I consider quality-of-life implementations and things you would generally expect for a club that utilizes quite a few independent platforms. This allows students to come to the website and access everything they need directly through there.

jmuchovej commented 5 years ago
  1. Sign-in button for members

Sure, this makes sense to have and will definitely be implemented once the authenticator is properly setup. We'll chat about this in the meeting today (Aug 14).

  1. Links to our other content

Agreed, though placement of all these links will take some time – as having a tidy navigation is ideal. Makes for less confusion. We may need to have a "hamburger menu" (think the 3 horizontal line menus in apps like those from Google) to store all our links.

I definitely think we should have the places we want the most interaction on the navbar itself.

They should definitely be in a footer, as should a sitemap, but I'd say that's a lower priority right now, as we need to figure out how we want the sitemap to be laid out (e.g. enumerating semesters, etc.).

  1. An actual menu bar from ~the main page~ all pages

This definitely needs to be there, when I initially built the site it was an afterthought because I didn't have time to put thought into designing it.

  1. Meet our Team and Contact Us pages

Meet our Team: We have something like that for Coordinators. How is this different? Also, should these be longer-term, in the sense that people can go back to a specific semester and see the Coordinators from that semester? Should we not care about that? (I disagree on the last bit.)

Contact Us: Should there be a form on the page? If so, why? What are you thinking of putting here? A page with just social links and an email is going to be very sparse, so what else might we put here? What if we combined it with an "About Us" or something of the like?

  1. A slide deck window on the front page to display some general pictures

You wanna get rid of particles.js? 😢

  1. A page to view our recent announcements (possible cross-implementation with a discord bot)

This is good, it was something previously discussed between @dibaccory and I – but this would actually take quite a bit of time to get it fully-functional. I think this is something to table until later in the Fall – as it requires dissecting the Discord, Instagram, and Facebook APIs (if we can auto-post on the latter two – I think they may prevent that now). NB: There are other ways to do this than using the APIs, but it's a bit more of a pain. Also, we can xpost on Instagram/Facebook, so may we just need to write it up on Instagram and Facebook will be sorted? This should also include email blasts.

  1. Updating our wordage from the main page, including a more detailed description of our vision

Sure, I believe we have a lot of that already documented someone in the abyss that is Google Drive, but it wouldn't be bad to have it somewhat immortalized on the site.

  1. Releasing Data Science

LOL. Y'don't say. 😅

Major takeaway: Previously, I tried to make a regular structure among groups, semesters, and the like. It seems we may need to discern some monolithic structure which can be use for the more generic things, like "Meet our Team," "About Us," etc. That may not be something easily injectable into the current site design – but we should have all this data present which means it just requires re-architecting.

SirRoboto commented 5 years ago

Note: Items are listed in order of priority first and broken down based on Content (denoted by “C”) and Style changes (denoted by “S”). If any of the items have “TBD” in them, then feel free to give them little head space, for now.

While the specific verbiage itself is not detailed here, this should help distinguish between additions of text and additions of pages/reorganization of content.

  1. Updating wordage for main page
    1. C: Course corrected to Core
    2. C: Change of main blurb to accurately represent the release of Data Science
    3. C: Vision statement should be expanded on
      1. S: Consider a link such as “Read More” to take them to that expanded explanation
  2. Releasing Data Science
    1. C: Wordage to give a summary of Data Science
      1. S: Data Science box appears beside Core and Intelligence
    2. TBD S: Data Science space should be formatted similar or use the same format/navigation as Core and Intelligence (aside from some extra additions such as competitions, which are TBD)
  3. Sign-in button for members
    1. C: “Sign in” text from Core, Data Science, and Intelligence pages
      1. S: Functionality of Sign-in button to redirect them to their respective account/update their attendance
    2. TBD C/S: Possibility of including an account page with details on GPU hours, submissions, feedback, and personal info put in when they registered
  4. Menu bar/hamburger menu
    1. Items on hamburger menu
      1. C: Meet our Team
        1. S: Like how we have coordinators displayed, we have a dedicated, archived space for current and past officers with their position and photo
      2. C: Other Resources (listed on hamburger menu)
        1. S: Should include links to Discord, Github, Instagram, and Facebook (for now)
      3. TBD C: Announcements Page
        1. S: We should hold off on this item, but it would most likely pull the announcements from somewhere else
      4. TBD C: Possible About Us
        1. C/S: Instead of expanding the vision statement in a “Read More” from the landing page, we could instead put it on our About Us page, or rather only have them navigate to the “About Us” through the menu bar
    2. TBD Menu bar persists either:
      1. S: Everywhere, including the landing page, OR
      2. S: Everywhere, excluding the landing page
    3. C/S: “Home” button on menu bar for all pages
  5. “Sponsor Us” button
    1. C/S: Appropriate page that includes a link to the sponsorship package or some coverage of the material in a condensed format, or some combination of both
    2. S: Button should fall below the fold, or at the bottom of the page
    3. C: Should be available from every page, including the landing page
  6. S: Implemented slide deck from Instagram
    1. S: Includes Pictures
    2. TBD C/S: Could do something similar for announcements
    3. S: Can be located on landing page in a way where it doesn’t affect particles.js
jmuchovej commented 5 years ago
  1. Updating wordage for main page

    1. C: Course corrected to Core _data/groups.yml
    2. C: Change of main blurb to accurately represent the release of Data Science index.md
    3. C: Vision statement should be expanded on index.md
      1. S: Consider a link such as “Read More” to take them to that expanded explanation index.md
  2. Releasing Data Science

    1. C: Wordage to give a summary of Data Science _data/groups.yml
      1. C: Data Science box appears beside Core and Intelligence _data/semesters/fa19.yml (make this and copy the structure of sp19.yml)
    2. TBD C: Data Science space should be formatted similar or use the same format/navigation as Core and Intelligence (aside from some extra additions such as competitions, which are TBD)

      Not sure what you mean here, are you talking about the page which would be at /data-science/?

  3. Sign-in button for members

    The following section, honestly, should be characterized under S more than C. 😅

    1. C: “Sign in” text from Core, Data Science, and Intelligence pages
    2. S: Functionality of Sign-in button to redirect them to their respective account/update their attendance
    3. TBD C/S: Possibility of including an account page with details on GPU hours, submissions, feedback, and personal info put in when they registered
  4. Menu bar/hamburger menu

    The following section, honestly, should be characterized under S more than C. 😅

    1. Items on hamburger menu
    2. C: Meet our Team
    3. S: Like how we have coordinators displayed, we have a dedicated, archived space for current and past officers with their position and photo
    4. C: Other Resources (listed on hamburger menu)
    5. S: Should include links to Discord, Github, Instagram, and Facebook (for now)
    6. TBD C: Announcements Page
    7. S: We should hold off on this item, but it would most likely pull the announcements from somewhere else
    8. TBD C: Possible About Us
    9. C/S: Instead of expanding the vision statement in a “Read More” from the landing page, we could instead put it on our About Us page, or rather only have them navigate to the “About Us” through the menu bar
    1. TBD Menu bar persists either:
      1. S: Everywhere, including the landing page, OR
      2. S: Everywhere, excluding the landing page
    2. C/S: “Home” button on menu bar for all pages
  5. “Sponsor Us” button

    1. C/S: Appropriate page that includes a link to the sponsorship package or some coverage of the material in a condensed format, or some combination of both
    2. S: Button should fall below the fold, or at the bottom of the page
    3. C: Should be available from every page, including the landing page

      On other pages, maybe it can go in the navbar? That seems reasonable, considering what most open-source projects do. Main "gripe" I had was on the homepage.

  6. S: Implemented slide deck from Instagram

    Where should this go? Homepage?

    1. S: Includes Pictures
    2. TBD C/S: Could do something similar for announcements
    3. S: Can be located on landing page in a way where it doesn’t affect particles.js
SirRoboto commented 5 years ago

So, anywhere you feel it should be more S than C, I only put C down because I considered that both those items (3. and 4.) may require some text/descriptions implemented among their respective pages and items, but I agree that it is primarily S.

2 ii. Correct, I'm talking about what's under /data-science/ 5 iii. navbar being where home currently sits on other pages? I'm still concerned that if sponsors can't immediately grab it when coming to the webpage, then it won't really serve us 6 Yes, I was thinking the home page

jmuchovej commented 5 years ago
  1. iii. navbar being where home currently sits on other pages? I'm still concerned that if sponsors can't immediately grab it when coming to the webpage, then it won't really serve us

So, on the homepage the button would still be there, but in a different place from the navbar. On all other pages, it would be on the navbar. That's what I'm thinking.