Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: minimal theme #93

Open
wants to merge 170 commits into
base: main
Choose a base branch
from
Open

Conversation

kimlimjustin
Copy link
Contributor

Added the first theme for the public page, a minimal theme.

zicklag added 30 commits May 6, 2024 14:36
zicklag and others added 25 commits June 24, 2024 18:58
This PR adds a bit more copy to the landing page based on commune-os#36.
Integrating mastodon profile into weird, we'll generate a site for the
users. Here's how:
1. Link account with Mastodon's server
2. Authorize the user
3. Happy ending :)

![image](https://github.com/commune-os/weird/assets/61906684/e3751f44-7ed4-41b5-aa40-ff006b17673c)

![image](https://github.com/commune-os/weird/assets/61906684/2c5f7a9d-912d-4705-9451-05cc79bbff68)

The link is discoverable under the member page

![image](https://github.com/commune-os/weird/assets/61906684/ac1b9fbb-79a1-4533-adc3-403ed948e153)
Fix double links and descriptions in the members card and saving profile
deleting mastodon username bugs
This PR removes emojis from card titles on the landing page and moves
the "milk and honey" emojis below the cards based on feedback from
Erlend.

Before: 

![weird one_
(3)](https://github.com/commune-os/weird/assets/33972521/e12d3393-43b9-43c3-ad49-770b09dcfd36)


After:

![localhost_9523_
(1)](https://github.com/commune-os/weird/assets/33972521/f893226e-e1e1-4356-991b-ee240f828b78)
This change moves the app into a separate route group
and adds rewrite rules so that sub-domains of the main
site will be rendered.

The subdomains don't load user data right now, though.
Enable the dissociation of an external authentication provider for users
who have previously linked both password and provider credentials
@kimlimjustin kimlimjustin marked this pull request as ready for review July 13, 2024 17:59
@kimlimjustin
Copy link
Contributor Author

Pushed a commit that supports the inline editing feature directly on the public page with the following algorithm:

  1. When a user is logging in, we pass the user to a worker page to save its csrfToken and also a variable justLoggedIn, telling that the user is logging in, to the cookies.
  2. The user will be redirected to Rauthy's default authorization URL to handle the logging-in process.
  3. After the user is logged in and redirected to the account page, a quick condition checker will run to check if the user just logged in via the justLoggedin cookie value. If that's true, we'll fetch a token for the user and the user will be redirected to the public page's pubpage-auth-callback page together with token and cookies as the queries.
  4. Through the pubpage-auth-callback page, the cookies and token will be saved locally in the pubpage's cookies.
  5. Whenever the pubpage is loaded, a quick checker will be run to confirm whether it's the author (aka who has the correct token) who is visiting the page. If it's true, then the content will be displayed in contentEditable format, giving the user the ability to edit the content directly.
  6. The users can save their change by clicking the submit button that will trigger a POST request to the /account/update endpoint.

Technical-wise, I've modified the account/update page to enable token-powered post request. Some essential changes in the backend were also made so that everything worked correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants