prototype/ contains a straight HTML/CSS/etc. version of the prototype
page. The static site generation system (to be added later) should produce
essentially the same output under the output/ directory.
At https://patio-coop.github.io/patio-homepage/ (on GitHub Pages) we publish one branch of the repo. This is whatever branch a developer happened to need to show to others at the time; feel free to change it when you need it. (It's set by clicking on the Settings tab and then in Pages in left sidebar.)
Alao, the homepage is copied to https://patio.coop by Netlify. Netlify is used for enabling the forms. The login/password information for netlify is kept by some people. Ask around! (But we need a proper sharing mechanism)
For development help contact anyone
in the #homepage-technical channel, in the
private chat server
To join the private chat group, contact someone you know or, yasu@tng.coop, or anyone you see in commit messages 😄
There is also a Trello board for the development
Design and content is done by the folks in the #Community Landing Page
group.
Information about naming and other code conventions is in the STYLE.md
document.
- The branch that contains the latest version agreed as valid by everyone is the "main" branch. The "production" branch is used to deploy the site.
- Whenever you take a new issue, you must create a new branch starting from main with the following name: "dev/your_name/something_that_identifies_issue".
- Whenever you work on your issue, please make sure to update your branch daily with the latest version of main.
- When you finish the issue (or while working on it), push everything to a remote branch with the same name.
- Lastly, create a pull request and assign it to a teammate.
We expect that if you are going to start working on an issue, you do something like what follows.
-
git status=> It will tell you the status of your current branch, make sure you are standing on your issue branch or main branch. -
git pull=> Pull everything from origin. "git pull origin main" for example updates the branch I'm standing on with the latest from main, this is to keep my copy of main up to date or my issue branch up to date with the changes from main. -
git checkout-b "dev/your_name/something_that_identifies_issue" => always check before running this command that you are standing on main using "git status". -
git add "filename"=> Add the file to the list of changed files ready to be committed. Make sure you add the changes you want to commit, avoid doing bulk actions (like doing "git add .", please don't do it unless you are sure about it) -
git commit -m "descriptive message"=> Please use a descriptive message. This action will commit the changes added with the "git add" statement above. Try not to make commits with many unrelated changes, it is advisable to make commits "with a certain logic", for example, if we are creating reusable components and then we will implement them, maybe it is a good idea to create them, make the commit and then implement them and make another commit. In this way we avoid huge commits where it is not easy to identify the changes. -
git pull origin main=> Before doing a push of the local commits, it is a good practice to do a pull to make sure that there will be no conflicts when the commits are merged with main. -
git push origin dev/your_name/something_that_identifies_issue=> this will create the branch of my issue in origin for others to see. Did you finish the issue? => Create a PR by going to the following address: https://github.com/patio-coop/patio-homepage/pulls
The way you type the commands may vary, in fact some may use a graphical environment to do these steps. What we care about is to show the sequence and make sure that we work in an orderly manner. The idea of the PR is that we have an excuse to chat with each other and read each other's code so we continue to learn and interact with each other.
The development group is using this figma board to work collaboratively in the design process.
To deploy, you must have the latest version of the site. The steps to follow are:
1- Make sure you are in the "production" branch.
git checkout production
2- Update the branch with the latest version of "main".
git pull origin main
3- Update "production" with the latest version of "main".
git push origin production
4- Update the site on the contracted netlify hosting with the folder containing the latest production version.
5- To continue working, make sure to go back to the main branch
git checkout main
Note: Currently it deploys to Netlify.