libscie / open.libscie.org Goto Github PK

JavaScript 100.00%

open.libscie.org's Introduction

Open.libscie.org

This is an Observable Framework project. To start the local preview server, run:

npm run dev

Then visit http://localhost:3000 to preview your project.

For more, see https://observablehq.com/framework/getting-started.

Project structure

A typical Framework project looks like this:

.
├─ docs
│  ├─ components
│  │  └─ timeline.js           # an importable module
│  ├─ data
│  │  ├─ launches.csv.js       # a data loader
│  │  └─ events.json           # a static data file
│  ├─ example-dashboard.md     # a page
│  ├─ example-report.md        # another page
│  └─ index.md                 # the home page
├─ .gitignore
├─ observablehq.config.js      # the project config file
├─ package.json
└─ README.md

docs - This is the “source root” — where your source files live. Pages go here. Each page is a Markdown file. Observable Framework uses file-based routing, which means that the name of the file controls where the page is served. You can create as many pages as you like. Use folders to organize your pages.

docs/index.md - This is the home page for your site. You can have as many additional pages as you’d like, but you should always have a home page, too.

docs/data - You can put data loaders or static data files anywhere in your source root, but we recommend putting them here.

docs/components - You can put shared JavaScript modules anywhere in your source root, but we recommend putting them here. This helps you pull code out of Markdown files and into JavaScript modules, making it easier to reuse code across pages, write tests and run linters, and even share code with vanilla web applications.

observablehq.config.js - This is the project configuration file, such as the pages and sections in the sidebar navigation, and the project’s title.

Command reference

Command	Description
`npm install`	Install or reinstall dependencies
`npm run dev`	Start local preview server
`npm run build`	Build your static site, generating `./dist`
`npm run deploy`	Deploy your project to Observable
`npm run clean`	Clear the local data loader cache
`npm run observable`	Run commands like `observable help`

open.libscie.org's People

Contributors

Watchers

open.libscie.org's Issues

`cron` jobs explore

In BlitzJS, I would use our own instance of Quirrel to run cron jobs. Is this still the best way to move forward in the Redwood case?

Quirrel was bought by netlify, where we deploy the app - potentially Scheduled functions would be of help here. If we are finding a new way to implement them, may just as well run it on still maintained infra instead.

Webhook GitHub organization

I want to still add a webhook for any push events on the libscie organization here on GitHub.

This is similar to #3. The organization webhooks can be found in the settings (if you have access), including example payloads. For more information on webhooks in Redwood, view the docs on webhooks and the docs on serverless functions.

Add workflow to add cash

It would be great to have an easy way to add new values to our historic dataset.

We can use input for actions like we used in force11's upstream

https://github.com/force11/upstream/blob/main/.github/workflows/webhook.yml

Backlog GitHub push events

We've done a bunch of work since our founding in 2019 on GitHub, which would be fantastic to reveal in our documentation.

We can use the GitHub API, octokit.js, and consult the docs to realize this.

The base url to do this from is https://api.github.com/repos/libscie/open.libscie.org/events, I believe.

Create a dev reference of all the common Redwood actions

yarn redwood dev
yarn rw dev

yarn rw g types

yarn redwood generate page <name> <path?>
yarn rw g scaffold <component>
yarn rw g sdl <model>

yarn rw setup auth dbAuth
yarn rw g dbAuth

yarn rw prisma migrate dev
yarn rw prisma studio

yarn rw g secret

yarn rw setup deploy netlify

Webhook `libscie.org`

I still want to add processing of a webhook for libscie.org, to automatically add any writing done for our blog.

This will require:

Setting up the webhook
Setting up a serverless function to receive the webhook
Expanding the database schema to capture a new type in the logs

Activity schema model

model Activity {
  id   Int @id @default(autoincrement())
  createdAt DateTime @default(now())
  value
  emissions
  title
  description
}

Backlog cash on hand

We're currently only reporting on cash on hand at the very beginning, and currently. It would be great for historic overview to add the (estimated) cash on hand since the founding in 2019.

libscie / open.libscie.org Goto Github PK

open.libscie.org's Introduction

Open.libscie.org

Project structure

Command reference

open.libscie.org's People

Contributors

Watchers

open.libscie.org's Issues

`cron` jobs explore

Webhook GitHub organization

Add workflow to add cash

Backlog GitHub push events

Create a dev reference of all the common Redwood actions

Webhook `libscie.org`

Activity schema model

Backlog cash on hand

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent