Bare-bones comparison of react-notion and react-notion-x.

📝 Notion inspired TODO with Notion integration A sleek and modern todo application built with React, TypeScript, and Vite, featuring a beautiful UI powered by Radix UI components. You can test app without Notion backend ⬇️

No description available

No description available

No description available

No description available

No description available

No description available

Testing react-notion-x with next and typescript.

For markdown render test in React (with Notion DB)

Test task https://laser-makemake-69e.notion.site/React-23e555d928db49e89122f743406e6f0f

Scandiweb entry react developer test by Ivan Vasilev https://www.notion.so/Entry-React-developer-TEST-39f601f8aa3f48ac88c4a8fefda304c1

Develeap Notion Clone - A full-featured Notion.so clone built with Next.js, React, TypeScript, Tailwind CSS, and Zustand. Includes comprehensive Playwright E2E test suite.

Professional testing and certification platform for Tarteel AI - React app with Notion integration, 60-min timed tests, and PDF certificates

This repository contains a solution for a Notion test designed. The solution is implemented using React and Express, and it addresses the key requirements and challenges outlined in the test.

AutoMata is visual workflow automation tool built with Next.js, Tailwind CSS, TypeScript, Prisma, and React Flow. Allows users to connect services like Discord, Slack, Notion, and Google Drive to design, test, and publish automated flows seamlessly.

# Senior React Developer test # **Welcome to Scandiweb React Developer test assignment!** ## Overview This task will put you face-to-face to some common tasks in the world of React development and possibly will get you acknowledged with a bit of new technologies. You are be expected to fetch data from the GraphQL endpoint and to provide an interface to view and interact with this data. You can find the endpoint [here](https://github.com/scandiweb/junior-react-endpoint), along with instructions on how to launch it. The solution should get implemented as per design, which is available at [[this link](https://www.figma.com/file/MSyCAqVy1UgNap0pvqH6H3/Junior-Frontend-Test-Designs-Public?node-id=0%3A1)]. ## Before you start The provided endpoint is a (GraphQL -https://graphql.org/learn/) endpoint. If you are not familiar with GraphQL - don't worry, only entry-level functionality is utilized. You can use any GraphQL client, for example, our own minimalistic: (**Opus** - https://www.npmjs.com/package/@tilework/opus) or more widespread and heavyweight (**Apollo** - https://www.apollographql.com/docs/react/). The functionality should be implemented exactly as-per-design. Not necessarily pixel-perfect though. Pay close attention to all of the details, there should not be any noticeable mismatches between the designs and your implementation both in terms of design and functionality. Think about the implementable functionality in scale, as in a real-life project. What will happen if you have more than 4 products? The pagination is not expected though - it is not in the design. ## Toolkit requirements When selecting a toolkit for this assignment, following these guidelines is mandatory. ## Required: - React. Anything not written in React will be rejected automatically. This is a React position, we expect a React solution. - Class components. Due to our [work specifics]([https://docs.scandipwa.com/stack/override-mechanism/extending-javascript](https://docs.scandipwa.com/developing-with-scandi/override-mechanism/extending-javascript)) we utilize them heavily. - Create-react-app to scaffold the application. ## Allowed: - State management libraries (e.g. Redux, Recoil) - CSS-in-JS approach allowers (e.g. styled-components) ## Prohibited: - UI libraries (e.g. Tailwind, Material UI, Ant Design) - Functional components, due to the reasons described above. ## Functionality requirements - PLP - product listing page, a.k.a. category page - PDP - product description page, a.k.a. product page - Cart page + Cart overlay (minicart) ## Details See some more specific information on the main requirements below. Remember - if something is in the design, but is not explicitly described here or above, it should be implemented anyways. - Ability to add/remove products and change their amounts in cart - on the cart page itself, PLP and PDP should be provided. - For products that have various options (attributes) - the options should be selected. - The selected options of added to cart products should be visible in cart overlay and in cart page. - If an attribute is a swatch attribute (type = swatch), a representation of the value should be rendered on PDP and PLP, rather than text description (e.g. the color itself, not "Blue" or "0000FF") - Filtering products by category name for all of the categories from BE - The descriptions provided in HTML format should be parsed and presented as HTML, not as plain text - Ability to change the currency of the store to one of the available currencies ## Last, but not least If you have any questions about the assignment, feel welcome to contact us with your questions! ### **How to submit?** 1. Push your code to Github and send us the link to your repository that is shared with a user with **hr@scandiweb.com** email or you can keep it public as well. 2. You can either send an invitation link or send the repository link directly in email. When submitting your Github link, please make sure that the repository link has your Name and Surname that you applied with in it! 3. **Make sure your repository is public so our evaluators could see it!** Have any questions? Please check out our Frequently Asked Questions page! [❓React Developer test - FAQ/frequently asked questions (1)](https://www.notion.so/8b0feb4481a549bc81f6be9826902125) # Good luck!  *Well, we just looked up some random image in Unsplash for "good luck" and here it is, the Chinese dragon!*

A sequential business visionary, Prof. Alex has more than two many years of experience during which he has worked crosswise over different ventures with organizations, for example, Scout Electromedia, SOMA Networks, BroadSoft, and Singularity Networks, and even established three organizations. In the times past, a specialist would choose what ought to be constructed, a coder would code it, a client would utilize it(maybe), and after that an investigator would attempt to make sense of what occurred. Today, high-performing organizations sanction interdisciplinary groups to iteratively improve results in a specific territory utilizing light-footed. That is somewhat dynamic; so here’s a progressively substantial perspective on what it implies by and by: That is a testable depiction of deft and you’ll know it’s working if: a) The group is utilizing ceaseless plan to improve the level of highlights that see high commitment b) The group is utilizing dexterous to build their speed as far as highlight yield c) The group is utilizing DevOps to make an increasingly ceaseless pipeline and discharge to clients all the more as often as possible Where do investigation become an integral factor? Not toward the end, and not afterward. An advanced group is utilizing lithe investigation to carry center and cognizance to their work crosswise over structure, coding, and conveyance. How would you know whether you’re getting to coordinated examination? I’ve watched seven central focuses with groups that have an advanced practice: All Ideas are Testable: When I got some information about his organization’s routine with regards to nimble, a CTO companion of mine let me know: ‘You know; you can’t simply take a multi month thought, cut it into fourteen day emphasess, and get coordinated’. We’re terrible at making our thoughts testable. I’ve differently been an originator, CEO, guide, and financial specialist for quite a long time, and when I get another thought, despite everything I begin with ‘Would n’t it be cool if’. Furthermore, that is alright, yet not once you choose to build up that thought. By then, render your thought testable. I like if the plan ‘In the event that we accomplish something for some particular persona or fragment, at that point they will react in some particular, quantifiable way’. For instance, in the event that we ran an organization that fixes cooling frameworks and chose it is cool to make an application for our field experts, we may render something like ‘On the off chance that we manufacture an application for the field specialists, at that point they will utilize it and it will build their billable hours’. Enormous Ideas Get Tested: This is the embodiment of Lean Startup. So as to limit squander, thoughts get tried with item intermediaries (MVPs) before they’re contender for being constructed. What’s more, a ton of organizations have a group off some place accomplishing something Lean Startup-ish. Be that as it may, do the huge thoughts get tried? The ones that the organization is putting truckloads of money in and trusting will drive its natural development? That is the significant inquiry. “Past the conspicuous advantage of utilizing proof to locate the correct plan early, model testing likewise makes a progressively engaged and rational change to investigation in the product once it’s discharged” All User Stories are Readily Testable: The client story fills in as a highlight for iterative improvement. It has the organization ‘As a client persona, I need to accomplish something so I can accomplish some testable reward’. That last statement about the testable reward? That is very significant and a foundation of spry investigation. For each client story, it ought to be clear how you would model that story, place it before a guinea pig, brief them with an objective, and check whether they accomplish that objective or not. Key User Stories get Tested: And do key client stories get tried? I complete a great deal of work with groups and we invest energy recorded as a hard copy increasingly testable client stories. I’ve never met any individual who thought composing better client stories was a poorly conceived notion. In any case, the groups make a propensity for testing early and frequently, with intuitive models for example, that really stay with the act of making their accounts testable. Past the undeniable advantage of utilizing proof to locate the correct structure early, model testing additionally makes a progressively engaged and reasonable change to examination in the product once it’s discharged. Analyses are Instrumented into Code: Instrumenting examination into code is simple and reasonable, and most organizations do it. All things considered, the group’s conveying solid, client driven theories through their item pipeline that is going to pick the privilege central focuses for the investigations those perceptions are supporting. For instance, one anticipate our Masters of Science in Business Analytics understudies are chipping away at is the USFDA’s ‘MedWatch’ site. On it, clients submit data about antagonistic responses to drugs. Suppose we’re attempting to make it simpler for a bustling specialist to present these responses so as to expand the information we gather. What would it be a good idea for us to A/B test? There are a great deal of ‘fascinating’ conceivable outcomes, however without approved learning on what that specialist is thinking and needing when they visit the site, we’re probably not going to put resources into A/B tests that truly move the needle on execution. Examination are Part of Retrospectives: Successful groups don’t demo their product; they translate tests. Working in short 1-multi week dashes is a typical element of lithe. Groups talk about how things went, and why and how they need to change their routine with regards to deft. Fortunately, this is normal practice. What’s less basic is for groups to make a propensity for looking into their investigations during those reviews. Eventually, we’re animals of propensity, thus, a group that is not unequivocally making time to audit their examinations is likely not going to get to deft investigation. Choices are Implied by Analytics: Are choices suggested by the group’s examination, or is the arrangement just to ‘audit the numbers’? The group that is rehearsing spry examination definitely knows the ramifications of their perceptions, on the grounds that their perceptions are attached to tests and the analyses are attached to choices. For instance, would you say you are truly prepared to slaughter that element in the event that it sees low commitment? Imagine a scenario where a client grumbles and says they totally must have it. Dexterous investigation makes the activity of choosing simple. for more information click here : technology.siliconindia.com