# Share what you are working on and using!

**URL:** <https://discuss.write.as/t/share-what-you-are-working-on-and-using/401>\
**Category:** Development\
**Created:** [February 13, 2019, 3:39am UTC](https://discuss.write.as/t/share-what-you-are-working-on-and-using/401 "2019-02-13T03:39:50Z")\
**Posts on this page:** 1\
**Showing post:** 136

<div class="post-metadata">

**Author:** ![dino](https://discuss.write.as/user_avatar/discuss.write.as/dino/32/645_2.png) [@dino](https://discuss.write.as/u/dino)\
**Post date:** [November 9, 2020, 10:01pm UTC](https://discuss.write.as/t/share-what-you-are-working-on-and-using/401/136 "2020-11-09T22:01:56Z")

</div>

Created a Blazor WASM app that can generate the contents for a Write.as archive page. You can find it on this site: [https://apps.dinobansigan.com/](https://apps.dinobansigan.com/). Just find the link to the Archive Page Generator on the nav bar.

The reason I’m linking to the homepage is due to the nature of the website, it is a Blazor single page application. Linking directly to the specific [archive generator page](https://apps.dinobansigan.com/WriteAsArchivePageGenerator) results in an error, unless the website has already been loaded previously. So you have to go through the homepage to start up the app. I’m sure there’s a workaround to this _(I’m still a noob when it comes to Blazor)_, but for now this will do.

Now for the app itself. It is a client side app, which means performance depends on your browser and machine. Building the archive page contents for a Write.as site with hundreds of posts can take awhile.

---

_[View the full topic](https://discuss.write.as/t/share-what-you-are-working-on-and-using/401)._