Beman Website Team Page

Beman Website and Docs
1

Hi,

We are building the new website for the Beman Project and we discussed to have a team page. Furthermore, this information is required when writing a blog post for the website (as the author of the blog).

You can see an example on how the final team page should look like on the mock-up website team page - https://radunichita.github.io/website/blog/authors

If you would like to feature on the team page of the Beman Project, please reply with your information, organized in the following format:

<AuthorTag>: # your author tag, this is what you will use in the header section for a log
name: # Your Real Name
title: # Your title, how do you want to be recognized by other people
url: # Your Github profile page
image_url: # A url for your profile image (if you want to put your Github profile image, you can go to your profile, then click on your image and open it in a new tab. From the new tab, copy the link).
page: true # if an author page should be generated for you. 
socials: # Include your socials (like your Github, X, Linkedin etc)
    github: <yourGithubId>
1 Like
2

Here is an example for myself:

RaduNichita:
  name: Radu Nichita
  title: Software Engineer
  url: https://github.com/RaduNichita
  image_url: https://avatars.githubusercontent.com/u/45298861
  page: true
  socials:
    github: Radu Nichita
3

We didn’t have enough time for this topic today. Since next meeting is in 14 days, as a lead for the website development, I propose to take a decision on this thread.

My strong proposal would be to create this page:

  1. It would be great to have lots of us on that page! (my hope - everybody!)
  2. Consistency for blog posts - e.g., when having 3 posts with same author, make sure we do the same author description by default.
  3. Search/filter for all posts made by the same author. A small feature for our website.
  4. GitHub Team Page for Beman Project is not helping us by default. Check Please sign up for team @bemanproject/core-reviewers.

Notes: The Website development team would pre-populate the Team Page and will make sure to have the list updated - ofc, we need the information from each individual. That would means that when somebody will do a new post, it should have the authors already available.

I would also like people thoughts on this topic, but also asking @leads for a guidance / decision here. We have lots of things to do for our website, so we would prefer a quick conversation here, regardless of the decision. Thanks!

4

I would like to be added to the site, here is my info:

PaulTsouchlos:
  name: Paul Tsouchlos
  title: C++, Open Source enthusiast.
  url: https://github.com/DeveloperPaul123
  image_url: https://avatars.githubusercontent.com/u/6591180
  page: true
  socials:
    github: DeveloperPaul123
    bsky: ptsou
1 Like
5

CC: @Jeff-Garland - this is the thread discussed in today’s meeting.

6

Getting back to this. This seems a little bit redundant with what github already does with project members, but I guess it’s probably unavoidable?

1 Like
7

Sorry, I missed the reply. @Jeff-Garland do you have a suggestion/decision or a question here?

8

As per yesterday Beman sync meeting, since we had 50%-50% split for this topic (3 x pro, 3 x against, 6 x “don’t care”), the decision was passed to the website developer team.

@decision 1
!!!TLDR: We keep status quo related to blog authors centralization inside a file.

Me and @RaduNichita did a few experiments which concluded that we need and we’ll keep the authors.yml file and aliases inside it. We get for free some important features such as grouping posts for an author etc.
Notes:

  1. We’ll pre-populate the file with the most active users / people which may want to post.
  2. Unless a person makes any post, the content for that specific person won’t be displayed.
  3. We already have documentation which shows how to add a new author

@decision 2
We WON’T create Team page for now.

Since we don’t have a (strong) consensus to also do a Team Page, which essentially is one step further and display all entries from authors.yml regardless of them being authors for blog posts, we decided to NOT create a Team page for now (we would still need people involved to get data from them, leads to pick a team order, etc - since people don’t want or don’t care, I think it’s best use of time to at least not have this discussion right now)

We’ll finish 1) and start domain switch for the website.

CC: @leads

1 Like