remix-website's People
Forkers
kayac-chang broisnischal sandeshthapa07 mindkhichdi nabinkatwal7 akkikumar72 nazarepiedady fernandocanizo takagimeow utkarshpant pierreberger gustavoguichard folafunmi-db varinliali kazuhiro-mimaki yasu551 yikayiyo arnabsen ag-remix whjvenyl yoshimatsu567 normanwilde lasseklovstad ovi-ispas bonny-kato thetnaingtn alexandromtzg eps1lon titusgahissy jacobparis dendrobiummoniliforme coleea cloudcreatr dirtyhenry sarvesh-ghildiyal alemtuzlak elledienne sravinet byjim saas-kits wouterds seanmcquaid lorissigrist ameh64 chialuka kandros simeongriggs sotabkw derpenstein69 camilo-camargo pavindulakshan toasahi parkermjones forge42dev auto-deploy-landingpage-inspirations johnny-rice kisaragi-hiu jas7457 nichtsam herrbertling tlawrie ihiutch nautman daguitosama boolary tchorzyksen37 anyuruf vanics akazwz ollieri3 devcarolzita kettanaitoremix-website's Issues
Switching theme scrolls to top
Add more template data
Need to add at least 20 templates to the templates.yaml
file
A few other niceties to add in this one
- Validate with zod
- Add
featured
or something similar as a flag to determine which template is featured
Add customers discuss repo again
Render Changelog on the Website
Our Changelog doc is sad
![image](https://private-user-images.githubusercontent.com/12396812/301922170-4f2c7cdd-4415-47bf-82a9-a70834c49994.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQzNjk1NDYsIm5iZiI6MTcyNDM2OTI0NiwicGF0aCI6Ii8xMjM5NjgxMi8zMDE5MjIxNzAtNGYyYzdjZGQtNDQxNS00N2JmLTgyYTktYTcwODM0YzQ5OTk0LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MjIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODIyVDIzMjcyNlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWViZWE1NzBlY2MxNjU4MzU5YWFlMGUxNzE3NWJmYzk0NDY2NWE1YWMxNGM3YjMxODM1YTI1NTU2MmUzNzBiMWEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.XgDizt44hhc5FC4k6pusox8rwbDdRuLb53IG8sj_OUc)
This was a temporary addition, but we would really prefer to render the full doc on our website. Just a matter of fetching the correct file on that specific route instead of what's in the docs.
Create meta tag helper function
Would be nice to have a common set of meta tags that we can use/extend. Maybe just a simple function with some defaults.
The main page (_marketing._index.tsx
) has a nice set of defaults
export const meta: MetaFunction<typeof loader> = (args) => {
let { siteUrl } = args.data || {};
let title = "Remix - Build Better Websites";
let image = siteUrl ? `${siteUrl}/img/og.1.jpg` : null;
let description =
"Remix is a full stack web framework that lets you focus on the user interface and work back through web standards to deliver a fast, slick, and resilient user experience. People are gonna love using your stuff.";
return metaV1(args, {
title,
description,
"og:url": siteUrl,
"og:title": title,
"og:description": description,
"og:image": image,
"twitter:card": "summary_large_image",
"twitter:creator": "@remix_run",
"twitter:site": "@remix_run",
"twitter:title": title,
"twitter:description": description,
"twitter:image": image,
});
};
I think we could possibly just extend this.
Admin token interface
Make a button to create tokens for any random github account, free for our employees/friends/ourselves, or if somebody purchased and there was an error.
When done, give Lennart a license
Issues cleanup
Add search to mobile
check for stripe customer ID before additional purchases
Otherwise stripe creates more customers w/ the same email!
Add navigation from docs back to main home page
Right now you can't get back to the home page on the docs site. The logo takes you to the root of the docs, which is sometimes nice, but maybe not what you'd expect (especially if you came from the home page)
Use actions instead of API routes, and redo checkout/registration flow to use username/password
Redirect to main branch when only lang slug is present
From user Alem Tuzlak on Discord:
Just a small suggestion for the remix docs, it would be cool if i went to remix.run/docs/en it would redirect me to the latest version or the main one of the docs instead of me hitting an error boundary. if you go to remix.run/docs it goes to => remix.run/docs/en/main but if you go to remix.run/docs/en it enters an error boundary
https://discord.com/channels/770287896669978684/770287896669978687/1110137964090101760
Expected Behavior:
https://remix.run/en -> redirects to https://remix.run/en/main
Visual accessibility issues in the remix.run/docs site
Reproduction
- Visit https://remix.run/docs/en/main/start/quickstart
- Run an accessibility audit, such as with Lighthouse or axe Devtools
System Info
n/a
Used Package Manager
npm
Expected Behavior
Pages such as https://remix.run/docs/en/main/start/quickstart shouldn't have any web accessibility issues.
Actual Behavior
Scanning with axe DevTools finds two visual errors:
- Insufficient color contrast: folks with low color perception and/or poor hardware or lighting conditions might not be able to read...
- ...in dark mode: the
#666666
commented-out text (e.g.# install runtime dependencies
) - ...in light mode: the
#30ba2d
light green commands (e.g.my-remix-app
)
- ...in dark mode: the
- Links indistinguishable without relying on color: the color contrast between link colors and regular body text similarly isn't enough for some folks to be able to see the difference...
- ...in dark mode: between the
#3992ff
link text compared to#a4a4a4
body text - ...in light mode: between
#1b6ef5
link text compared to#434343
body text
- ...in dark mode: between the
I haven't dug too deeply. There might be more insufficient color contrasts or other issues.
Some quick suggested remediations could be:
- Lightning the comments in dark mode to be more visually distinct
- Darkening the green text in light mode to be more visually distinct
- Adding an underline to link text, the way GitHub recently did for Markdown by default
Note that I'm not an accessibility professional and might have missed some issues. I'd be happy to send in a PR with these fixes or alternatives, but would recommend having a real professional go through a full site audit.
Dark mode via system preferences is not persistent across navigations
As you can see, dark mode via system preferences does not persist well
crazy-dark-mode.mov
I believe it's due to this script, which can get unsynchronized on navigation changes.
Fix display dates on blog posts
The display dates seem to be off by 1 on our blog posts, which is no good. Probably just some faulty logic somewhere
Pricing page updates
- Price going up to $1,200 for commercial
- What "beta" means
- We don't anticipate any more API changes
- Now is a good time to get in and help us get it stable
- Should be stable in a few weeks, work now can be deployed confidently then!
Fetch docs from github, use new syntax highlighter
Little encoding issue with Algolia Search
update vertical alignment of "Docs Navigation" in mobile header
Can view repo - Not purchased.
Hey! I was interested in remix and browsed around. After I saw your tweet: https://twitter.com/remix_run/status/1321470965134471171 I did the following:
Clicked buy on the indie license,
Logged in with Github,
Loaded the stripe purchase page, but then backed out (not paying),
loaded remix.run/dashboard and I can see the docs while also having an invite to collaborate here.
Hopefully, if this is not intentional you can catch it early!
Upgrade website to v0.13
Deploy websites with GH Actions
rework license invitation to use a token instead of the license key as the invite token
Add ability to change from npm to yarn/pnpm
Support multiple authors in meta image tags
Right now we only support uploading only one author to Cloudinary for our meta images
So for Remix ❤️ Vite we just have Pedro
I believe this is just because we only allow a single author to be passed
Add error handling/good fallbacks for Resource data
Either add error messages/clear defaults when certain data doesn't load, or improve the error message shown. These are all the data fetching that needs to be handled:
resources.yaml
-- Can probably default to the main error page if this failsfetchReadme
/getResourceReadme
-- Individual resource page, show a message that the readme can't be loaded properly with a link to the repo- image fails to fetch -- better fallback than a broken image
getSponsorUrl
-- Maybe just don't show the sponsor button if this one fails? I think this one actually works this way alreadyfetchResourceGitHubData
/getResourceGitHubData
-- Maybe some good fallbacks, such as "failed to load description". I think this is better than the whole thing blowing up
Licensing / Convertkit Features
Stripe lets them cancel any time. We've got automations in convertkit to warn them (to avoid getting a bunch of refund requests after the fact)
- If they cancel within 3 months
- Deactivate their license
- Give a special message from the registry instead of just 404, like "Your license has expired, to renew go to https://remix.run/renew/:token"
- Add convertkit refunded tag
Other cases need to put more thought in:
-
cancel after refund period months
- add convertkit tag
- add version to license so they can't install passed it
- remove from any cool education material when we have it if they no longer hold a current license
-
renew
- have endpoint to do it /renew/:key
- add ck tag
-
unused license
- after some time add ck tag
-
team member
- add ck tag for broadcasts
Add loading indicator to top nav
A suggestion from @brophdawg11
we should add some form of loading indicators to the top nav (Docs, Blog, Showcase, Resources). I clicked on one that didn't have a cache entry so it took ~1-2s and there's no visual feedback that my click did anything
blog - scroll is broken
Add types/validation for matches
useMatches
and other cases of matches don't supply any types. With the v2 upgrade, this ended up causing TS to start failing. Added a bunch of @ts-expect-error
statements with the intention of coming back and fixing them
If using zod
makes this easy, that's great since we already have it in this project. However, avoid using it in any data that ships to the client (so server-side only)
Bug: npm let us use undeclared (in package.json) dependencies
Is there a serious showstopper reason to not be using pnpm
yet?
(jump to the end to see about the bug from the title of this issue)
- For all these excerpts, assume
$ rm -rf node_modules/
has been run prior to the timed command. - First run was without lock file and second run was always with lock file.
- Verification made while standing on HEAD, which currently is commit
f54dbcd
npm
First run: ~55 seconds
$ time npm ci
added 1261 packages, and audited 1262 packages in 54s
10 vulnerabilities (9 moderate, 1 high)
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
real 0m54,574s
user 0m18,137s
sys 0m15,546s
Second run: ~20 seconds
$ time npm ci
[redacted...]
real 0m19,637s
user 0m11,526s
sys 0m8,368s
pnpm
First run: ~40 seconds
$ time pnpm i
Packages: +1168
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Progress: resolved 1232, reused 1167, downloaded 0, added 1168, done
[redacted...]
Done in 39.5s
real 0m39,637s
user 0m16,913s
sys 0m14,826s
Second run: ~3 seconds
$ time pnpm i
[redacted...]
Done in 2.7s
real 0m2,802s
user 0m8,708s
sys 0m2,670s
yarn
First run: ~113 seconds
$ time yarn install
yarn install v1.22.21
info No lockfile found.
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
[4/5] Linking dependencies...
warning "@docsearch/react > @algolia/[email protected]" has unmet peer dependency "@algolia/client-search@>= 4.9.1 < 6".
warning "@docsearch/react > @algolia/autocomplete-core > @algolia/[email protected]" has unmet peer dependency "search-insights@>= 1 < 3".
warning "@docsearch/react > @algolia/autocomplete-core > @algolia/[email protected]" has unmet peer dependency "@algolia/client-search@>= 4.9.1 < 6".
warning " > @remix-run/[email protected]" has unmet peer dependency "@remix-run/server-runtime@^1.15.0 || ^2.0.0".
[5/5] Building fresh packages...
success Saved lockfile.
Done in 112.08s.
real 1m52,302s
user 0m17,545s
sys 0m4,605s
Second run: ~7 seconds
$ time yarn install
Done in 6.84s.
real 0m7,085s
user 0m8,749s
sys 0m10,127s
Other considerations
-
npm requires
audit
npm
shows "10 vulnerabilities (9 moderate, 1 high)". After runningnpm audit fix
we are left still with "9 moderate severity vulnerabilities". Finallynpm audit fix --force
gets ride of all the warnings, however it requires further analysis as some packages needed a SemVer major change.pnpm
produces a clean installation without warnings. However after installing I runpnpm audit
just in case, and it found only one vulnerability:
$ pnpm audit
[redacted]
moderate │ xml2js is vulnerable to prototype pollution
-
yarn leave us with "unmet peer dependencies"
-
both yarn and npm let us use undeclared dependencies
Whether we install and run with yarn or npm, the server starts and runs ok. However, if we install our dependencies with pnpm, and run the server, we encounter this bug:
Error: Cannot find module 'react-router-dom' imported from 'app/routes/docs.$lang.$ref.tsx'
This happens because the way both yarn and npm resolve peer dependencies, which is wrong, as it let us use packages that we haven't explicitly declared in our package.json
.
I vote we jump head first to start using pnpm
. If no arguments against are given, I'll do the PR.
Upgrade rehype, remark, and related dependencies
The following packages needed to be bumped to the latest major versions:
- rehype-autolink-headings
- rehype-slug
- rehype-stringify
- remark-gfm
- remark-html
- remark-parse
- remark-rehype
- unified
- unist-util-visit
I upgraded them, deployed, and everything seemed to work fine. However, I got some type errors and am not familiar enough with these packages or the setup to quickly fix it. I figured this might be an issue someone else would be eager to dig their hands into
Fix www redirections
http://www.remix.run
and https://www.remix.run
should both redirect to https://remix.run
Blog on mobile looks terrible
Too much margin and the font is kinda big. FIx it.
Add auth token endpoint for CLI auth flow
Instead of asking users to go copy/paste their auth token from the dashboard, it'd be neat if we could open the login/purchase page in the browser for them and then call back to a localhost
URL with the auth token when they're done. So the new user UX flow would be:
npm init remix
- open the web browser
- purchase a license
- init script gets the token and finishes
docs CSS doesn't load when navigating from homepage under certain circumstances
PS: Can't migrate the issue from remix-run/remix since remix-website is not a proposed target.
Upgrade to Remix 2.6.0
Quoting from the blog post Open Sourcing the Remix Website
We invite you to explore and learn from the source code
...
Open sourcing our website allows us to provide a real-world Remix site to learn from
I believe that if one of the ideas is to provide a real-world working site, it would be better to do it with the latest version of Remix.
Currently the website is using 2.5.1
I haven't used Vite so far, I'm waiting for it to become stable-stable to start using it on my projects, but I don't mind giving it a shot if you need help with this upgrade. I love solving issues :)
Look into typesense
I've been curious about typesense as an alternative to DocSearch (what we use now). It would also be nice to add search to the react-router website, so curious if this is a good fit for that as well.
Would need to do a little spike work to see what's involved, if it's easier to use, and if it would be easy to migrate to
Edit link referencing RR website
This line
remix-website/app/routes/docs/$lang.$ref.tsx
Line 747 in 6e9127a
Should be
- let repoUrl = "https://github.com/remix-run/react-router";
+ let repoUrl = "https://github.com/remix-run/remix";
For some reason, I can't create a PR, so that's why I'm posting this issue
"Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node." on https://remix.run/
Update quick start docs to match the starter template
- do it in typescript
- make a very clear note to use the no-ts branch for JS only
unusual scrolling issue with a screening effect on Mac Safari aswell as Chrome
Pull Template data from GitHub
Need to pull the following data from GitHub for the templates
- description
- tags
- stars
- sponsor URL (if exists)
Will want to leverage server cache so we aren't constantly re-fetching this data. Will need to figure out a good strategy for fetching all of the templates, filtered templates, and individual templates. Ideally we want to use the same cache for each of these, and maybe a separate one or separate key for the README (for template slug pages)
associate github account w/ remix account, add to remix source code repo
email new purchases the registration url after a purchase
No HTTPS Redirects for `remix.run` on Safari
What version of Remix are you using?
N/A, issue is with remix.run
site
Are all your remix dependencies & dev-dependencies using the same version?
- Yes
Steps to Reproduce
For the remix.run
site and all routes under it (i.e. /docs
), there aren't automatic redirects to HTTPS in Safari for both macOS and iOS.
So typing in remix.run
or remix.run/docs
in the address bar leads me to http://remix.run
or http://remix.run/docs
which causes a "Not Secure" badge to be shown.
I tried it in Chrome and it did direct me to the HTTPS version, so not too sure if it's a Safari only bug or a feature of Chrome, though I didn't have forced redirects to HTTPS turned on in Chrome.
Expected Behavior
I expected the site to be redirected to the HTTPS version on every browser/platform.
Actual Behavior
On Safari across all devices (both up to date), the site hasn't been performing forced redirects to the "securely" connected site for months.
Here's a link to a screen recording to demonstrate what I'm seeing on my end.
I do know Kent mentioned in a podcast that Remix.run is hosted on Fly.io, and in case it's not just a Safari issue, just wanted to help out and throw in some helpful things I found on Fly's website.
There's an [http_service]
section of the fly.toml
that has a force_https
flag that can be enabled, i.e.:
# /fly.toml
[http_service]
force_https = true
Though it only works for Apps_V2 servers that are only using HTTP/HTTPS services.
Or, you can use the services.ports
section in whichever service's section that's being used to serve the site, i.e.:
[[services.ports]]
force_https = true
Or, you can use Express middleware to handle it for you, per Fly.io's blog post:
app.use (function (req, res, next) {
if(req.get("X-Forwarded-Proto")=="http") {
// request was via http, so redirect to https
res.redirect('https://' + req.headers.host + req.url);
} else {
next();
}
});
Thanks for all you guys are doing in the React space! Super excited about HMR and HDR in v2. Cheers!
Handle incomplete emails
Remove unused package `dotenv-cli`
It looks that the development dependency dotenv-cli
is unused. A grep through the repository didn't show matches. However I understand it's a CLI tool to run the project with different or even combine .env
files.
While I don't see any reason for this dependency, if there's some valid use, then it should be documented.
package.json
uses it for the preview
script:
"preview": "cross-env NODE_ENV=production dotenv node server.mjs",
But we already have dotenv
setup on vitest.config.mts
, so it seems is not doing any useful work there. Or at least I cannot see it after reading the package documentation.
Add combobox to templates page
It would be nice to have a combo box on the templates page that allows you to search different tags and possibly template names
Cursor is pointer on algolia search modal in docs website
What version of Remix are you using?
remix.run
Are all your remix dependencies & dev-dependencies using the same version?
- Yes
Steps to Reproduce
- Access remix.run/docs
- Click top left algolia search button.
- Cursor is pointer on the modal.
Expected Behavior
Cursor is default on the modal.
Actual Behavior
Cursor is pointer on the modal.
Algoliasearch modal has [role=button]
attribute.
When [role=button]
, cursor is pointer.
This class is set by TailwindCSS.
But algoliasearch don't set css for cursor.
So add css for cursor, fix that.
Ex.
.DocSearch-Container {
cursor: auto;
}
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.