Apply upgraded theme features to the site

Signed-off-by: Chris Abraham <[email protected]>

.gitignore

@@ -7,3 +7,4 @@ static/css/style-*.css
 .sass-cache/
 .hugo_build.lock
 *.code-workspace
+static/pagefind

Makefile

@@ -16,6 +16,7 @@ production-build:
 	git submodule update --init --recursive
 	hugo \
 		--minify
+	npx -y pagefind --site public"
 
 preview-build:
 	git submodule update --init --recursive
@@ -24,3 +25,4 @@ preview-build:
 		--buildDrafts \
 		--buildFuture \
 		--minify
+	npx -y pagefind --site public"

README.md

@@ -67,6 +67,13 @@ npm run build
 npm run start
 ```
 
+## Other npm commands for working with a local instance
+
+- `npm run dev:start` - Starts the local dev environment using exampleSite
+- `npm run dev:start:with-pagefind` - Starts the local dev environment using exampleSite with working pagefind search
+- `npm run dev:build` - Builds the site using exampleSite
+
+
 This command should give an address you can visit on your local machine to see the local copy of your site. Typically this is `localhost:1313`. Just navigate to http://localhost:1313 in your browser and you should see the site running.
 
 If modifying the theme files, you should never edit the themem that is imported via Git Submodule, as otherwise the changes will be overwritten or lost the next time the theme is updated. Changes should be made in override files inside the root directory as this will override the theme directory. [Read docs](https://gohugo.io/getting-started/directory-structure/).

config/_default/params.yaml

@@ -33,3 +33,8 @@ social_links:
   twitter: ""
   x: "https://twitter.com/todogroup"
   youtube: "https://youtube.com/@ospology"
+
+# Makes the header sticky on tall screens
+sticky_header: true
+# Enable search in header UI
+show_search: true

content/en/faq/benefits.md

@@ -1,6 +1,7 @@
 ---
 title: What are the benefits of being a TODO General Member?
 weight: 50
+noindex: true
 ---
 
 Please take a look to the [TODO Group Overview Presentation](https://docs.google.com/presentation/d/1p4dhx0Dg8fZDO8yzp7nWC2r5WHyVH-jjSQM59lkKLdo/edit?usp=sharing) to learn more about General Membership benefits.

content/en/faq/communication-channels.md

@@ -1,6 +1,7 @@
 ---
 title: Which are the main communication channels?
 weight: 90
+noindex: true
 ---
 
 Please visit our [communication channel](/community/comms/) page to learn more.

content/en/faq/deliverables.md

@@ -1,6 +1,7 @@
 ---
 title: What deliverables can we expect to see from this project?
 weight: 80
+noindex: true
 ---
 
 Our plans include work such as:

content/en/faq/get-involved.md

@@ -1,6 +1,7 @@
 ---
 title: How can I start getting involved in the TODO Community?
 weight: 100
+noindex: true
 ---
 
 Please visit our [Get Started page](/community/get-started/) to learn more

content/en/faq/get-updates.md

@@ -1,6 +1,7 @@
 ---
 title: How can I stay up to date with TODO?
 weight: 120
+noindex: true
 ---
 
 The easiest way is to [subscribe to OSPONews](https://ospo-news.ghost.io/) and follow us on [LinkedIn](https://www.linkedin.com/company/todo-group/)

content/en/faq/government-institution.md

@@ -1,6 +1,7 @@
 ---
 title: As a government institution, can I join the TODO Group?
 weight: 70
+noindex: true
 ---
 
 The TODO Group welcomes any government institution representative willing to collaborate on practices, tools, and other ways to run successful and effective open source programs and open source initatives, as well as to engage in discussions with experienced OSPO professionals.

content/en/faq/open-source-foundation.md

@@ -1,6 +1,7 @@
 ---
 title: Is the TODO Group a new open source foundation?
 weight: 110
+noindex: true
 ---
 
 No. We’re an open source project and a community of practice hosted under the linux Foundation with a common interest who have come together to help solve the problem of building open source programs and open source initiatives within organizations.

content/en/faq/should-i-join.md

@@ -1,6 +1,7 @@
 ---
 title: Should I join?
 weight: 20
+noindex: true
 ---
 
 TODO is specifically intended as a space for organizations' open source program practitioners to come together, but also for people committed to open source willing to learn and get practical knowledge on open soruce program offices and open source initiatives.

content/en/faq/steering-committee-elected.md

@@ -1,6 +1,7 @@
 ---
 title: How is the TODO Group Steering Committee elected?
 weight: 100
+noindex: true
 ---
 
 The TODO Group Steering Committe sets the policy and strategic goals for TODO Group. The Steering Commitee is elected by the TODO Members on a yearly basis.

content/en/faq/todo-community.md

@@ -1,6 +1,7 @@
 ---
 title: Can I be part of the TODO Community without being a TODO Member?
 weight: 40
+noindex: true
 ---
 
 Yes, TODO Group resources are essentially like any other open source project.

content/en/faq/university.md

@@ -1,6 +1,7 @@
 ---
 title: As a university or academic institution, can I join the TODO Group?
 weight: 60
+noindex: true
 ---
 
 Universities can join the TODO Group to collaborate on practices, tools, and other ways to run successful and effective open source programs and open source initatives, as well as to engage in discussions with OSPO professionals.

content/en/faq/which-organisations.md

@@ -1,6 +1,7 @@
 ---
 title: Which organizations are participating?
 weight: 30
+noindex: true
 ---
 
 See the full [list of General Members](/about/members) and [OSPO Associates](/about/associates/).

content/en/faq/whom-is-this-group-for.md

@@ -1,6 +1,7 @@
 ---
 title: Whom is this group for?
 weight: 10
+noindex: true
 ---
 
 The primary purpose of this community and project is to bring together open source practitioners and organizations who run open source programs and open source initiatives to develop and share resources and knowledge in the open.

content/en/search.md

@@ -0,0 +1,6 @@
+---
+title: Search
+description: Search this site using Pagefind
+---
+
+{{< search_form >}}

content/ja/search.md

@@ -0,0 +1,6 @@
+---
+title: Search
+description: Search this site using Pagefind
+---
+
+{{< search_form >}}

content/zh-CN/search.md

@@ -0,0 +1,6 @@
+---
+title: Search
+description: Search this site using Pagefind
+---
+
+{{< search_form >}}

package.json

@@ -6,7 +6,10 @@
   "scripts": {
       "build": "hugo --theme=dot-org-hugo-theme",
       "start": "hugo serve --logLevel info --configDir=config --buildDrafts --buildFuture --ignoreCache --disableFastRender --gc  --printI18nWarnings --printMemoryUsage --printPathWarnings --printUnusedTemplates --templateMetrics --templateMetricsHints",
-      "dev": "hugo serve --logLevel info --configDir=config --themesDir=../.. --buildDrafts --buildFuture --ignoreCache --disableFastRender --gc  --printI18nWarnings --printMemoryUsage --printPathWarnings --printUnusedTemplates --templateMetrics --templateMetricsHints",
+      "dev": "npm run dev:start",
+      "dev:start": "hugo serve --logLevel info --configDir=config --buildDrafts --buildFuture --ignoreCache --disableFastRender --gc  --printI18nWarnings --printMemoryUsage --printPathWarnings --printUnusedTemplates --templateMetrics --templateMetricsHints",
+      "dev:start:with-pagefind": "hugo --baseURL=/ --theme=dot-org-hugo-theme && npm_config_yes=true npx pagefind --site 'public' --output-subdir '../static/pagefind' && npm run dev:start",
+      "dev:build": "hugo --theme=dot-org-hugo-theme",
       "pulltheme": "git submodule update --remote"
   },
   "repository": {