-
Notifications
You must be signed in to change notification settings - Fork 89
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
[epic] Trial flowershow with some sites #21
Labels
Epic
Epic
Comments
@olayway can you put notes / links about how we sorted out using custom components and our overall learnings:
|
@rufuspollock, done |
FIXED. All done - lots learned 🎉 🚢 |
rufuspollock
pushed a commit
to rufuspollock/flowershow
that referenced
this issue
Oct 27, 2023
olayway
pushed a commit
that referenced
this issue
Oct 31, 2023
olayway
pushed a commit
that referenced
this issue
Oct 31, 2023
olayway
pushed a commit
that referenced
this issue
Oct 31, 2023
olayway
pushed a commit
that referenced
this issue
Oct 31, 2023
nyejon
pushed a commit
to nyejon/flowershow_blog
that referenced
this issue
Nov 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Trial product e.g. on flowershow itself or building Life Itself new community site. Possible candidates
Acceptance
Tasks
unstyled.js
(?)Issues from ecosystem upgrade
flowershow
or similar. Or have user components in a specific folder distinct from componentsYou cannot define a route with the same specificity as a optional catch-all route ("/" and "/[[...slug]]")
[[...slug]]
to[..slug]
✅2022-08-23 move stuff into mdxNotes from Ecosystem upgrade
Changes
This shows changes to files in the app in ecosystem vs original flowershow. Additions aren't a problem at all. It's changes that are a problem.
unstyled.js
git diff 1766db630dcac5eaf81e00d95bdbe7a3a3647447 5cd6035c8963ea7819272e8d38235adacc49dc5f layouts/unstyled.js
MDX.js
(UPDATE)
git diff 1766db630dcac5eaf81e00d95bdbe7a3a3647447 d9154b0e5438a18c1b5596ce0f4e22c389121379 components/MDX.js
git diff 1766db630dcac5eaf81e00d95bdbe7a3a3647447 4b40577c51f407e5e278140163339fc3b722ee0b components/MDX.js
[[...slug]].js
(UPDATE)
lib/db.js
git diff 1766db630dcac5eaf81e00d95bdbe7a3a3647447 44acfcfa9d8e9eae3f618cb6568e348c77b1d12e pages/\[\[...slug\]\].js
git diff 1766db630dcac5eaf81e00d95bdbe7a3a3647447 ca1ce9a76e1840bd53492dcb3885880effd5c5b5 pages/\[\[...slug\]\].js
package.json
git diff 1766db630dcac5eaf81e00d95bdbe7a3a3647447 d0d578f9a71c45dd8146183d0c79771ca3982347 package.json
Notes from creating Flowershow website using Flowershow template
MDX syntax support
MDX syntax fully works and is documented on this page - https://flowershow.app/docs/mdx.
Most important syntax elements that work:
import
andexport
statements which allow for importing as well as locally defining components/data,{}
.Separation of template components and user defined components
You can have custom components outside of the Flowershow template's
/components
dir and still import them in MDX files.In order to have less confusing import paths atm we're symlinking the folder with custom components (in our case
/site/components
) toflowershow/templates/default/components
. See issue #88 to learn more.Tailwind
You can use Tailwind to style JSX components in your MDX files. This is documented here: https://flowershow.app/docs/tailwind
The text was updated successfully, but these errors were encountered: