You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By October 1, you are to have set up the "technology stack" for your project and integrated all the moving parts, so that it is possible to begin adding features. For example, if you are creating a PHP/MySQL based website, you need to have established a web hosting account, set up the database and some of its tables, decided on a PHP version, and created at least one basic "hello world" page with links to a basic CSS file. Determining a folder structure, and perhaps creating dummy files for pages yet to be developed, are also good ideas. Commit the current version of your code to the GitHub repository and tag it “v0.2”. This step is vital because it makes it possible to test and demonstrate new features. With the technology stack in place, someone could make a change to the CSS (or something) and test it with all the other components working. For full credit, you also need to provide a set of instructions for others to use your software. I, or anyone else, should be able to follow these instructions to get your project up and running. Therefore, in addition to your code, you need to provide information about how your server is set up, and you'll probably need to provide the SQL scripts to set up your database. A sign of good design is that the list of instructions doesn't need to be too long!
In your presentation to the class, take up to 10 minutes to tell us about the tech stack and demonstrate that it works. This is also a good time to tell your classmates where you’d like help.
The text was updated successfully, but these errors were encountered:
By October 1, you are to have set up the "technology stack" for your project and integrated all the moving parts, so that it is possible to begin adding features. For example, if you are creating a PHP/MySQL based website, you need to have established a web hosting account, set up the database and some of its tables, decided on a PHP version, and created at least one basic "hello world" page with links to a basic CSS file. Determining a folder structure, and perhaps creating dummy files for pages yet to be developed, are also good ideas. Commit the current version of your code to the GitHub repository and tag it “v0.2”. This step is vital because it makes it possible to test and demonstrate new features. With the technology stack in place, someone could make a change to the CSS (or something) and test it with all the other components working. For full credit, you also need to provide a set of instructions for others to use your software. I, or anyone else, should be able to follow these instructions to get your project up and running. Therefore, in addition to your code, you need to provide information about how your server is set up, and you'll probably need to provide the SQL scripts to set up your database. A sign of good design is that the list of instructions doesn't need to be too long!
In your presentation to the class, take up to 10 minutes to tell us about the tech stack and demonstrate that it works. This is also a good time to tell your classmates where you’d like help.
The text was updated successfully, but these errors were encountered: