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

Company profile enhancements #498

Open
doomspork opened this issue Mar 12, 2019 · 13 comments
Open

Company profile enhancements #498

doomspork opened this issue Mar 12, 2019 · 13 comments
Labels
discussion Further discussion is necessary enhancement A new feature or enhancement to the existing functionality help wanted Get involved! We'd love to have your help.

Comments

@doomspork
Copy link
Member

doomspork commented Mar 12, 2019

Following my conversation with @Nitrino it was determined we need to create an issue it identify and implement some profile enhancements to companies. Some of these off the top of my head could include:

  • Whether they consider themselves "remote" (despite having offices). I could see people searching on this.
  • More complete support for social networks. Right now we store Github and a blog. We could and should allow for others: Twitter, Facebook, Medium, ... you get the idea. Can we find a way to support this without having to add new columns for each new type? I think we can and I think we can update the UI to handle this gracefully.

I'd love to get your thoughts @tajchumber since you do a lot of the UI work 😁

@doomspork doomspork added enhancement A new feature or enhancement to the existing functionality help wanted Get involved! We'd love to have your help. discussion Further discussion is necessary labels Mar 12, 2019
@Nitrino
Copy link
Contributor

Nitrino commented Mar 12, 2019

Can we find a way to support this without having to add new columns for each new type?

Social networks usually do not require indexing and searching, so we can just use the PostgreSQL JSON array. e.g.:

[
  {
    "network": "twitter",
    "url": "https://twitter.com/elixirschool"
  },
  ...
]

@maartenvanvliet
Copy link
Member

I'd like to tackle the "remote" option for companies.
I suggest adding a remote true/false field to the companies table. Or are more options needed?

Also, what should the design look like?

@gemantzu
Copy link
Collaborator

@maartenvanvliet thank you for your help. I guess the more accurate solution would be to have a remote field in the jobs schema, because a company might have remote and non remote jobs to offer. Than, we could filter the remote jobs for anyone interested.

@tsrandrei
Copy link

One suggestion : Logo of the company ? might help having a visual impact I think. Perhaps doing a redesign of cards might help?

@nathanl
Copy link

nathanl commented Jul 22, 2020

I've wanted an optional field on submissions for a link which shows that the company is using Elixir. It could be public or visible only to admins, but something like a blog post by one of their engineers or a job posting would substantiate the claim.

@maartenvanvliet
Copy link
Member

Yes that would be helpful, I do some quick checks usually to check the claim (blogs, jobs, github repo's, phoenix html tags, cowboy http headers) but having submissions provide evidence would help 😅

@doomspork
Copy link
Member Author

@dzachrich @LatitudeAdjustment @gemantzu @samuelpordeus I would love to revisit the conversation to enhance our company profiles further (they're admittedly a bit lackluster). Do any of you have thoughts? All ideas welcome 🎉

@gemantzu
Copy link
Collaborator

gemantzu commented Mar 9, 2023

From the above, company logo should be a very good addition. The remote flag, I am still not sure about.

@doomspork
Copy link
Member Author

Would take a bit of time to convert all the existing companies but thoughts on a format like this?

%{
  company: %{
    company_logo: "" # What sizes? 35x35?
    description: "A brief description of the company",
    github: "https://github.com/",
    industry: "IT Services",
    name: "Example",
    sector: "Information Technology",
    website: "https://www.example.com",
  },
  locations: [%{
    # Support N locations for companies spread out?
  }],
  elixir_usage: %{
    blog_posts: [
      # Links to blog posts on Elixir usage
    ],
    projects: [
      # Links to Open Source Elixir projects
    ],
    summary: "A summary of how Elixir is used",
  },
  last_changed_on: ~D[2023-03-11],
  remote: true
}

It contains all the current information with some additions:

  • A section specific to Elixir usage with a summary, links to specific blog posts, and any open source Elixir projects
  • Industry + Sector to better align with GICS
  • Support for multiple office locations
  • A remote boolean
  • Support for logo

@hassan
Copy link

hassan commented Mar 13, 2023

This might somewhat overlap with "Elixir usage" but I would love to see an "adoption story" section describing how and why the company chose Elixir - something to show the CIO/CTO crowd that the decision was based on a rational risk/benefit analysis.

@doomspork
Copy link
Member Author

@hassan this is a great suggestion! I think this would go a very long way to helping the executive stakeholders as you mentioned. Thanks so much for sharing 🙏

@yordis
Copy link
Member

yordis commented Mar 13, 2023

Instead of remote: true maybe it is better to make it an enum and move it to be per location as well

type BetterNameField = 'REMOTE' | 'ONSITE' | 'HYBRID'

@doomspork
Copy link
Member Author

@yordis that's a great idea!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Further discussion is necessary enhancement A new feature or enhancement to the existing functionality help wanted Get involved! We'd love to have your help.
Projects
None yet
Development

No branches or pull requests

8 participants