We have a link at the bottom of the project README that is supposed to link to the issues for this project, but instead (because we copied it from another project when we started), it links to issues for another project. The link should point to https://github.com/approachable-io/software-interview-prep/issues instead of https://github.com/approachable-io/approachable-io/issues

ISSUE TYPE

• Typo
• Bug
• Feature

WHERE / WHAT

Right now, going to a route that doesn't exist will show a generic github 404 message

It would be better to have a custom 404 message (information about approachable.io and how to get involved in this project) as well as the 404 message.

EXPECTED BEHAVIOR

visiting a link that doesn't exist (eg http://interview.approachable.io/qwerty) should display our custom 404.html

REPRODUCTION STEPS

I would suggest starting with this document:
https://help.github.com/articles/creating-a-custom-404-page-for-your-github-pages-site/

ISSUE TYPE

• Typo
• Bug
• Feature

WHERE / WHAT

Our technical interview questions are a little light on technical.html. It would be good to add this question to our list.

EXPECTED BEHAVIOR

Clicking a link will take you to the question page which will allow you to see a possible response to the question.

REPRODUCTION STEPS

To create this new question, you should be able to follow the guide in the README https://github.com/approachable-io/software-interview-prep

ISSUE TYPE

• Typo
• Bug
• Feature

WHERE / WHAT

Continue filling the questions categories with at least one item per category.

EXPECTED BEHAVIOR

A good start is to define what it is and how it is useful.

REPRODUCTION STEPS

Add new document <angular-question>.html
Modify questions.html to link to new question page.

Move the dependency installation section to the supplemental-documentation folder to keep only critical instructions in the README (to keep things clear and simple without requiring a node install).

Put a link in the main guide for those interested in learning more (something like, "At this point, many projects will require installing dependencies, click here to learn more").

ISSUE TYPE

• Typo
• Bug
• Feature

WHERE / WHAT

Help flesh out technical questions page by adding categories not already represented.

EXPECTED BEHAVIOR

Give quick and simple "What is CSS" and give some general info on how it can be useful in web design.

REPRODUCTION STEPS

Add document what-is-css.html
Update link in technical.html to direct to new question page.

Images are really good quality but give no hints as to that to do. Maybe cirles or arrows pointing to the actions to be used?

ISSUE TYPE

• Typo
• Bug
• Feature

WHERE / WHAT

Continue filling the questions categories with at least one item per category.

EXPECTED BEHAVIOR

A good start is to define what it is and how it is useful.

REPRODUCTION STEPS

Add new document <agile-scrum-question>.html
Modify questions.html to link to new question page.

ISSUE TYPE

• Typo
• Bug
• Feature

WHERE / WHAT

Continue filling the questions categories with at least one item per category.

EXPECTED BEHAVIOR

A good start is to define what it is and how it is useful.

REPRODUCTION STEPS

Add new document <c-sharp-question>.html
Modify questions.html to link to new question page.

If you are new to this project and approachable.io, we would love your feedback (first time contributors welcome)!

I went back through our guide today and I think the dependency installation and creating a branch sections are well written, but I think it might make the guide less approachable for new users. We have a supplemental-documentation folder that could be used to store these sections. We could put links in the main guide for those interested in how to do things the right way?

@redxtech I would love your thoughts on this. I think it's definitely best practice to create a new branch, but I'm worried that it could make the project less approachable. This project in particular will probably remain npm install free in order to maintain approachability, so I'm not sure that the section is necessary here. It could be something we include in a later guide? The plan is to build to more and more complex topics. Is there maybe a balance where we add this as supplemental material like a suggested best practice instead of including it in the main guide?

ISSUE TYPE

• Typo
• Bug
• Feature

WHERE / WHAT

Link on technical.html doesn't load the new data-science.html question.

EXPECTED BEHAVIOR

The Data Science question should link to the local repository's file for data science instead of the forked copy.

REPRODUCTION STEPS

1. Visit interview.approachable.io
2. Choose the View our list of technical questions link
3. Follow the Data Science Overview link

You will find yourself at @syedbilal5000's repo instead of the question's HTML page in this repo.

ISSUE TYPE

• Typo
• Bug
• Feature

WHERE / WHAT

Our technical interview questions are a little light on technical.html. It would be good to add this question to our list.

EXPECTED BEHAVIOR

Clicking a link will take you to the question page which will allow you to see a possible response to the question.

REPRODUCTION STEPS

To create this new question, you should be able to follow the guide in the README https://github.com/approachable-io/software-interview-prep

ISSUE TYPE

• Typo
• Bug
• Feature

WHERE / WHAT

Users on our 404 page don't have suggestions on what to do next. We should probably provide suggestions on where they might want to go.

EXPECTED BEHAVIOR

Users who end up on our 404 page should be given links back to our index.html and possibly be told a little more about the organization.

REPRODUCTION STEPS

visit http://www.approachable.io/404 to see current state. Would like similar functionality, but with links to suggested content.

We're trying to create a repository of software technical interview questions. We have created a guide for how to add a new question which is the README for this repository.

We would love to start adding more questions to the list!

Right now, for instructions on making changes we basically just tell the user to "make changes". This makes sense to people who have been doing development for a while, but is super confusing to someone new to software.

Specifically, this guide should show a user how to add a new whiteboard question or add a new technical question. This involves:

1. Adding a new html file
2. Adding a link to that html file to its respective whiteboard.html or technical.html

Right now, the details suggest using an IDE, but I think we should be more explicit and tell the person following the guid (and potentially using GitHub or writing code for the very first time), exactly how to do this in detail with a specific editor. We can add more editors later, but I'd like to have one of these examples done in a free, approachable (no emacs or vim), editor like Atom or VS Code.

ISSUE TYPE

• Typo
• Bug
• Feature

WHERE / WHAT

EXPECTED BEHAVIOR

REPRODUCTION STEPS

ISSUE TYPE

• Typo
• Bug
• Feature

WHERE / WHAT

https://github.com/approachable-io/software-interview-prep/blob/master/docs/PULL_REQUEST_TEMPLATE.md

EXPECTED BEHAVIOR

Many of our new Pull Requests are well-intentioned, but are missing things, would be good to have a checklist included on the Pull Request Template so that people had a reminder of all of the small things necessary to add a new question. A new section with checkboxes like this specifically for those PRs like:

• <title> tag has been updated
• <h1> tag has been updated
• new file is kabob-case-like-this.html
• link to question has been added in technical.html or whiteboard.html

REPRODUCTION STEPS

Create a new Pull Request and the new checkboxes should be added.

Error in directory notes

The last step is to add your question to the main list. If you wrote a whiteboard question, this list will be in views/questions/whiteboard.html; technical questions go in views/questions/technical.html.

This should read The last step is to add your question to the main list. If you wrote a whiteboard question, this list will be in views/whiteboard.html; technical questions go in views/technical.html.

ISSUE TYPE

• Typo
• Bug
• Feature

WHERE / WHAT

The "More technical interview questions" link is the same size as the heading instead of being standard size in @mike8161990's database/SQL question about CRUD.

EXPECTED BEHAVIOR

The link should be the same size as standard text as with other questions.

The text for the whiteboard link on whiteboard.html reads What is the difference between a class and an object? when it should read Fizz Buzz. We need someone to fix the text.

http://interview.approachable.io/views/whiteboard.html

ISSUE TYPE

• Typo
• Bug
• Feature

WHERE

Project's Community Profile will track this progress

EXPECTED BEHAVIOR

Completing the Community profile for the project. Adding in templates and overall guidelines will help Build a strong community

• Description of Project
• README
• Code of Conduct
• Contributing Guidelines
• License
• Issue Template
• Pull Request Template

REPRODUCTION STEPS

I propose we add these items to a /docs/ directory to keep the root as clean as possible. The other option supported by GitHub is /.github/ which may not be intuitive or visible for users not familiar with hidden directories.

If interested, I have some starter templates for both Issues and PR that could be added in with minimal effort. If they turn out to bring no additional value the files can always be removed after.

If interested in learning more or you need ideas: Open Source Guides

ISSUE TYPE

• Typo
• Bug
• Feature

WHERE / WHAT

EXPECTED BEHAVIOR

REPRODUCTION STEPS

ISSUE TYPE

• Typo
• Bug
• Feature

WHERE / WHAT

As explained the README content is too much. It's hard to navigate sometimes.

EXPECTED BEHAVIOR

There should be some Table of Contents section at the beginning of the README. It can be generated automatically using this plugin or add the headers manually for the time being.

ISSUE TYPE

• Typo
• Bug
• Feature

WHERE / WHAT

This is a question that comes up often (or ones like it) in interviews. It would be good to add an answer to this to our collection. It currently has an approach, so this is probably a matter of embedding a github gist like our other questions.

ISSUE TYPE

• Typo
• Bug
• Feature

WHERE / WHAT

This view has Algorithms as the title and the h1. These should say Recursion instead

EXPECTED BEHAVIOR

Display correct title and h1.

Create a smaller version of the logo, but don't remove the current one. Then change the references to the new smaller (and ideally optimized) version.

The largest version of the logo we actually use on the site is just 20px wide, so it can be shrunk to that size. Then compressed using the steps laid out here https://developers.google.com/speed/docs/insights/OptimizeImages

ISSUE TYPE

• Typo
• Bug
• Feature

WHERE / WHAT

Our technical interview questions are a little light on technical.html. It would be good to add this question to our list.

EXPECTED BEHAVIOR

Clicking a link will take you to the question page which will allow you to see a possible response to the question.

REPRODUCTION STEPS

To create this new question, you should be able to follow the guide in the README https://github.com/approachable-io/software-interview-prep

We're trying to create a repository of whiteboard interview questions. We have created a guide for how to add a new question which is the README for this repository.

We would love to start adding more questions to the list!

ISSUE TYPE

• Typo
• Bug
• Feature

WHERE / WHAT

This is a question that comes up often (or ones like it) in interviews. It would be good to add this to our collection

EXPECTED BEHAVIOR

We should add this page (follow the guide in the README) to the application

ISSUE TYPE

• Typo
• Bug
• Feature

WHERE / WHAT

We suggest git add README.md instead of suggesting git add . and then we explain that . is an option. We should reverse this since most of our users will likely be using git add . and not selecting individual files to commit.

We are trying to make a website (plain html and css) that helps walk users through their first commit with an IDE. I tried simplifying things down, and thanks to Visual Studio Code's ability to clone a repository down from the application, I have gotten pretty far without the user needing to use the command line, but I've hit a point with being able to push where I don't know how to do it without the command line.

My biggest concern is that for a brand new user, the command line is a pretty big and intimidating beast, so I would like to do it without that. Any ideas or suggestions? Feel free to make a PR to the README.md if you have an idea.

I have also provided images up to that point (and am able/willing to produce them after that point) if someone has ideas. The biggest thing about not using the command line (besides the learning curve) is that if I can keep everything in Github and Visual Studio Code, then I don't need to write separate examples for Mac and PC and can still be inclusive.

The Fizz Buzz question on fizz-buzz.html to include a better description of the classic Fizz Buzz problem.

Adding an answer (in the language of your choosing or maybe even pseudo-code or an image of a whiteboard/paper or video) would be a great addition!

ISSUE TYPE

• Typo
• Bug
• Feature

WHERE / WHAT

--> Class vs object question in technical question

EXPECTED BEHAVIOR

REPRODUCTION STEPS

ISSUE TYPE

• Typo
• Bug
• Feature

WHERE / WHAT

Our technical interview questions are a little light on technical.html. It would be good to add this question to our list.

EXPECTED BEHAVIOR

Clicking a link will take you to the question page which will allow you to see a possible response to the question.

REPRODUCTION STEPS

To create this new question, you should be able to follow the guide in the README https://github.com/approachable-io/software-interview-prep

ISSUE TYPE

• Typo
• Bug
• Feature

WHERE / WHAT

Would love to have a "Back to Top" or "Back to TOC" type of link at each section to add to the easy navigation @AshBardhan built out.

EXPECTED BEHAVIOR

Click a section link from the table of contents and be able to quickly jump back up to the table with a quick link at each section.

We're creating a guide to making Pull Requests on projects and we would love feedback. If you're totally new to Github or Pull Requests, I would suggest starting with our getting-started guide.

If you are somewhat familiar with Github, we would love for you to follow the guide for this repository and add an issue or create a Pull Request for anything you find to be confusing. This is a work in progress, so please, if there's a point in the guide where you get stuck or even a point that took longer than you think it should have to figure out, let us know!

ISSUE TYPE

• Typo
• Bug
• Feature

WHERE / WHAT

We're getting quite a few contributions (and merge conflicts) because everyone is adding questions to the bottom of the list. Moving the questions into categories would help us avoid this problem. Maybe these could have links at the top the would skip down to certain sections of the page (based on ids?), but that could be a separate issue.

EXPECTED BEHAVIOR

Questions on technical.html would be divided into categories like:
JavaScript
C#
Java
Agile / Scrum
HTML
CSS
ANGULARJS
OOP
NODE

with corresponding questions underneath them.

REPRODUCTION STEPS

Currently technical.html is just a list without any categories, adding categories will allow it to be searchable to those interested in specific topics.

We accidentally created a file that isn't supposed to be a part of the project. We would like someone to remove the demo-file file in the root directory for us.

If you've never made a Pull Request before, check out this getting-started guide first, otherwise, this is a great issue for a new developer to tackle.

If you're a pretty experienced developer, we would love your help improving the guide for this repo or adding a whiteboard question or adding a technical question to this repository.

ISSUE TYPE

• Typo
• Bug
• Feature

WHERE / WHAT

EXPECTED BEHAVIOR

REPRODUCTION STEPS

Note that the new question .html file should just be copied from an existing one in its respective /questions/technical/ or /question/whiteboard/ folder and modified accordingly to maintain consistency.

Note that the created technical or whiteboard question must be added to the respective whiteboard.html or technical.html file.

Note that the <title> and <h1> tags of the copied file must be changed to represent the new question.

Supported by #33