Ola Rubaj 688db3e6a6
Changesets setup + auto-publish to npm (#922)
Closes #905 

## Summary

This PR sets up changesets with the aim to simplify the process of documenting changes committed to the codebase, as well as automating versioning packages and publishing them to npm.

## Changes
- initialised [changesets](https://github.com/changesets/changesets) in the repository
- (separately from this PR) installed [changesets bot](https://github.com/apps/changeset-bot) in the repository (it will check if a submitted PR includes a changeset file and inform if found or not)
- added `.github/workflows/release.yml`: The workflow creates a PR with version bumps and related changelog
files' updates, each time a commit containing changeset
file(s) is added to the main branch. After merging this auto-generated PR, this workflow will also auto-publish the released packages to npm and add git tags.
- added the following scripts to the root `package.json`:
  - `changeset`: should be run to generate changeset files, that describe changes made to the code,
  - `prerelease`: runs linting and testing on packages affected by the changes in a PR
  - `release`: runs `changeset publish` and is used by the `release` workflow then the above-mentioned auto-generated PR is merged to the main branch
2023-06-05 17:41:37 +02:00
2023-06-02 18:59:04 -03:00
2023-04-10 22:22:34 -03:00
2023-05-19 11:15:52 +02:00
2023-04-12 09:37:04 -03:00
2023-04-10 22:22:34 -03:00
2023-04-11 13:23:53 -03:00
2023-04-11 13:23:53 -03:00
2023-04-12 09:13:17 -03:00
2023-04-26 14:44:56 -03:00
2023-04-11 13:23:53 -03:00

🌀 Portal.JS
Rapidly build rich data portals using a modern frontend framework

What is Portal.JS

🌀 Portal.JS is a framework for rapidly building rich data portal frontends using a modern frontend approach. Portal.JS can be used to present a single dataset or build a full-scale data catalog/portal.

Built in JavaScript and React on top of the popular Next.js framework. Portal.JS assumes a "decoupled" approach where the frontend is a separate service from the backend and interacts with backend(s) via an API. It can be used with any backend and has out of the box support for CKAN.

Features

  • 🗺️ Unified sites: present data and content in one seamless site, pulling datasets from a DMS (e.g. CKAN) and content from a CMS (e.g. Wordpress) with a common internal API.
  • 👩‍💻 Developer friendly: built with familiar frontend tech (JavaScript, React, Next.js).
  • 🔋 Batteries included: full set of portal components out of the box e.g. catalog search, dataset showcase, blog, etc.
  • 🎨 Easy to theme and customize: installable themes, use standard CSS and React+CSS tooling. Add new routes quickly.
  • 🧱 Extensible: quickly extend and develop/import your own React components
  • 📝 Well documented: full set of documentation plus the documentation of Next.js and Apollo.

For developers

  • 🏗 Build with modern, familiar frontend tech such as JavaScript and React.
  • 🚀 Next.js framework: so everything in Next.js for free: Server Side Rendering, Static Site Generation, huge number of examples and integrations, etc.
    • Server Side Rendering (SSR) => Unlimited number of pages, SEO and more whilst still using React.
    • Static Site Generation (SSG) => Ultra-simple deployment, great performance, great lighthouse scores and more (good for small sites)

Docs

Access the Portal.JS documentation at:

https://portaljs.org/docs

Community

If you have questions about anything related to Portal.JS, you're always welcome to ask our community on GitHub Discussions or on our Discord server.

Appendix

What happened to Recline?

Portal.JS used to be Recline(JS). If you are looking for the old Recline codebase it still exists: see the recline branch. If you want context for the rename see this issue.

Description
🌀 Rapidly build feature-rich data portals using a modern frontend framework. CKAN compatible.
Readme 104 MiB
Languages
TypeScript 69%
JavaScript 20.1%
CSS 10.6%
Shell 0.3%