bradwestfall / webdevphoenix Goto Github PK

Leave questions here regarding adding company profiles

Hello, I need to remove "G/O Digital" as they're becoming their parent company TEGNA and possibly no longer hiring developers in Phoenix. There were great directions when I set them up and I cannot find them now, nor know enough to infer what to do. Thank you!

when a user is contributing a company they use the Github interface for convenience. I personally forked the project and created a company page which will later be requested as a pull. Forking the project then receives the following emails.

The page build completed successfully, but returned the following warning:

CNAME already taken: webdevphoenix.com

For information on troubleshooting Jekyll see:

  https://help.github.com/articles/using-jekyll-with-pages#troubleshooting

If you have any questions you can contact us by replying to this email. 

Good idea, putting this up here.

Anyhow, yeah that exactly what i'm saying, profiles for individuals to really match people who will work well together. Finding a co-founder isn't like hiring an employee it's a much more delicate process, more like dating.

Hello, the "Pull Request" link and "Contribute" button both generate 404 errors. Not sure if you're aware.
http://webdevphoenix.com/add-company/

Travis CI provides a PR build flow, approving and auto merging a PR into code. This type of workflow will decrease the necessary maintenance. I would consider this project (webdevphoenix) as open source, a license file might be needed to make it official. Travis CI is free to projects considered as open source.

Further information:
http://jekyllrb.com/docs/continuous-integration/

I think the site would really come to life with job postings and a forum. I think they can be one in the same. Since it's a Jekyll project I can do Disqus comments on a page that is dedicated to job postings. My hope is that it would be a long running thread where people can post links to jobs at other sites. I don't think I want to host the postings themselves because:

1. The know-how it takes to make pull requests. We can't expect job posters to know this. Company and developer profiles are different
2. If lots were posted, the volume of work to accept and merge them
3. The lack of discussion around the job

The Forum style approach solves all these. Also postings can more easily expire by virtue of falling off the thread when lots of new comments are posted.