treefarmstudio/odyssey-theme

A modern business marketing website theme/starter built with Astro 🚀

odyssey-theme's Issues

stakblitz missing images

I see it's running astro dev so maybe images need to be copied?

Stackblitz is not working with 2.0

Might need to open an issue with Stackblitz, it might be an issue with the Astro image integration

Stable is broken without @odyssey-theme/components package

This will be fixed shortly with v2.0 but wanted to make people aware it's a known issue

integrate this theme into Astro local project

hi, I am new in Astro but not in Node/JS - I created a local Astro project (in Astro-js, not TS) and I would want to integrate the theme "odyssey-theme" - I may be jump over an explanation but I do not understand how to add that theme at my basic Astro website . Thank you !

Nav.astro redudant to Header.astro?

As titled. Header.astro includes the slot NAV and the styling already. Or did I miss something.
Thanks.

Live demo website down

The live demo website is down: live demo

The score is not a perfect 100 in performance

Broken images in live demo and also README

https://odyssey-theme.littlesticks.dev/theme/get-started/

Firefox on Windows

Link broken in README for form-fields

Hi! The link sending to the form-fields is broken, because it is still routed to 'core/Form...', instead it should be 'form-fields/Form...'.

SVG logo causing 404 error

Hi.` I've forked the repo and successfully run it but when switching out the logo in the 'Logo.astro' file is causing a 404 error... I've consulted others, and good ol chatgpt, and can't understand why the following modified Logo.astro file can't access the alternative logo in the same directory. In order to troubleshoot, I've reduced the size of the logo, tried another svg logo, tried referencing the relative and absolute paths in the Logo.astro file, and confirmed the appropriate server environment permissions for the file ("-rw-rw-r--"). I'm at a loss and welcome any input. Happy to tip. Thanks so much!

<img class="odyssey-logo" src="logobuoy.svg" alt="buoy.fish">

Broken build caused by old component package being removed from npm

I'm trying to rebuild an existing site based on Odyssey but do not yet want to upgrade to the latest version. Don;t have the time as this is a breaking change.

However npm install now fails on clean machine as you have deleted the old components package from npm.

Can you please reinstate the old package or provide me with a version I can use locally?

Thanks

astro 1.0.0-rc.1

It seems canonicalURL changed into url so Astro.url must be used

odyssey-theme is not working with astro 1.0.0-rc.1

Odyssey theme does not work with last Astro 2.8.3 version

I downloaded this package .
and with cd theme npm install npm start
it works.
Now as I want to integrate it in a recent Astro site , version 2.8.3 , I upgraded the package.json : see attached
package.json.zip
and then I got in my console the following errors :
`$ npm start

[email protected] start
astro dev

🚀 astro v2.8.3 started in 538ms

┃ Local http://localhost:3000/
┃ Network use --host to expose

/home/william/Téléchargements/odyssey-theme-main/theme/src/components/theme-switcher/theme-switcher.ts:51
this._doc = document.firstElementChild;
^

ReferenceError: document is not defined
at new ThemeSwitcher (/home/william/Téléchargements/odyssey-theme-main/theme/src/components/theme-switcher/theme-switcher.ts:51:17)
at new LitElementRenderer (file:///home/william/T%C3%A9l%C3%A9chargements/odyssey-theme-main/theme/node_modules/@lit-labs/ssr/lib/lit-element-renderer.js:18:24)
at render (/home/william/Téléchargements/odyssey-theme-main/theme/node_modules/@astrojs/lit/server.js:39:19)
at render.next ()
at Object.renderToStaticMarkup (/home/william/Téléchargements/odyssey-theme-main/theme/node_modules/@astrojs/lit/server.js:108:11)
at renderFrameworkComponent (/home/william/Téléchargements/odyssey-theme-main/theme/node_modules/astro/dist/runtime/server/render/component.js:187:66)

Node.js v18.14.0
`
How can I solve that error please ?
(I do not need theme switcher at1st sight)
thanks

No dev dependencies

Hi there!

Inside package.json there is nothing to be installed because there is nothing is listed under devDependencies.
Using Deploy to Netlify button also failing.

how to support markdown format posts

under theme/src/pages there is only .astro format

Hello! Is there any way to make Chinese and English characters have the same weight?

/* Special thanks to this tool for local fonts CSS generation:
https://google-webfonts-helper.herokuapp.com/fonts/lato?subsets=latin
*/

/* roboto-serif-600 - latin /
@font-face {
font-family: 'Noto Serif TC';
font-style: normal;
font-weight: 600;
font-display: swap;
src: local(''),
url('/assets/fonts/noto-serif-tc-chinese-traditional-600-normal.woff2') format('woff2'), / Chrome 26+, Opera 23+, Firefox 39+ /
url('/assets/fonts/noto-serif-tc-chinese-traditional-600-normal.woff') format('woff'); / Chrome 6+, Firefox 3.6+, IE 9+, Safari 5.1+ /
}
/ roboto-serif-700 - latin /
@font-face {
font-family: 'Noto Serif TC';
font-style: normal;
font-weight: 700;
font-display: swap;
src: local(''),
url('/assets/fonts/noto-serif-tc-chinese-traditional-700-normal.woff2') format('woff2'), / Chrome 26+, Opera 23+, Firefox 39+ /
url('/assets/fonts/noto-serif-tc-chinese-traditional-700-normal.woff') format('woff'); / Chrome 6+, Firefox 3.6+, IE 9+, Safari 5.1+ */
}

/* lato-300 - latin /
@font-face {
font-family: 'Noto Serif TC';
font-style: normal;
font-weight: 300;
font-display: swap;
src: local(''),
url('/assets/fonts/noto-serif-tc-chinese-traditional-300-normal.woff2') format('woff2'), / Chrome 26+, Opera 23+, Firefox 39+ /
url('/assets/fonts/noto-serif-tc-chinese-traditional-300-normal.woff') format('woff'); / Chrome 6+, Firefox 3.6+, IE 9+, Safari 5.1+ /
}
/ lato-regular - latin /
@font-face {
font-family: 'Noto Serif TC';
font-style: normal;
font-weight: 400;
font-display: swap;
src: local(''),
url('/assets/fonts/noto-serif-tc-chinese-traditional-400-normal.woff2') format('woff2'), / Chrome 26+, Opera 23+, Firefox 39+ /
url('/assets/fonts/noto-serif-tc-chinese-traditional-400-normal.woff') format('woff'); / Chrome 6+, Firefox 3.6+, IE 9+, Safari 5.1+ /
}
/ lato-700 - latin /
@font-face {
font-family: 'Noto Serif TC';
font-style: normal;
font-weight: 700;
font-display: swap;
src: local(''),
url('/assets/fonts/noto-serif-tc-chinese-traditional-700-normal.woff2') format('woff2'), / Chrome 26+, Opera 23+, Firefox 39+ /
url('/assets/fonts/noto-serif-tc-chinese-traditional-700-normal.woff') format('woff'); / Chrome 6+, Firefox 3.6+, IE 9+, Safari 5.1+ /
}
/ lato-700italic - latin /
@font-face {
font-family: 'Noto Serif TC';
font-style: italic;
font-weight: 700;
font-display: swap;
src: local(''),
url('/assets/fonts/noto-serif-tc-chinese-traditional-700-normal.woff2') format('woff2'), / Chrome 26+, Opera 23+, Firefox 39+ /
url('/assets/fonts/noto-serif-tc-chinese-traditional-700-normal.woff') format('woff'); / Chrome 6+, Firefox 3.6+, IE 9+, Safari 5.1+ */
}
:root {
--font-size-sm: clamp(14.4px, 0.07vw + 14.13px, 15px);
--font-size-base: clamp(18px, 0.23vw + 17.09px, 20px);
--font-size-md: clamp(22.5px, 0.47vw + 20.61px, 26.66px);
--font-size-lg: clamp(28.13px, 0.84vw + 24.76px, 35.54px);
--font-size-xl: clamp(35.16px, 1.39vw + 29.6px, 47.37px);
--font-size-xxl: clamp(43.95px, 2.18vw + 35.22px, 63.15px);
--font-size-xxxl: clamp(54.93px, 3.32vw + 41.64px, 84.17px);
}

html,
body {
line-height: 1.5;
font-family: var(--theme-font-family-serif);
font-size: var(--font-size-base);
color: var(--theme-on-bg);
}

h1,
h2,
h3 {
font-family: var(--theme-font-family-serif);
font-weight: 700;
}

h1 {
font-size: var(--font-size-xxl);
}

h2 {
font-size: var(--font-size-xl);
}

h3 {
font-size: var(--font-size-lg);
}

h1,
h2 {
line-height: 1.1;
font-weight: 700;
}

h3 {
font-weight: 500;
}

h6 {
font-size: var(--font-size-sm);
}

h1,
h2,
h3,
h4,
h5,
h6,
p {
margin: 0 0 1rem 0;
}

blockquote {
font-style: italic;
font-size: var(--font-size-base);
font-weight: 500;
margin-bottom: 1rem;
padding-left: 1.5rem;
border-left: 0.25rem solid var(--theme-on-bg);
}

How do I get the emailform working?

I can't find any POP/SMTP stuff in the codebase? Do I add them in 'ContactForm.astro' or directly in 'contact.astro'?

Is there an easy way to disable switching theme AND also choosing the default theme?

Deploy to Netlify button isn't working...

Netlify deploy failing

Launching from this repo directly, I'm getting a build failure. Looks like astro isn't available in deploy sequence?

8:43:32 AM: ────────────────────────────────────────────────────────────────
8:43:32 AM: 1. Build command from Netlify app
8:43:32 AM: ────────────────────────────────────────────────────────────────
8:43:32 AM: ​
8:43:32 AM: $ npm run build
8:43:32 AM: npm WARN config tmp This setting is no longer used. npm stores temporary files in a special
8:43:32 AM: npm WARN config location in the cache, and they are managed by
8:43:32 AM: npm WARN config cacache.
8:43:32 AM: > [email protected] build
8:43:32 AM: > astro build
8:43:32 AM: sh: 1: astro: not found
8:43:32 AM: ​
8:43:32 AM: ────────────────────────────────────────────────────────────────
8:43:32 AM: "build.command" failed
8:43:32 AM: ────────────────────────────────────────────────────────────────
8:43:32 AM: ​
8:43:32 AM: Error message
8:43:32 AM: Command failed with exit code 127: npm run build (https://ntl.fyi/exit-code-127)

[Q] Is there a way to add an author to a post

Hi, is there any way to add an author to a post with this theme?

> @SteveALee Can you elaborate on the "page not found" issue you were seeing with astro-icon? That might be a separate issue I need to look into but I can't seem to reproduce it. Thanks!

          > @SteveALee Can you elaborate on the "page not found" issue you were seeing with astro-icon? That might be a separate issue I need to look into but I can't seem to reproduce it. Thanks!

I think I might have reproduced this very same issue. This morning I duplicated an already working odyssey-theme repo and tried running npm install && npm start and it just broke everthing and started throwing the "404: Not found
Path: /" astro icon page for me.

Originally posted by @irfanirshad in #19 (comment)

Project always creates sub theme folder when deploying from vercel or installing via command

Project always creates sub theme folder when deploying from vercel or installing via command meaning it can never find the astro command in the project root folder! What is the solution to this?

Disabling showLittleSticksPlug in settings.js doesn't work

I have set showLittleSticksPlug: false, in settings.js

Yet the Little Sticks plug in the footer remains active with the button Get this template still showing.

Am I missing something with removing this?

Thanks

migrate project to astro 2.0

Currently the project uses astro 1, and when using astro 2 the build fails.

There is a guide here
https://docs.astro.build/en/guides/upgrade-to/v2/

Before upgrading

~/w/o/theme (main)> yarn build
yarn run v1.22.19
$ astro build
05:02:25 PM [build] output target: static
05:02:25 PM [build] Collecting build info...
05:02:25 PM [build] Completed in 44ms.
05:02:25 PM [build] Building static entrypoints...
Ambiguous external namespace resolution: "node_modules/lit/index.js" re-exports "html" from one of the external modules "lit-element/lit-element.js" and "lit-html/is-server.js", guessing "lit-element/lit-element.js".
Ambiguous external namespace resolution: "node_modules/lit/index.js" re-exports "LitElement" from one of the external modules "lit-element/lit-element.js" and "lit-html/is-server.js", guessing "lit-element/lit-element.js".
Ambiguous external namespace resolution: "node_modules/lit/index.js" re-exports "css" from one of the external modules "lit-element/lit-element.js" and "lit-html/is-server.js", guessing "lit-element/lit-element.js".
"html", "LitElement" and "css" are imported from external module "lit-html/is-server.js" but never used in "node_modules/lit/index.js".
05:02:28 PM [build] Completed in 2.99s.

 building client
Generated an empty chunk: "hoisted"
Completed in 239ms.


 generating static routes
▶ src/pages/index.astro
  └─ /index.html (+440ms)
▶ src/pages/landing-pages/landing-1.astro
  └─ /landing-pages/landing-1/index.html (+26ms)
▶ src/pages/landing-pages/landing-2.astro
  └─ /landing-pages/landing-2/index.html (+6ms)
▶ src/pages/company/contact.astro
  └─ /company/contact/index.html (+16ms)
▶ src/pages/company/about.astro
  └─ /company/about/index.html (+14ms)
▶ src/pages/company/legal.astro
  └─ /company/legal/index.html (+15ms)
▶ src/pages/theme/customizing-odyssey.mdx
  └─ /theme/customizing-odyssey/index.html (+19ms)
▶ src/pages/theme/get-started.astro
  └─ /theme/get-started/index.html (+139ms)
▶ src/pages/theme/style-guide.astro
  └─ /theme/style-guide/index.html (+16ms)
▶ src/pages/theme/theme-setup.mdx
  └─ /theme/theme-setup/index.html (+16ms)
▶ src/pages/blog/index.astro
  └─ /blog/index.html (+21ms)
▶ src/pages/blog/posts/odyssey-theme-officially-released.mdx
  └─ /blog/posts/odyssey-theme-officially-released/index.html (+12ms)
▶ src/pages/blog/posts/remote-work-mental-health.mdx
  └─ /blog/posts/remote-work-mental-health/index.html (+12ms)
▶ src/pages/blog/posts/consider-hybrid-work.mdx
  └─ /blog/posts/consider-hybrid-work/index.html (+10ms)
▶ src/pages/blog/tags/index.astro
  └─ /blog/tags/index.html (+1ms)
▶ src/pages/blog/tags/[slug].astro
  ├─ /blog/tags/remote-work/index.html (+14ms)
  └─ /blog/tags/odyssey-theme/index.html (+27ms)
▶ src/pages/404.astro
  └─ /404.html (+12ms)
Completed in 2.59s.

05:02:31 PM [build] 18 page(s) built in 5.90s
05:02:31 PM [build] Complete!
✨  Done in 8.26s.

Build passes.

But fails to build after

~/w/o/theme (main)> yarn add astro@latest

yarn add v1.22.19
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
warning [email protected]: The engine "pnpm" appears to be invalid.
warning [email protected]: The engine "pnpm" appears to be invalid.
[3/4] 🔗  Linking dependencies...
warning "@astrojs/mdx > @mdx-js/[email protected]" has unmet peer dependency "rollup@>=2".
warning "@astrojs/mdx > [email protected]" has unmet peer dependency "typescript@>3".
warning "@astrojs/mdx > remark-shiki-twoslash > [email protected]" has unmet peer dependency "typescript@>3".
warning Workspaces can only be enabled in private projects.
[4/4] 🔨  Building fresh packages...
success Saved lockfile.
warning "astro" is already in "devDependencies". Please remove existing entry first before adding it to "dependencies".
warning Workspaces can only be enabled in private projects.
success Saved 24 new dependencies.
info Direct dependencies
└─ [email protected]
info All dependencies
├─ @astrojs/[email protected]
├─ @astrojs/[email protected]
├─ @astrojs/[email protected]
├─ @astrojs/[email protected]
├─ @astrojs/[email protected]
├─ @astrojs/[email protected]
├─ @esbuild/[email protected]
├─ @types/[email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
└─ [email protected]
✨  Done in 14.54s.
~/w/o/theme (main)> yarn build
yarn run v1.22.19
$ astro build
05:04:07 PM [astro] Added src/env.d.ts types
05:04:07 PM [content] No content directory found. Skipping type generation.
05:04:07 PM [build] output target: static
05:04:07 PM [build] Collecting build info...
05:04:07 PM [build] Completed in 107ms.
05:04:07 PM [build] Building static entrypoints...
[vite:build-import-analysis] Parse error @:10:282
file: @astro-page:src/pages/theme/customizing-odyssey@_@mdx:10:281
 8:     p: "p"
 9:   }, props.components);
10:   return <_components.p>{"const page = () => import(“/src/pages/theme/customizing-odyssey.mdx”);\nimport "}{renderers}{" from “@astro-renderers”;\nimport "}{onRequest}{" from “�empty-middleware”;export "}{page}{"\nexport "}{renderers}{";\nexport "}{onRequest}{";"}</_components.p>;
                                                                                                                                                                                                                                                                                             ^
11: }
12: function MDXContent(props = {}) {
 error   Parse error @:10:282
  File:
    @astro-page:src/pages/theme/customizing-odyssey@_@mdx:10:281
  Code:
    8:     p: "p"
     9:   }, props.components);
    10:   return <_components.p>{"const page = () => import(“/src/pages/theme/customizing-odyssey.mdx”);\nimport "}{renderers}{" from “@astro-renderers”;\nimport "}{onRequest}{" from “�empty-middleware”;export "}{page}{"\nexport "}{renderers}{";\nexport "}{onRequest}{";"}</_components.p>;
                                                                                                                                                                                                                                                                                                 ^
    11: }
    12: function MDXContent(props = {}) {
  Stacktrace:
Error: Parse error @:10:282
    at parse$e (file:///Users/jason/workspace/odyssey-theme/theme/node_modules/vite/dist/node/chunks/dep-df561101.js:16472:355)
    at Object.transform (file:///Users/jason/workspace/odyssey-theme/theme/node_modules/vite/dist/node/chunks/dep-df561101.js:46579:27)

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
~/w/o/theme (main) [1]>

`shadowroot` attribute is deprecated, and will *no longer function*.

The older, non-standardized shadowroot attribute is deprecated, and will no longer function in M119. Please use the new, standardized shadowrootmode attribute instead.