The compiler.la from compilerla

Draft content for the Work page

To-Dos

Finalize copy for the work page
Finalize case studies for SCAG, ODS, CS strategy, and Data + Donuts
Finalize designs

Design the Home Page

Make any required changes to the website home page to reflect current stylings and brand.

Design work for the home page will be done in Figma and can be found there.

Design the About Page

Design the new About page for the Compiler website.

All design work will be done in Figma and can be found there.

Update jobs page with Mailchimp link

To-Dos

Replace bottom language on the /jobs page to: Missed a past opportunity? Subscribe to our mailing list, as we are always looking for great candidates

Build out the first draft of the website roadmap in Clickup whiteboard

Add Compiler Benefits & Perks content

Update the Jobs list page to include information on Compiler's Benefits & Perks.

To-Dos

Design jobs listing page to include Compiler info along with a list of Job openings / Past openings
Approve designs
Write content using benefits & perks doc
Add to roadmap schedule for future page updates
Develop using approve content and design

Copy for Home page

As this copy will be simple (~ 2 sentences), Anthony and Olivia will take care of drafting and finalizing.

Build out current website design in Figma

Using the styling from our current website and Figma designs:

Build out the Compiler homepage in Figma
Add in button design and changes listed in #9
Get owner access to past Figma designs

Update styling on Job postings

To-Do

Meeting with @segacy1 to introduce her to the website project

Segacy To-Do

Build out new design for job listing page
Build out new design for job posting page

Set up Netlify previews for pull requests

Context

As a part of our decision to go with Jekyll, we want to use Netlify as hosting and set it up to provide previews on GitHub pull requests. Contributors will hopefully feel confident in making edits to the website since they can preview their changes before it's deployed to the real website.

Acceptance Criteria

Pull requests contain a link to a Netlify preview of the site using the codebase from the pull request

Add link to Compiler's GitHub

Make it the 3rd line:

[email protected]

we build software for the government

github.com/compilerla

Refactor layouts to use Bootstrap

As we move towards adding more information to our website and towards restyling some parts (e.g. #24 and #33), it would be beneficial to use Bootstrap rather than writing all the CSS ourselves.

This refactor involves adding Bootstrap, making necessary changes to preserve the existing visual layout/styles, and then cleaning up unused CSS from our stylesheet.

Automatically add issues to the Project Board

This will be helpful for the team as we start to build out the backlog - so everything is captured on the board!

See https://github.com/cal-itp/benefits/blob/dev/.github/workflows/add-to-project-issues.yml for an example of a workflow that does this.

Q3 2022 sprint

Due date: September 30, 2022

Background

The focus for Q3 will be to add content targeting the "potential client" audience type - i.e. those that may want to hire Compiler.

Tasks

#6

Build out the 2023 website roadmap

To-Dos

Attend workshop to determine 2023 goals
#47
Create milestones/issues for 2023 based on the roadmap.
Discuss the timing of remaining pull requests for current jobs page revamp with the dev team

Team Image assets for About page "meet the team/who we are" section

The About page on the website has a "Meet the Team" section, which calls for photos of team members and a group shot. The website made the decision to use the watercolors made during our 2022 holiday party for the team photos.

Team photos:

Talk with Shelby to get in touch with the artist so we can ask her to create watercolors for any team members who do not have one
Label existing watercolors with name of person
Handoff images to design

Group photo:

Finalize which image to use from existing options

Design for Career/job page phase 2

Close account manager position

Move the account manager position from the jobs page Accepting applications to Past opportunities and grey out the apply now link (ex: Product Manager position)

Set up devcontainer with Jekyll

Context

@thekaveman , @machikoyasuda , and I settled on using Jekyll to at least start the new Compiler website. We have experience with Jekyll and it has a good amount of flexibility/control for us to get something up and running in the next month.

This task is for setting up this project's devcontainer, containing a basic installation of Jekyll.

Acceptance Criteria

Devcontainer is set up with git and pre-commit
Jekyll tooling is available (no need for actual Jekyll files yet)

Add ClickUp to /jobs

ClickUp can link lists, tasks, and subtasks with web forms created in ClickUp.

To-Dos

Look into ClickUp API information: https://clickup.com/api
Connect Netlify with ClickUp either through API or Zapier
Add form submissions to Inbox Careers@
Create a Custom field in ClickUp for job-roles and a dropdown option in Netlify for the applicant to fill out their role (product, delivery, UX/UI, software engineer, etc.)

Create initial Jekyll site structure and theme

Context

Once #1 is done, this task is for setting up the basic structure of our Jekyll site. This includes finding or creating a basic theme for the website (can be very MVP).

Some potentially relevant Jekyll docs:

Acceptance Criteria

The site can be viewed locally
There is a basic structure and theme in place

Create a budget for the website work

Tracking the creation of a budget for the Compiler website. While there is no hard number we must stick to, we wish to do this for a few reasons:

It's beneficial to track how much time is spent on this internal, non-billable effort
We may outsource some of the copy, for which we want to be aware of costs
Provides the PM's with an opportunity to work on skills development related to financial ownership, which is within the Delivery career ladder

Tasks:

@AnthonyRollins and @o-ram meet with Shelby to kick this effort off and learn what we can have access to
Review of Toggl hours tracked against the website project so far

Add capabilities statement

Content

Finalize content/design for capabilities statement

Design

#16
Add two new buttons; Get in touch and Capabilities Statement
Capabilities Statement button should use styling form Figma design and should be first and left-aligned link to compiler.la/capabilitites. On-hover change background to opacity: 70%;
Get in touch button should appear next to the Capabilities button with Compiler green #88B440 outline and #ffffff font mailto link: [email protected]. On-hover change background to opacity: 70%;
We build software for the government. change to an h1 and moved just under the logo

Implementation

Add a download button for the capabilities statement to the preview site, based on future Figma designs
Redirect https://compiler.la/capabilities to the capabilities statement downloadable file

Consider max width for site

Just a thought: I have a super widescreen, and the site currently expands to fill the entire viewport. Not necessarily a problem, but it might be more readable if we imposed a max width with the content center aligned and increased margins/padding on the sides.

Here's a screenshot of the homepage at full width on my screen:

And another of the current job posting:

Prep/Develop website workshop

To build a roadmap and meet our OKR (develop website roadmap by Q1), Segacy will lead a workshop with the website team and others to understand the website's needs in 2023.

To-Dos

@segacy1 to develop an outline for the workshop
@segacy1 host workshop in February
@AnthonyRollins @o-ram schedule website workshop
#41

Build out footer

Content

Check-in with Haley
@AnthonyRollins Respond to questions and add updates to lo-fi wireframes
Haley making edits to content strategy
~~Finalize homepage content strategy~~ Not needed for this ticket
Send footer content to designer

Design

~~Vyki to check in with Kristi~~
Send designer final content / strategy
Approve final design drafts for footer

Implementation

Develop footer based on design specs

Resources

Prior art / initial Figma design (not final, but to give an idea)
Lo-Fi Wireframe

Update apply link for account manager job

I've updated the form we should use for the Apply Now button on the website: It should go here

Redirect link for Compiler Retreat

For the upcoming retreat, we want the Compiler team to access our Retreat Guide on ClickUp easily. Could we create compiler.la/retreats page that redirects to a public link for our retreat guide?

A public link would be best as it provides a smoother experience for the team to access the docs, and there is nothing sensitive in the docs.

Development work for About page

This is a placeholder for the development work that will take place this quarter. Issues will be built out once designs and content are done.

Development work for Work page

This is a placeholder for the development work that will take place this quarter. Issues will be built out once designs and content are done.

Post Account Manager job position

Account manager Job Description . Open today, May 5th and close on May 19th.

Move compiler/jobs into this repo

We have a repo compiler with a jobs folder containing markdown files describing different job postings we've had. We'll likely be adding at least one new description there soon.

We link to these description files (directly to GitHub) in various forums: on our GitHub profile, Twitter, job boards, etc. and may also have openings to post soon.

Let's move that whole folder into this repository, so the descriptions become simple pages on our website that we can link to, like: compiler.la/jobs/product-manager.

Note we'll want to replace _ with - in the file name to make cleaner URLs

Todo

Make the Compiler logo a link to the homepage
Convert jobs to a Jekyll collection, render each as a page (output: true)
Create a jobs/index.html page with list of links for each job posting, add headings for Accepting applications, Past opportunities
Add frontmatter to job posts for open: true/false, on jobs index, render under the separate headings
On each job post, add back link to jobs index
Ensure [email protected] is a mailto link on each job post

Design for the Work page

Fix devcontainer dependency issue

This error shows when trying to open the devcontainer:

#0 29.70   Attempting uninstall: distlib
#0 29.71     Found existing installation: distlib 0.3.3
#0 29.71 ERROR: Cannot uninstall 'distlib'. It is a distutils installed project
and thus we cannot accurately determine which files belong to it which would lea
d to only a partial uninstall.
------
failed to solve: executor failed running [/bin/sh -c python3 -m pip install --up
[2022-08-10T17:31:59.138Z] 
grade pip &&     pip install pre-commit]: exit code: 1

Not sure what changed to cause this, but it seems like something external to our code. To fix this, we could try using a virtual environment within the Docker container or redoing the container setup to be based on a different image.

Refactor job `open` boolean to instead be an expiration date

Currently our job page looks for a variable named open for each job to decide whether it shows up in "Accepting applications" or "Past opportunities". This means that when a job is no longer open, we have to open a pull request to update the boolean. (See #42 and #48.)

We could instead have an expiration date variable on the job and have logic that checks the relationship between that date and the current date.

I'm not sure what the implementation would look like. This would have to be dynamic logic on the page rather than generated by Jekyll.

Development work for Home page

This is a placeholder for the development work that will take place this quarter. Issues will be built out once designs and content are done.

Update fonts and colors

Once the styling updates in #33 have been finalized in Figma, we can start incorporating those changes by updating the font sizes and colors.

Workflow for resume collection

On Compiler's Jobs page, there is a place where users can send us their resumes when there are no open positions. We need to find an internal and external workflow for applicants who want to send us their resumes.

Create a style guide page

Basically recreate the style guide page that Segacy has in Figma, but in code so that we can verify the styles are working correctly.

Text appears on top of button on job posting

Context

The bottom content appears over the Apply Now button on the latest job posting for the Senior Consultant, Product Manager. This position no longer accepts applications, so this isn't an urgent fix, but it should be resolved before our next post. No other job posting pages are affected as they don't have the Apply now button.

Screenshots

Desktop

Mobile

Update Job post page styling

Segacy has updated the styling for the job post pages. You can find the styling in Figma.

Obtain client testimonials

One of the sections for the About page calls for client testimonials. We ideally would like to have 2-3 that we can feature on the page.

This issue specifically tracks the tasks related to getting those testimonials, such as

Identify target clients
Draft email and testimonial copy (doc for planning here)
Coordinate with the appropriate individuals to contact the clients
Finalize the copy as well as who to attribute it to
Send requests to at least 2 clients
Insert copy into about page copy doc for testimonial 1
Insert copy into about page copy doc for testimonial 2

Update Jobs page styling

Segacy has updated the styling for the jobs page. You can find the styling in Figma.

Let me know what other info you need.

Brand work for website

To-Dos

Create Figma components for existing website designs.
Update styling (font size, colors, spacing) for all webpages
Produce mobile mockups of pre-existing pages.

Add Google Analytics settings

Add this to the <head> section of the index.html file.

<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-2JY7J1TEN2"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());

  gtag('config', 'G-2JY7J1TEN2');
</script>

Add instructions on getting started to README.md

Context

This is separate from #1 so that we don't block progress. This task is for writing instructions in README.md on cloning the project, starting up the site locally, etc. A good example to reference is the README from cal-itp/mobility-marketplace.

Acceptance Criteria

The README has enough information for someone else to follow and get the site running locally

Draft content for career/job page phase 2

Add Amplitude to website

To-Do

Setup amplitude under the Compiler account
Add tracking events for form submissions, page views, clicks, etc.

Document brand work for workshop

After concluding our website workshop on Feb 14th 2023, we need to capture the findings from those meetings to provide an update to the rest of the team who couldn't attend the workshop.

To-Do

Document brand work from the workshop
Report out to the Compiler team in #websites channel

Draft copy for the About page

Draft content for all sections of the "about" page

TBD on whether we handle all copy for this page in-house or if we ask Haley to help.

compilerla / compiler.la Goto Github PK

compiler.la's People

Contributors

Stargazers

Watchers

compiler.la's Issues

To-Dos

To-Dos

To-Dos

To-Do

Segacy To-Do

Context

Acceptance Criteria

Background

Tasks

To-Dos

Context

Acceptance Criteria

To-Dos

Context

Acceptance Criteria

Content

Design

Implementation

To-Dos

Content

Design

Implementation

Resources

Todo

Context

Screenshots

To-Dos

Context

Acceptance Criteria

To-Do

To-Do

Recommend Projects

Recommend Topics

Recommend Org