Skip to content

Commit

Permalink
Add test.md
Browse files Browse the repository at this point in the history
  • Loading branch information
SasikaA073 committed Apr 11, 2024
1 parent 2c37602 commit 43ffbc9
Show file tree
Hide file tree
Showing 5 changed files with 334 additions and 114 deletions.
2 changes: 1 addition & 1 deletion docs/en.search-data.json
Original file line number Diff line number Diff line change
@@ -1 +1 @@
{"/test/":{"data":{"":"","how-to-get-started#How to get started":"How to get started\rClone the Repository:\nDevelopers should start by cloning the repository to their local machine: git clone https://github.com/mora-bprs/mora-bprs.github.io.git\rNavigate to the Hugo Site Directory:\nOnce cloned, developers should navigate to the directory where the Hugo site is located: cd mora-bprs.github.io\rInstall Hugo:\nDevelopers need to have Hugo installed on their local machine. They can follow the installation instructions provided on the official Hugo website. Start Editing the Site:\nDevelopers can start editing the Hugo site by modifying the content files located in the content directory. They can use Markdown syntax to write content and make changes as needed. Preview Changes Locally:\nTo preview their changes locally, developers can run the Hugo development server: hugo server -D\rThis command starts a local web server, and developers can view the site in their web browser at http://localhost:1313. Commit Changes to the “dev” Branch:\nAfter making changes, developers should commit their changes to the “dev” branch: git checkout dev\rgit add .\rgit commit -m \"Description of changes made\"\rgit push origin dev\rSubmit Pull Requests (Optional):\nIf your workflow involves code reviews, developers can submit pull requests from the “dev” branch to other branches (e.g., “main” for production). This allows for review and collaboration before merging changes. Deploy to Production (Optional):\nOnce changes are ready to be deployed to production, you can merge the “dev” branch into the appropriate branch (e.g., “main”) to trigger a deployment. By documenting these steps, developers will have a clear understanding of how to clone, edit, and push updates to the Hugo site hosted in the “mora-bprs.github.io” repository, helping to streamline the development process."},"title":"How to get started"}}
{"/test/":{"data":{"":"","how-to-get-started#How to get started":"How to get started\rClone the Repository:\nyou should start by cloning the repository to their local machine:\ngit clone https://github.com/mora-bprs/mora-bprs.github.io.git\rNavigate to the Hugo Site Directory:\nOnce cloned, you should navigate to the directory where the Hugo site is located:\ncd mora-bprs.github.io\rInstall Hugo:\nYou need to have Hugo installed on their local machine. They can follow the installation instructions provided on the official Hugo website. Start Editing the Site:\nRefer to this hugo theme documentation to edit the pages. You can start editing the Hugo site by modifying the content files located in the content directory. They can use Markdown syntax to write content and make changes as needed. first create a folder with the slug name in the content folder, then create an index.md file in that folder and write the content in it.\ntemplate for index.md file:\n--- title: \"Title of the page\" date: 2024-03-03 authors: - name: imfing link: https://go.io tags: - Markdown - Example - Guide draft: false --- ## Sample Markdown content Here write the content of the page in markdown syntax.\rPreview Changes Locally:\nTo preview their changes locally, you can run the Hugo development server: hugo server -D\rThis command starts a local web server, and you can view the site in their web browser at http://localhost:1313.\nGenerate the changes locally:\nTo generate the changes locally, you can run the Hugo command: hugo --destination docs\rThis command generates the static files in the docs directory.\nCommit Changes to the “dev” Branch:\nCreate a branch named dev when you run this for the first time.\ngit checkout -b dev\rIf this is not your first time working with dev branch do the following.\nAfter making changes, you should commit their changes to the “dev” branch:\ngit checkout dev git add . git commit -m \"Description of changes made\" git push origin dev"},"title":"How to get started"}}
Loading

0 comments on commit 43ffbc9

Please sign in to comment.