I am once again making a change to a file while trying to push to github
This is the repo for my portfolio. The initial project is on the repo called A. Once that project was built I decided to work features and bug fixes in more of a agile ecosystem. This is to learn and show my knowledge about working in a team environment. My knowledge of SCRUM development and sprint cycles.
For project management I am using Click Up which is an all in one platform. I can create docs or link to resources. I have it set to work in a agile work flow with scrum. To review this please ask to be added at dev3027@mason-roberts.com.
For communication I am using Slack which includes a slack channel dedicated to this build. As cards are moved or commented on in Click Up, the Slack channel is updated.
For code I am using Github. This allows me to have feature branches and a production branch. My production branch for this project is the main branch.
For CI / CD I am using the above and Netlify. Netlify is using this repo and builds the main branch when a change is made. So as changes are merged of pushed to the main branch, Netlify will perform a build and present it.
Click Up has been integrated in this repo. Click Up is being used for project management. I am using a standard Agile, scrum work flow. This is worked in standard sprints of 2 weeks.
To change the status of a task on Click Up, include the task id when you commit your change. You can get the id from the card. Hover over the card, click the three dots in the lower right to bring up the menu. Click the hash tag icon in the header to copy the card id. Format like: cu-1234[status].
This is a general idea, but the tree structure for this project is as follows. There may be some issues with the word module in this structure. I may change these names moving forward but the general concept will be held to.
src - the source folder created by npx create app
actions - folder for redux actions
auth - folder dealing with auth
data - folder for data such as database
hooks - folder for custom hooks
reducers - reducers for redux
routing - any hook or utility built for routing
utilis - utility or helper built
components - folder holds pages and parts of pages
elements - for individual pieces parts
modules - base component assembled in part from elements
constants - parts of the page shown on all pages
layouts - can be considered a page layout
forms - folder for any forms built
- src
- actions
- auth
- data
- hooks
- reducers
- routing
- utilis
- components
- elements
- alert
- spinner
- button
- modules
- info_card
- show_card
- header (hero)
- constants
- navbar
- footer
- layouts
- main_page
- about_page
- projects_page
- forms
- contact
- login
- register
- elements
I use a extension called better comments so you may see a funny syntax in the comments. With the extension these comments are highlighted in different ways.
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify