We need a way to identify broken URLs so they can be quickly fixed.

If someone changes a heading i.e.

## My First Heading

to

## My New Heading

It will break any jumplink URLs that point to the previous heading title i.e. /page#my-first-heading needs to be updated to say /page/#my-new-heading

The only way I’m aware of is to do a find & replace to change URLs from /page/#my-first-heading to /page/#my-new-heading

TRIAGE

It says Slack app is installed in GitHub Settings but when trying to use the /subscribe slash command it says I need to connect my GitHub account

Get @bigolboyyo's fork onto docusaurus.climatetechhandbook.com

Going to try this in Miro

So currently we are using a widget from clock and it has default styling:

We really only want the top Deadline bar. We don't need it to be red/black either.

I propose starting off with some basic styling. Make it fit into the home page better. Consider putting it at the top of the page. Or working with anyone associated with the layout issue: #30

My second thought is start doing research on a custom climate clock. Start off by gathering resources we could use, ie Nasa API, weather api, etc. Prototyping out a basic design or even pseudo code out the logic. This issue is meant to be a starting point for brainstorming as well.

Maybe work this into a custom weather widget that shows average increase in comparison with carbon output year after year (just an idea), feel free to be creative and shoot a stream of consciousness at this one.

The climate clock will be our main "call to action" on our homepage. The "why" it matters you join the movement today!

Fill below:

• Nav buttons
• Hero slogan
• Footer content
• Card titles & sentences
• Site title (add "The")

Hero Slogan

Version A: current website tagline

We are here to help you answer the most important question in the world:
How am I going to make a difference?

Button says: Find out

(This version depends on having a section with two font sizes, smaller for sentence 1 and larger for sentence 2.)

Version B:

We’re building the most accessible and accurate climate tech resource on the planet.

Button says: Show me

Top row navigation

• The Climate Tech Handbook (Has "The" in it)
• Climate Job Seekers
• Climate Startups
• About Us
• News

Footer

• Remove Technologies under Resources
• Under solutions, change text to List of climate solutions

Card Titles and Paragraph

Climate Job Seekers

Becoming a climate expert feels daunting.

But it's easier than you think.

If you don't currently work in tech, you also have options.

Button says: We can help

Climate Startups

The climate tech landscape is changing rapidly.

Founders, investors, philanthropists, and government funders - all have a responsibility to spend money wisely.

Our future depends on it.

Get the best information possible on what's working, and what to avoid.

Button says Show me

As title states the plan is to aggregate a list of rss feeds into the 13 sectors associated with our solutions.

Here's a list of feeds I've started gathering:

https://grist.org/feed/
https://arstechnica.com/tag/climate-change/feed/
https://www.desmog.com/feed/
https://techcrunch.com/tag/climate-tech/feed/
https://www.carbonbrief.org/feed
https://www.greenbuildingadvisor.com/feed
https://www.sciencedaily.com/rss/earth_climate.xml

Additionally we can use these google feeds to watch each company in our growing list of resources!

"and don’t forget there’s an RSS url pattern for every single Google News search" - @futuresoup 

For the organization “One Tree Planted”
https://news.google.com/search?q=%22One%20Tree%20Planted%22&hl=en-US&gl=US&ceid=US%3Aen
https://news.google.com/rss/search?q=%22One+Tree+Planted%22&hl=en-US&gl=US&ceid=US:en

Current Progress

I am using Vercel serverless functions for now and grabbing data from a climateTechFeeds array. Once @shreeup get's our flask app finalized I'll move towards transposing it to an api endpoint in our flask app if/when needed.

If Vercel ends up working standalone for this that's fine too.

mvp code

import { VercelRequest, VercelResponse } from '@vercel/node';
import fetch from 'node-fetch';
import { parseStringPromise } from 'xml2js';
import { climateTechFeeds } from '../data/climateTech';

export default async function (req: VercelRequest, res: VercelResponse) {
  const allowedOrigins = ['http://127.0.0.1:8000', 'https://www.climatetechhandbook.com'];
  const origin = req.headers.origin || "";
  if (allowedOrigins.includes(origin)) {
    res.setHeader('Access-Control-Allow-Origin', origin);
  }
  res.setHeader('Access-Control-Allow-Methods', 'GET');

  // Fetch and parse RSS feeds
  const parsedFeeds = await Promise.all(
    climateTechFeeds.map(async (feed) => {
      const response = await fetch(feed.urls[0]);
      const xml = await response.text();
      const json = await parseStringPromise(xml);
      return { ...feed, items: json };
    })
  );

  res.status(200).json(parsedFeeds);
}

My Current Ongoing Development

• Gather as many "climate tech" related feeds as possible.
• Gather them all into one unified bridge
• Parse through the massive bridge and separate into 13 sectors

How to help

• Gather more feeds into a master list
• Start designing UI/UX for the end feed (integrate to mkdocs? separate standalone html doc? separate app framework all together?)
• Start planning integration with @Yinan0409's fine tuning progress (how are we going to train based off of these feeds)
• start gathering a list of Google rss feeds for each associated job we have in our google drive documents (a quick script could probably handle this)
• Make suggestions, more specific issues, feature requests, and get involved. Even comments and discussion is highly encouraged

Now that the CRM is working, let's update cover photos for each Solution page based on the ones picked by @Muxi0630

Just a place to brainstorm

Two inspirational examples that I’m looking at for a fancier design:

• The Material For MKDocs website has a decent homepage and because they’re using our exact same platform, we have the code.

• The OpenEarth Foundation as some pretty schnazzy elements. Probably a bit overkill if we go to bedazzled though. At least for now.

The OAuth app currently has very broad permissions which can scare off contributors.

A GitHub App has fine grained permissions to only access necessary things when a contributor installs it to use the CMS.

In addition to the climate countdown clock - which can be depressing for people, we should have a motivational ticker as well for progress that's been made.

They have something similar on climateclock.world

We can put our own stats though based on news we learn about the solutions on the website, like dollars invested, jobs open, etc.

It's time to get the dirty Data Magic repo cleaned up and merged into our primary repo.

@ArLough is leading this, with advisory assistance from @bigolboyyo, @justBanks, and @shreeup

Tasks:

• Copy over the Flask back-end (App folder)
• Migrate Issue tickets over
• Get the Flask app deployed and API accessible
  • Option A: using onrender.com via @shreeup's instructions in comments below (requires paid subscription)
  • ?? Research a free option or a paid option with a free open source license ??
• Create a production branch and deployment workflow
• Rename "Data Magic" repo to "Playground" for running community experiments and testing @Yinan0409's AI model
• Update documentation
• File ticket to set up Replit

We really need a CMS to collaborate with writers who can't figure out GitHub, Git, or raw Markdown workflows.

(I brought this up in the Material for MKDocs forum).

Decap CMS is an open source CMS that should work great for MKDocs.

How could this be implemented?

If it's too hard or not possible, we could try to be creative.

For example, authoring in Notion and using their API? Some sort of notebook environment? The GitHub GUI?

Goal: allow writers to author & collaborate with Notion as a wiki CMS

Implementation: use the Notion API to sync Handbook pages into a Notion workspace.

Details (work in progress)

• Possibility - Docu-notion on GitHub

• Bi-directional sync? Perhaps start with a one way sync from The Handbook pages to Notion if that's easier to implement. Once the page updates are complete on the Notion side, a Notion page can be manually exported to Markdown for Handbook integration in the other direction

@dovid11564 thanks for your help with this.

We are migrating from Material MKDocs.

Current docs are in /docs of the main repo.

We are going to put them in /docs of the docusaurus-test repo and account for quirks like:

Primary goals

1. Migrate
2. Standarize formatting i.e. callout boxes (admonitions)

Details

- [x] changing the admonition syntax

• having the sidebar appear on pages that aren't actually listed in sidebar.js
• filling in front matter properly - for example description: field
• ...more things to uncover...

Might need ideas on managing build minutes in Netlify now that the CMS is constantly doing stuff.

Slack Message

For @alexmayberry

• Every time a change saves it unpublishes. Any way around that? Is it actually taking the page down and therefore requiring each save to go through a republish?

• Fix the { in the file name

• Get the PRs from GitHub in the person’s name who’s making the edits. Currently it’s all under Alex Mayberry

• Get the permissions hierarchy put in place. I think anybody can currently publish and merge PRs into Main

• Initiate a mass update through the backend Flask system to get the front matter formatted so the pages work in the CMS

• Fix weird Issue labels that are generated

• Fix page titles

For @Muxi0630

Play around and report what you find.

The table of contents only displays on Desktop.

For better mobile usability, it should also be accessible via flyout from an icon on the top right header bar.

You can see an example with the "Read the Docs" layout.

Make the window responsive and look at the top right.

Pages

• Intro
• How to use the handbook
• Job seekers
• Contribute page
• Resources page / video
• Add Muxi's 2 pages + Fan's Rice page
• New Sectors/Solutions - finance, data, methane leak management

Tasks

- [X] Fix syntax - font-awesome/material icons

• fix additional instances of :font-awesome: and :material: syntax
• Fix admonitions
  - [X] File solutions explorer ticket
• Add sidebar to all page front matter
• Remove solutions explorer link from Plant Rich page or fix first
• Fix footer names/URLs
• Fix footer icons/URLs
• Fill in Blog
• Emoji for each solution in menu bar (?)
• How to fix "Next Page" - skips over solutions.tsx to electricity.md

See #4 - we need to reconcile the Markdown formatting of template.md

It would be great if we could add an autocompleting tooltip for the editor that suggests links to internal pages when editors type double square brackets [[ ]] similar to internal linking functionality in other md editors like obsidian.

This would reference page titles rather than file paths.

Transportation works (see title of the tab)

But Land Sinks and other Sectors don't.

Latest design here.

Highest Priority

• decide on removing sticky navigation for Table of Contents dropdown - @sbasken
• Convert Solutions page to solutions.md and optimize
• Get sidebar on all pages - @futuresoup
• Repo cleanup, documentation, issue migration - @futuresoup
• Set up previous and next pages on all Solution pages - @futuresoup
• Finish 0.9 content and stage 1.0 content draft workflow - @futuresoup
• Reorder social icons
• Fix sidebar emoji gap
• Icon image bug is back! - @sbasken
  • Sizing - @sbasken - LinkedIn, GitHub, add Slack (chat.climatetechhandbook.com)
• Remove breadcrumbs until we figured out #220 @futuresoup
• Clean up contacts and outreach plan - @futuresoup
• Get meta description: to be automatically filled with the first few sentences in front matter. I don't believe this is happening which is messing up SEO and social media sharing. Need to confirm first though.

Content - @futuresoup

• Intro page
• Career guide page
• Sector descriptions
• About page (Vision, Team)
• Solutions landing page
• Resources page
• Meta description for Google and link previews
• Blog post
• Image card for /sector-health-and-education
• Test DecapCMS
• Contribute page with Patreon working
• Sweep through all Solution pages
  • Reorder by solution size and visualize with #106 and other techniques
• File ticket for role related pages
• File tickets for Level 0,1,2 content + Muxi/Fan/Neel's content
• File ticket for two new sectors - financing, data & accountability
• File routine scrub for new internal links and pages

Meta

• #123 + Docusaurus repo with documentation and team announcement
• Get Figma file migrated and test + invite everybody + integrate content map JamBoard
• Update iterations, end dates, and milestones -> move tasks to v1.0 release

Secondary Priority

• Get social icons up
• Design for Previous and Next page navigation at the bottom of each page
• Try new Hero image
• A/B test tagline and homepage content
• File ticket for contribution video guide

CSS changes

Mobile

• Tighten gap between bottom of clock and image card picture so the user can see the top of the picture and knows they can scroll - @thenunachi
• Make "Next Page" and "Previous Page" far more obvious - @sbasken
• Some pages still have horizontal scroll issue
  • Perhaps related to things like YouTube video too wide in /career-guide page
• Search bar requires manual zoom out after using (don't think we can fix)
• New search bar fit is still a little off. Doesn't say "search" completely, and needs to be tested on multiple screens.
• Tighten uneven gap between Slack and the other footer icons so they're even
• See if there's room for "The" versus no "The" in the navbar. Perhaps "The" appears on Desktop but not mobile for space considerations - @thenunachi
• Hero fonts look small and a little weird
• Hero "Show me" button is too small, and should look more prominent, and perhaps more centered.
• Clock doesn't quite fit right still. Perhaps squeeze colons together a tad more? Ideally we could spell out "Years" instead of "Yrs" and leave the other abbreviations, which don't matter as much.
• Spacing gap between Job Seeker and Founders section appears to big and should be tightened.
• Some pages still has horizontal bouncy effect when scrolling with finger (if finger deviates sideways)

General

• Styling and markdown for image captions -@dovid11564
• Fix inconsistent image alignment on image cards - @sbasken
• Weird skinny fonts and sidebar text spacing on Chrome/Safari versus normal in Firefox
• Odd button width discrepancy on homepage with top "Show me" and Bottom "Find Out" - @thenunachi
• images way to big and image cards not aligned correctly underneath for Sector pages, such as sector-transportation
• Make navbar fonts larger on Desktop for legibility and accessibility
• Slightly more prominent border around "Next Page" and "Previous Page" buttons
• Button text should be white not black
• Button's disappear on hover ONLY IN PRODUCTION NOT LOCALHOST
• Line break for second sentence on "job seekers" image card so each sentence gets its own line
• Table of contents - highlight as you scroll down the page, like on the Climate Papa post

Solution page & sub-pages

• Fix Solution cards (Figma Design)
• Make entire card clickable, ideally with hover effect to make it more noticeable and pleasant.~
• Content - 14 sectors and 93 solutions with image, title, and one sentence description
• Update arrow design
• Work on arrow alignment

Later

• Clean up front matter and file ticket for standardization
• Feedback on previous/next buttons at bottom of page, and styling
• File ticket for Algolia - @futuresoup
• Social media previews - og:image and page description (LinkedIn, Slack, etc)
• File ticket to investigate scrunched up elements on mobile Slack App, iPhone SE newer generation (see screenshot)
• File ticket for dropdown bar to filter solution cards
• File ticket for menu to fade out on mobile during scroll
• Get image zoom working (turn plugin back on in docusaurus.config.js)
• File ticket to deal with displayed_sidebar problem
• DevOps - set up develop and staging branches to auto-deploy to dev and staging sites
• #217
• File ticket to try Framer for landing page test and update #149
• File ticket for making sidebar and scroll up circle a little more obvious
• File ticket to test sharing display on popular social platforms
• SEO Audit
• Audit: code quality / tech debt potential

Attempting to install both mkdocs and markdown from the requirements.txt file yields:

ERROR: Cannot install -r requirements.txt (line 12) and Markdown==3.4 because these package versions have conflicting dependencies.

The conflict is caused by:
    The user requested Markdown==3.4
    mkdocs 1.4.3 depends on markdown<3.4 and >=3.2.1

Currently very bare.

We can start with:

• Image
• Two sentences
• 3 bullet points

Some background info on the sectors are available at Project Drawdown's Sector page

It looks like DecapCMS supports a link to "Edit this Page" which allows people to contribute pull requests with content updates through the DecapCMS editor.

That would be a great way to encourage more content contributions.

It also saves time because you don't have to find the page in the backend. Simply edit it from the front end!

Here's a page where you can see the "Edit this page" link:

https://decapcms.org/docs/docusaurus/

Immediate Pass

• Set up Project Boards

• Set up Project Views

  • Study tutorial video
  • Implement template and update all 5 projects

• Set up all Milestones

  • Filter and ensure all Issues have assigned Milestones

• Set up all Labels

  • Color and categorize labels - similar to this video

• Set up Iterations

  • Figure out how they work...

• Full Issue cleaning!

  • Filter all Issues, see if the following are missing:
    • Project
    • Assignee
    • Milestones
    • Labels
      • Storypoints
    • Working branch / file

• Team training

  • File in correct repo (Website or Data assistant)
  • Ensure all issues created have two projects (release, and category)
  • Labels, Milestone
  • Self assign whenever possible
  • Add branch when ready

Schedule

Day 1: User Personas

Task: Create user personas to understand your target audience and their needs.
Approach: Research your target market, conduct interviews or surveys, and compile the data into user personas.

• Pomodoro Focus Session:
  • Research target market and gather data.
  • Analyze data and identify common characteristics.
  • Create user persona profiles based on the gathered information.
  • Validate the user personas with stakeholders or potential users.

Recommended Resource: The User Persona Template: A Guide For Agile UX Designers by Jerry Cao

Day 2: User Stories

Task: Define user stories to capture specific user needs and requirements.
Approach: Break down the user personas into actionable user stories that represent user goals, actions, and desired outcomes.

• Pomodoro Focus Session:
  • Review the user personas created on Day 1.
  • Identify key user goals and actions.
  • Formulate user stories using the "As a [user], I want [action] so that [outcome]" format.
  • Prioritize user stories based on importance and impact.

Recommended Resource: User Stories Applied: For Agile Software Development by Mike Cohn

Day 3: Epics

Task: Define epics, which are high-level user stories that represent large features or functionalities.
Approach: Identify overarching themes or major functionalities required by users and break them down into epics.

• Pomodoro Focus Session:
  • Review the user stories created on Day 2.
  • Group related user stories into thematic categories.
  • Define high-level epics that encapsulate each category.
  • Validate and refine the epics with stakeholders or potential users.

Recommended Resource: Agile Product Management with Scrum: Creating Products that Customers Love by Roman Pichler

Day 4: Issue Tickets & Tasks

Task: Convert user stories and epics into granular issue tickets and tasks.
Approach: Break down epics and user stories into smaller actionable tasks that can be assigned to team members.

• Pomodoro Focus Session:
  • Review the epics and user stories created on Day 3.
  • Break down each epic and user story into smaller tasks.
  • Create issue tickets or tasks in your preferred project management tool.
  • Prioritize and assign tasks to team members, considering dependencies and resources.

Recommended Resource: The Agile Samurai: How Agile Masters Deliver Great Software by Jonathan Rasmusson

Day 5: Milestones & Sprints

Task: Define milestones and plan sprints for the development process.
Approach: Determine significant milestones in the project timeline and organize tasks into sprints for iterative development.

• Pomodoro Focus Session:
  • Review the issue tickets and tasks created on Day 4.
  • Identify major milestones or checkpoints in the project timeline.
  • Organize tasks into sprints, considering their priority and dependencies.
  • Create a sprint plan and allocate tasks to specific sprints.

Recommended Resource: Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days

It's just about ready - here is @bigolboyyo's personal repo that needs to be moved

just needs a dev review from @shreeup @connor-cs @airbr

To Do

• Someone please claim this in a comment below for Friday release @shreeup @connor-cs @airbr

• Add notice in README that it's not the live website, but a testing site for our migration available at docusaurus.climatetechhandbook.com (Password: test)

• Ensure it runs locally and README makes sense for new dev contributors

• Anything I'm missing?

Developers, please fix those links, whenever you have time. Because it directly affects the SEO rankings of the website

We need to get a real assessment on where the major holes are in our new CMS capability, and how easy/hard they will be to implement a fix.

For example:

• Is there a somewhat decent collaboration workflow out there? What would it take to implement a workaround and move towards a native solution?

• Are standard permissions controls just not there?
  I’ll put together a ticket for that task soon.

• Generate list of what we're testing for - @DustinBr
• Create test URL for UsabilityHub - @UlianaBil
• Recruit and execute test - (TBD)

Currently buttons are only available in the primary green color.

We need another set of two buttons for the secondary color.

You'll notice by hovering over an existing button (do this on the homepage, and you'll see the secondary purple upon hover.

We just need a new button class with this behavior reversed so instead of green primary / purple hover, the secondary set of buttons has a purple primary / green hover

This is easily done by adding to the docs/extra.css file

Hoping for another option besides Algolia. I'm a bit confused about the options.

Here is the draft OKR Sheet.

• Instructions in Decap.

• Need to figure out Docusaurus configuration

Here are companies/organizations working in this sector on ClimateBase for some inspiration.

Also Wikipedia’s page on Climate Adaptation.