Skip to content
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

Improving the C-R website #63

Closed
4 of 12 tasks
sarabellei opened this issue Sep 7, 2022 · 5 comments
Closed
4 of 12 tasks

Improving the C-R website #63

sarabellei opened this issue Sep 7, 2022 · 5 comments

Comments

@sarabellei
Copy link
Contributor

sarabellei commented Sep 7, 2022

Here a draft document with the https://docs.google.com/document/d/1nDg-13cJD-6a2H05dDD97A4qvpxbD8WBcKRc4CkGu0U/edit

You can find the draft, a trace of the discussion we had about it, and a description of what needs to be improved.
More in detail:

  • menu should be changed to: (Research) (Projects) (Applications) (Resources) (Team) (Careers)
  • HOMEPAGE: add Compiler-Research Logo on the Homepage.
  • HOMEPAGE: change headline and sub-headline. Proposal in the document shared above.
  • HOMEPAGE: on the right side of the homepage, link to: upcoming events/upcoming meetings/view all past events.
  • HOMEPAGE: (this is just an idea) link to: subscribe to upcoming events.
  • RESEARCH/INTERACTIVE C++: needs to be rewritten.
  • RESEARCH/COMPILER_AS_A_SERVICE: needs to be rewritten. Proposal outline in the document shared above.
  • RESEARCH/AUTOMATIC_DIFFERENTIATION: needs to be rewritten. Proposal outline in the document shared above.
  • PROJECTS/CLING: should we refer to the read the docs Cling webpage?
  • PROJECTS/CLANG-REPL: we need to think what page we will link here.
  • RESOURCES: see proposal in the document shared above.
  • CAREERS: see proposal in the document shared above.
@sarabellei sarabellei changed the title Improvement of C-R website Improving the C-R website Jan 18, 2023
@QuillPusher
Copy link
Contributor

QuillPusher commented Apr 27, 2024

Current Statuses

  • menu should be changed to: (Research) (Projects) (Applications) (Resources) (Team) (Careers)
    - Change Openings (under Join Us) to Careers PR169
    - Skip Resource/ Links (not enough data)
    - Moving the Application/Impact to a separate issue: issue 170
  • HOMEPAGE: add Compiler-Research Logo on the Homepage.
  • HOMEPAGE: change headline and sub-headline. Proposal in the document shared above.
  • HOMEPAGE: on the right side of the homepage, link to: upcoming events/upcoming meetings/view all past events.
    - New timelines added to homepage, linked to pages with details
  • HOMEPAGE: (this is just an idea) link to: subscribe to upcoming events.
    - This functionality doesn't exit yet. Can use a free Newsletter service like MailChimp, but newsletter maintenance and publishing requires a lot of periodic effort.
  • RESEARCH/INTERACTIVE C++: needs to be rewritten.
    - Exists but is outdated
  • RESEARCH/COMPILER_AS_A_SERVICE: needs to be rewritten. Proposal outline in the document shared above.
    - Exists but is outdated
  • RESEARCH/AUTOMATIC_DIFFERENTIATION: needs to be rewritten. Proposal outline in the document shared above.
    - Moved to its own PR - New page added for Research Area "Automatic Differentiation" #163
  • PROJECTS/CLING: should we refer to the read the docs Cling webpage?
    - Linked to ReadTheDocs
  • PROJECTS/CLANG-REPL: we need to think what page we will link here.
    - Linked to Clang-REPL doc on LLVM, including CR's Execution Results Handling features.
  • RESOURCES: see proposal in the document shared above.
    - The Google Doc mentions "webinars, case studies, scientific publications, etc.", but these are already covered in Project Meetings, Presentations and Publications sections.
  • CAREERS: see proposal in the document shared above.
    - PR169

@vgvassilev
Copy link
Contributor

Can we close that issue in favor of the newly created ones?

@QuillPusher
Copy link
Contributor

@vgvassilev yes, we can close #63 since all pending tasks within it have been broken down into more manageable smaller issues listed above

@vgvassilev
Copy link
Contributor

Thanks a lot, @QuillPusher!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants